Legal

Privacy Policy

This policy explains what Reltext stores, why it is needed, and how you can remove it.

Effective November 20, 2026

What Reltext stores

Reltext is a personal blog writing and publishing tool operated by an individual developer. We store the following data to provide it:

  • Account: the name you give when you sign up (used to greet you, for example in your first draft), your email address and a password stored as a secure hash by our authentication provider. Reltext uses email-and-password accounts only; there is no social login.
  • Writing data: your drafts, draft version history and site configuration.
  • Media: images you upload for drafts, stored under a folder only your account can access. Before an image is uploaded, Reltext removes location and other camera metadata from the file, so the stored copy does not record where a photo was taken.
  • Publishing records: when you explicitly confirm a publish, the publish job and a frozen copy of its content for processing and troubleshooting.
  • GitHub connection metadata: the installation ID, account name, permission summary and connection status. We do not store long-lived GitHub tokens; publishing uses short-lived, single-repository tokens issued at publish time.
  • Subscription information: if you subscribe to Reltext Pro, we store your plan, the status of your subscription, the current billing period, whether the subscription is set to renew, the store through which you purchased it, and whether your account has used its free trial. Payments are processed by Apple or Google; we do not receive or store your payment card details.
  • Security logs: the IP address and time of sign-in and other account events, kept by our authentication provider to protect your account.
  • Device ID: a random identifier created by each browser or app installation, sent with your saves so that edits from the same device can be grouped into versions. It is not used to track you.
  • Sessions: the Web app uses session cookies and short-lived signed cookies; the Mobile app uses session tokens held in the device's secure storage. These exist only to keep you logged in and protect the GitHub connection flow. Reltext does not use advertising or cross-site tracking cookies.

What Reltext does not collect

  • No behavioral analytics, advertising identifiers or tracking SDKs.
  • No connected crash-reporting service in this version.
  • No payment card or other payment details. Payments for Reltext Pro are processed by Apple or Google, and we receive only the subscription information described above.

Your content and AI

Reltext has no AI features. We do not use your drafts, images or published posts to train machine-learning models, and we do not give them to anyone else to do so.

Responsibility and legal basis

The data controller is LI ZHIWEN, the individual developer who operates Reltext, at Room 2707, Unit 2, Building 11, Zijingcheng Phase 2, Datang Village, Xingsha Town, Changsha County, Changsha, Hunan 410100, China. Contact: support@reltext.com. We process data to perform our contract with you by providing the service, and for our legitimate interest in securing and operating it. We do not sell personal data.

How we share information

Reltext does not sell personal data and does not share it for advertising purposes. Personal data is shared only in the circumstances described below.

  • Service providers. The following providers process personal data on our behalf to operate Reltext. They may process it only to provide their services to us, as set out in their terms and data processing agreements.
    Supabase
    Database, authentication and file storage, hosted in Singapore (ap-southeast-1).
    Vercel
    Hosting and delivery of the Web application.
    Cloudflare
    Bot protection (Turnstile) on sign-in, registration, password reset and account re-authentication in settings, which receives technical information from your browser or device, such as your IP address and browser characteristics, to distinguish people from automated traffic; the infrastructure that runs the publishing worker, which handles the content you confirm for publishing; and storage of encrypted backups (R2, Asia-Pacific region), which Cloudflare cannot read.
    GitHub
    Runs the daily backup job, which copies the database and uploaded images and encrypts them before they are stored; the job keeps no copy after it ends.
    Resend
    Delivery of account and authentication emails, sent from auth.reltext.com.
    RevenueCat
    Management of subscriptions purchased through the App Store and Google Play. RevenueCat receives your Reltext account identifier, a random identifier that does not contain your email address, technical device information such as IP address, device model and app version, and the store's transaction records.
    Apple and Google
    Payment processing for subscriptions purchased through their stores, governed by their own terms and privacy policies.
  • At your direction. When you confirm a publish to a GitHub repository you own, the post and the images it uses are transferred to that repository. When you export a draft, the file is created for you and goes only where you choose to save or send it. No other data is included.
  • Legal requirements and safety. We disclose personal data where required by applicable law or legal process, or where disclosure is reasonably necessary to protect the safety or rights of any person.
  • Transfer of the service. If Reltext is transferred to another party, personal data may be transferred as part of that transaction and will remain subject to this policy. We will notify you before any such transfer so that you may delete your account.

International data transfers

Account data, drafts and images are stored in Singapore. Some of the service providers listed above, including Vercel, Cloudflare, GitHub, Resend and RevenueCat, process personal data in other countries, including the United States. These transfers are protected by safeguards such as the Standard Contractual Clauses adopted by the European Commission. The developer operates Reltext from China and may access personal data from there to operate and support the service; database backups made before maintenance are also stored there.

Publishing and device data

When you confirm a publish, the post and the images it uses are committed to your own GitHub repository and may become publicly visible through your own site. Content published there is under your control, not ours; deleting your Reltext account does not delete content already committed there.

The Web app keeps an unsaved copy of the draft you are editing in this browser's local storage, so a closed tab or a lost connection does not lose it. The Mobile app stores recovery files, so that unfinished writing survives interruptions, and copies of your drafts and their images, so that they can be read and edited offline. Signing out removes the offline copies of drafts and images; it keeps recovery files, including any edits not yet uploaded. Settings > Storage & data > Clear local data on this device removes both for that account.

Account deletion

You can delete your account in Account settings on the Web, or under Settings > Account > Delete account in the Mobile app. Deletion is immediate and irreversible:

  • All drafts, version history, media files and stored objects, sites, publish records, subscriptions, GitHub connection metadata and the login identity are permanently deleted.
  • A pseudonymous deletion receipt, containing a one-way hash of your account identifier and no email address, name or content, remains as proof that deletion completed.
  • Deleting your account does not cancel a Reltext Pro subscription. To stop future charges, cancel the subscription in your App Store or Google Play settings before you delete your account.
  • We retain a log of subscription events (event type, time and processing result), which contains no email address or content. Your customer record at RevenueCat (account identifier and purchase history) is deleted as part of account deletion. Apple and Google retain their own transaction records in accordance with their legal and tax obligations.
  • Uploaded media files cannot be restored to your account. Encrypted backups may hold copies for up to 90 days, as described under Backups.
  • Content already published to your GitHub repository is not touched.
  • Local files may remain on devices you used until removed there.

Read the public account deletion instructions.

Retention

We keep your data for as long as your account exists, with the following exceptions:

  • Drafts in Trash are permanently deleted 30 days after they are moved there.
  • Saves from the same device within about 10 minutes are kept as a single version in version history. Each draft keeps up to 200 versions, and when an account's draft storage limit (50 MB on Reltext Free, 500 MB on Reltext Pro) is reached, the oldest unreferenced version history is deleted first to make room for new saves.
  • A new draft that was never edited is deleted after 24 hours. A draft whose title and text were removed entirely, and that is not edited for 7 days, is moved to Trash.
  • What remains after account deletion is described under Account deletion above; database backups are described under Backups below.

Backups

We keep private backups of the database and uploaded images for disaster recovery. Every day a copy is encrypted before it is stored with Cloudflare R2 in the Asia-Pacific region; only the developer holds the key that can read it. Copies of the database made before maintenance are also stored on storage controlled by the developer in China. Backups are deleted within 90 days, so deleted data may persist in them for up to 90 days. Backups are not used for any other purpose.

Children's privacy

Reltext is not intended for children under 13, or the higher minimum age required in your jurisdiction, such as 16 in parts of the EU. We do not knowingly collect personal data from children. If you believe a child provided us personal data, contact support@reltext.com and we will delete it.

Your rights and contact

You may request access to, correction of or deletion of your data at any time. Depending on where you live, you may also have the right to data portability, to object to or restrict processing, and to lodge a complaint with your local data protection authority. You can export your drafts at any time, as described in the user guide. You can delete your account yourself on the Web or in the Mobile app, as described above. For any other request, contact support@reltext.com.

Changes

We will update this policy when the facts change, such as when a new service provider or diagnostic service is introduced, and revise the effective date above. Material changes will be announced in the app or on the website before they take effect.

This Privacy Policy shall be governed by and construed in accordance with the laws of Singapore.