Privacy Policy

Lettrim is a writing service operated by an individual based in India. The operator decides how and why Lettrim processes personal data and is responsible for responding to privacy requests. In this policy, “Lettrim”, “we” and “us” refer to that operator and the service.

This policy applies when you visit Lettrim, create an account, collaborate, read or publish work, or contact the operator. An external website, sign-in provider or service you choose to use can also process information for its own purposes under its own privacy terms.

We use your email address and a Lettrim account identifier to set up your account and connect it to your work. We also store the username, display name, pen name, profile image, biography, website, location or other profile details you choose to provide. Profile visibility and publishing choices affect which of those details other people can see.

Clerk manages sign-in, verification, credentials and sessions. If you sign in through an external identity provider, Clerk and the provider handle that sign-in and share the identity information needed to connect it to your Lettrim account. Lettrim receives the account and session information it needs to recognize you and check access. For sensitive actions such as account deletion, Lettrim can ask you to re-enter your password and send it to Clerk for verification.

Lettrim stores the preferences needed to run your workspace, which can include writing and display settings, onboarding answers you choose to give, and metadata used to reopen a recently visited project or file.

We store the material you commit or submit to the service, including manuscript text, files and folders, references, project descriptions and briefs, and the images or documents you upload. An import can create files and versions from the material you supply. The service may retain an original upload where that feature is enabled.

Version history records changes, branch and file structure, commit messages, contributor information and timestamps. Reviews, comments, tasks, invitations, roles and project activity may be stored with the relevant project so collaborators can work together and understand what changed. A deleted or renamed file can still appear in retained versions.

Only include personal information about other people when you have the right to use it. Manuscripts, review comments and attachments can contain sensitive information even when the profile fields are ordinary. Check the document and its history before inviting people or enabling public access.

While you type, Lettrim can keep a recovery copy in the browser associated with your account. Recovery is specific to that browser and device. Making a deliberate commit sends the selected work to Lettrim for versioned storage. Importing a file, uploading an attachment, submitting a comment or publishing an edition also sends the material needed for that action to the service.

Browser recovery can be lost if you clear site data, switch devices or browsers, use a private window, or hit a storage limit. You can inspect, download or clear recovery drafts in Settings where available. Clearing a browser recovery copy and removing a committed version are separate actions. Account deletion may leave local copies on devices you used.

New projects are private by default. Access to a private project depends on membership, the permissions assigned to each person, and the rules for its workspace. An authorized collaborator may see your byline, comments, changes and activity related to that project. Removing someone’s access prevents future use of that permission. They may still have a copy they already received or downloaded.

The operator asks your permission before opening a private manuscript to help with a support request. Limited access without advance permission may be necessary to respond to a security incident, recover the service in an urgent failure, or comply with a legal obligation. In those situations the operator limits access to what is needed and informs you when it is lawful and safe to do so.

The service and its infrastructure providers process private content to store, retrieve, verify and deliver it as part of operating the workspace. The permission rule above concerns human access by the operator.

Making a project public can expose its files, folders, committed alternate drafts and revision history to signed-out visitors. Names or pen names, commit messages, dates and earlier versions can be visible too. Review the branches and history as well as the current text before you make this choice.

Publishing an edition uses a separate reader-facing view. The current edition reader requires sign-in. Its content and byline are shown through that view, and where you enable writing-process sharing, eligible edition history can be visible as well. A project that you also make public has the broader access described above.

When you allow readers to fork an edition, an eligible reader can make a private copy of the published snapshot. Copying is off by default. Unpublishing an edition, making a project private or disabling future copying affects access through Lettrim going forward. Copies already made, exports and copies held outside the service may remain.

We may process connection and request information such as IP addresses, request timing, session information, rate-limit records, permission checks and audit events to authenticate requests, investigate abuse, diagnose failures and protect the service. Operational records are separate from optional product analytics.

If you send a support request, privacy request, appeal or report, we may retain your contact details, the correspondence, the material you choose to submit and our response. A report submitted through an edition’s reporting feature can be visible to the owner in the edition’s moderation queue. Share only the details necessary for your request, especially where it concerns a private manuscript or another person.

We use account and project information to provide sign-in, save and deliver writing, manage permissions, support collaboration, generate exports and carry out visibility or publishing choices. We use limited operational records to secure the service, troubleshoot failures, respond to reports, and keep records needed for legitimate disputes or legal obligations.

Where law requires a legal ground for processing, the relevant ground depends on the purpose and jurisdiction. It may be performance of the service you requested, compliance with a legal obligation, a permitted interest such as preventing fraud or securing the service, or consent. Where consent is required, we seek it before carrying out the relevant processing and give you a way to withdraw it. Withdrawal applies to processing going forward.

When product analytics is enabled, PostHog EU receives a limited set of completed workflow events, such as signing up, creating or importing a project, committing a version, opening a review, merging a draft and exporting a manuscript. An opaque Lettrim account ID lets us understand whether the same account completes a workflow or returns later.

Lettrim filters the analytics payload to exclude manuscript text, review comments, titles, filenames, emails, names, usernames and page URLs. Automatic interaction capture, page-view collection, session replay, console capture and exception capture are disabled in this integration. The analytics network request still reaches the provider’s infrastructure.

The current application configuration enables product analytics for signed-in accounts with no saved browser preference. Rollout depends on local requirements, including whether prior consent is needed. In Settings → Your data you can change the preference for your browser. Lettrim honors Do Not Track and Global Privacy Control. Turning collection off stops future events. Earlier events are handled through retention and erasure procedures.

Sign-in uses essential session and security storage. Lettrim can also use browser storage for writing recovery, display preferences and the analytics choice. The analytics integration keeps the analytics account identifier in memory during use and stores your preference in the browser. Clearing browser storage can reset that preference and remove local recovery drafts.

You can manage site storage from your browser. Blocking essential storage can affect sign-in and recovery. Use the in-app analytics control or your browser’s privacy signals to manage optional product analytics.

Clerk provides account authentication. Lettrim uses managed PostgreSQL infrastructure, currently Neon in its documented setup, for application data. Cloudflare services support hosting and versioned manuscript storage through Artifacts where configured. Cloudflare R2 can store uploaded files when enabled. PostHog EU processes the limited analytics events described above when collection is enabled.

Providers receive the information needed for the service they supply. People you give access to receive the project information their permissions allow. Readers receive information through the public features you enable. Lettrim may disclose information when legally required, or where permitted and necessary to address a serious security or safety issue.

Lettrim does not sell your personal data. The recipient list and provider locations should be read against the configuration of the hosted service you are using.

The operator is based in India and intends to make Lettrim available internationally. Hosting, authentication, storage and analytics providers may process data in other countries. A provider’s storage region and the places from which support or infrastructure can access data may differ.

Where transfer rules apply, the final notice will identify the relevant providers, locations or categories of locations, and any safeguards used for restricted transfers. We will explain how you can request information about those safeguards.

Lettrim will never train AI models on your writing or personal data. This commitment covers public and private writing. Publishing a project or edition does not give Lettrim permission to train on it.

If Lettrim offers an AI assistant in the future, it will use only API services whose terms prohibit the provider from training on the writing and personal data submitted through the assistant. Before you use the feature, Lettrim will explain the provider, the information sent to it, the purpose of that processing and applicable retention. Public sharing may allow other people to access the material under the permissions and license you chose.

We retain account and project information as needed to provide the workspace. Retained history is part of a version-controlled project. Archiving keeps the project and its versions, removes public access and pauses editing. Restoring returns the project to the workspace with private visibility.

Different records may have different retention periods. Security records, moderation records, backups and records needed for legal obligations or disputes can remain after ordinary workspace access ends. The production backup, storage cleanup and analytics schedules still need verification before this draft can give time limits.

Settings → Your data offers an account export. Projects also have export options for committed work, including text, Markdown, Word and Git history where available. A project Git bundle can carry version history separately from the account archive. Browser-only drafts can be downloaded through recovery controls when available.

Account deletion removes your active app profile information and owned project records from the workspace, with exceptions for records that must remain. The service attempts separate cleanup of the Clerk identity. If that step fails, the app can show a pending cleanup state. Workspace owners must resolve ownership first, and the current deletion flow requires password verification.

Edits and comments you contributed to someone else’s project can remain so their project and history continue to work. Lettrim uses a deleted-writer label where it previously displayed your account identity. Existing forks, copies on other people’s devices, local recovery data, and retained provider storage or backups may remain. Text you wrote can still contain identifying information even after your account label is removed.

Lettrim intends to include historical analytics erasure in account deletion. The current account-deletion flow stops future analytics for the deleted account but does not automatically erase earlier PostHog events. Those events require separate operator handling. Provider cleanup and backup expiry can take longer than removal from the active workspace.

Depending on where you live and the laws that apply, you may be able to ask for access to personal data, correction, erasure, a portable copy, restriction or objection, or withdrawal of consent. Some jurisdictions also provide grievance, appeal or complaint rights. You may have the right to complain to the privacy authority that applies to you.

Some requests can be made directly in Settings. For other requests, contact the operator once the public channel below is available. Use the email associated with your account where possible and explain the request. We may need to verify that you control the account or are authorized to act for the person concerned. We may limit disclosure to protect other people’s privacy or meet a legal obligation.

Lettrim accounts are intended for users aged 13 or older, subject to local requirements. Lettrim does not routinely collect a birth date at signup. Where a higher age or parent or guardian authorization is required, those requirements apply to the relevant account or feature.

If a parent or guardian believes a child has provided information in circumstances that require action, they can contact the operator. Lettrim will assess the report and take the steps required by applicable law. Collection and use of analytics for young users is subject to applicable child-privacy rules.

The policy date shows when this text was last revised. When we make a material change, we will explain it through the service or another appropriate channel and obtain a new choice when required.

Draft item for completion before publication. Add the operator’s legal name and a monitored contact for privacy requests, grievances and other required notices. Confirm the production providers and locations, retention schedule, analytics rules by launch market, and any jurisdiction-specific disclosures before setting an effective date.