Privacy Policy

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: 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.
• 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.
• 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 data; this version of Reltext is free.

Responsibility and legal basis

The data controller is the individual developer operating Reltext. 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.

Where data is processed

Supabase

Database, authentication and file storage, hosted in Singapore (ap-southeast-1).

Vercel

Web application hosting and delivery.

Cloudflare

Publish worker infrastructure.

Resend

Transactional authentication emails, sent from auth.reltext.com.

GitHub

Publishing content you explicitly confirm to a repository you own and control.

Publishing and device data

When you confirm a publish, the selected content is written 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 Mobile app keeps local copies of drafts and recovery files so unfinished writing survives interruptions and offline use. Signing out intentionally does not delete these files. A dedicated remove local data from this device action is planned but has not shipped.

Account deletion

You can delete your account from Settings > Delete account. 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.
• An anonymized deletion receipt, containing a one-way hash with no email, name or content, remains as proof that deletion completed.
• Uploaded media file contents cannot be recovered.
• 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.

Backups

We keep periodic private database backups for disaster recovery. Deleted data may persist in backups for up to 90 days before those backups are rotated out. 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, correction or deletion of your data at any time. The fastest deletion path is the in-app action described above. For anything else, email support@reltext.com.

Changes

We will update this policy when the facts change, such as when a new processor or diagnostic service is introduced, and revise the effective date above.