Privacy Policy

• We collect the minimum needed to run an account: your email address, whatever profile details you choose to add, and the content you upload.
• There are no passwords to leak, because we do not use them. Sign-in is a one-time code sent to your email.
• Your documents are never used to train machine-learning models, ours or anyone else's.
• We do not sell personal data, and we run no advertising or cross-site tracking.
• You can export everything as JSON, or delete the account outright, from your settings, without emailing anyone.

Account data

Your email address, which is how the account is identified. A display name, and optionally a bio, affiliation, location and avatar if you choose to fill them in. None of the optional fields are required to use the service.

Content

Projects, LaTeX source, uploaded images and PDFs, compiled output, and the documents you create. This is stored so we can give it back to you.

Technical and security data

For each active session we record the IP address, browser, operating system and approximate location, so you can review your sessions and spot one you do not recognise. We also keep an audit log of security-relevant events (sign-ins, failed sign-in attempts, account changes, deletions), which is what makes it possible to investigate if an account is compromised.

Usage counters

Monthly totals of image conversions and PDF pages, used to enforce plan limits and to render your statistics page. These are counts, not copies of the content.

Payment data

If you subscribe, Stripe handles the transaction. We store your Stripe customer and subscription identifiers, your plan, and invoice records. We never receive or store full card numbers.

Where the UK GDPR or EU GDPR applies, we rely on: performance of a contract, for everything needed to provide the service you signed up for; legitimate interests, for security logging, abuse prevention and aggregate analytics; legal obligation, for retaining financial records; and consent, where we ask for it explicitly, which you can withdraw at any time.

We use a small number of sub-processors. Each receives only what its function requires.

Two things worth being explicit about. First, AI providers only ever receive the specific document or image involved in a request you started. Opening the editor sends nothing. Second, we use these providers under terms that exclude your requests from model training, and we do not use your content for training either. Provider terms change; if that ever stops being true we will say so here and in the changelog before it takes effect.

If none of that is acceptable for your data, self-host. The entire stack is MIT licensed, you can point it at your own AI keys or none at all, and no data leaves your infrastructure.

• Projects and uploads: until you delete them, or delete your account.
• Version history snapshots: 30 days, then deleted automatically. This is a convenience feature, not a backup, so keep your own copies.
• Sign-in codes: expire within minutes and are purged hourly.
• Sessions: until they expire or you revoke them; inactive sessions are cleared after 7 days.
• Security audit logs: retained beyond account deletion where needed to investigate abuse or meet a legal obligation.
• Invoices and financial records: as long as tax and accounting law requires, typically six to seven years.
• Encrypted backups: deleted content can persist in backups for up to 30 days before rotating out.

Depending on where you live you may have the right to access, correct, delete, restrict or object to processing of your personal data, and to receive it in a portable format. Two of these are built into the product rather than requiring a request:

• Export: Settings gives you a JSON file containing your account data, projects and metadata.
• Deletion: Settings deletes the account and its content from the live service. It cannot be undone, so export first.

For anything else, email privacy@texer.org. We aim to respond within 30 days. If you are in the UK or EU and are unhappy with our response, you may complain to your national data protection authority.

We set one essential cookie to keep you signed in. There are no advertising cookies and no third-party trackers.

The marketing site uses a self-hosted Umami instance for aggregate page statistics. It sets no cookies, collects no cross-site identifier, and produces counts rather than profiles, which is why there is no cookie banner asking for your consent to it.

Data is encrypted in transit with TLS. At rest it is stored with providers that encrypt their storage and database volumes; we do not add a separate application-level encryption layer on top, and we say so because “encrypted at rest” on its own tends to imply more than it means. File access uses short-lived signed URLs rather than public links. There are no passwords to leak, and two-factor authentication is available in settings.

What we do not have: a third-party certification such as SOC 2 or ISO 27001. Those are audits of process documentation, and for a project of this size the cost is better spent on the controls themselves. The code is open, so the controls can be read rather than taken on trust.

No system is perfectly secure. If we discover a breach affecting your personal data we will notify affected users and the relevant authority without undue delay, and within 72 hours where the GDPR requires it.

Found a vulnerability? Please report it privately to security@texer.org rather than opening a public issue.

Our sub-processors operate internationally, so your data may be processed outside your country. Where data leaves the UK or EEA we rely on adequacy decisions or Standard Contractual Clauses.

The service is not directed at children under 13 (or under 16 where local law sets that threshold), and we do not knowingly collect their data. If you believe a child has created an account, contact us and we will remove it.

We will update this page when our practices change, and email registered users about anything material. The date at the top always reflects the current version.

Privacy questions: privacy@texer.org. See also the Terms of Service and Refund Policy.