How TeXAnt handles your data.
Last updated: October 4, 2026
TeXAnt is built local-first. Your writing, your compilation and your PDF output all happen on your device, inside an embedded LuaTeX engine, not on our servers. Data leaves your device in only three situations, and this page describes each one: optional diagnostics you switch on, purchase verification if you buy TeXAnt Pro, and features you explicitly invoke that talk to a third party of your choosing.
Your documents stay on your device
TeXAnt servers never receive your document content, your compiled PDFs, your file names or your project metadata. Compilation runs entirely offline against the LuaTeX engine bundled in the app. Math OCR, which turns a photographed equation into LaTeX, also runs on the device. Its recognition model is downloaded once and then kept locally; your image is never uploaded.
Optional diagnostics (off by default)
Diagnostics and telemetry are opt-in and disabled until you turn them on. When enabled, the app may send:
- Device model, operating system version, and screen resolution or display density
- Theme preference, interface language, and editor or app settings
- Package and font data: installed items and install-failure diagnostics such as package or font names and error details
- Crash reports and error diagnostics (crash signature hash, error code, and a sanitised stack trace)
This data is anonymous. It is tied only to a random per-install identifier, never to an account or a personal identity. TeXAnt uses no third-party analytics or crash-reporting SDK: there is no Sentry, Crashlytics, Firebase or comparable service in the app. Diagnostics go only to TeXAnt's own infrastructure over HTTPS.
Toggle: Settings → About → Privacy & Legal.
Separately from this toggle, a message you choose to send through the in-app feedback form is delivered when you tap Send, together with the same per-install identifier, the app and OS version and your subscription tier. The app does not attach your name, email address or any device advertising identifier.
Purchase verification (required for TeXAnt Pro)
If you buy a subscription or the lifetime licence, the app must verify that purchase. This is not optional and is not covered by the diagnostics toggle. For verification we process an Apple App Attest key identifier and assertion, the App Store transaction identifier, and the purchased product identifier, in order to issue a device-bound entitlement.
We never receive your name, email address, billing address or payment details. Payment is handled entirely by Apple; card data never reaches TeXAnt.
Features that contact third parties when you use them
Some features exist specifically to connect your work to a service you have chosen. In each case the connection is made because you asked for it, and the third party's own privacy policy applies to what they receive.
- AI assistant. Disabled until you supply your own API key. When you use it, the text you select or the document excerpt you submit is sent to the provider you configured (OpenAI, Anthropic, Google Gemini, OpenRouter or NVIDIA) under your own account and their terms. Your key is held in the device's secure storage. TeXAnt's servers are not part of this request and never see the content.
- Cloud storage. iCloud Drive, Google Drive, Dropbox, OneDrive, Box, Yandex Disk, Amazon S3 and Overleaf. Files sync to your account; access tokens are stored on your device. Two things involve TeXAnt's backend. For Box and Yandex Disk, the one-time sign-in code is exchanged for a token by our backend, so the provider's client secret never ships in the app; the token is passed straight back to your device and is not stored on our servers. For Amazon S3, the backend issues short-lived, scoped credentials instead of keeping long-lived keys on the device.
- Git. Clone, commit, push and pull go directly to the remote repository you configure.
- Reference managers. Zotero, Mendeley and EndNote credentials are stored on your device, and imports go directly to those services. As with Box, the Mendeley sign-in code is exchanged for a token by our backend without the token being stored there.
- Package and font installation. Missing LaTeX packages and fonts are downloaded from public CTAN mirrors. The mirror sees your IP address and the name of the package requested.
This website's contact form
When you send the form on the Contact page, we receive your name, email address, organization (if given) and message, and use them only to answer you. The message is delivered to our support mailbox and may be kept on our server together with a one-way hash of your IP address, which we use to stop abuse. To keep out spam, the form uses Google reCAPTCHA, which is loaded only on that page and is covered by Google's Privacy Policy and Terms of Service. Ask us at the privacy address below and we will delete your message.
Cookies
This website does not set any cookies and uses no analytics or advertising trackers, so there is no cookie banner to accept. Your light or dark theme choice is saved in your browser's local storage and never leaves your device. Fonts are loaded from Google Fonts, which receives your IP address as part of the request but sets no cookies. The only exception is the Contact page: when you start filling in the form, Google reCAPTCHA is loaded and Google may set its own cookies for that check.
Device permissions
Every permission below is optional, is requested only at the moment you first use the feature that needs it, and can be revoked at any time in iOS Settings.
- Camera: photographing an equation for Math OCR. Recognition runs on the device; the image is not uploaded.
- Photo library: choosing an equation image for Math OCR or inserting a figure into your project. Processed locally.
No tracking, no advertising
We do not track you across other companies' apps or websites. No advertising identifier is used, no ad network receives anything, and we do not sell or rent data to anyone. Because TeXAnt does not track, it never shows the iOS App Tracking Transparency prompt, and its privacy manifest declares no tracking and no tracking domains.
Transport and retention
Everything the app or this website sends travels over HTTPS, with one exception we cannot control: EndNote's sign-in pages, run by Clarivate, redirect through plain HTTP addresses, so the app allows HTTP for those two Clarivate domains only. Information is processed only for the purposes described here and is kept only as long as reasonably necessary for those purposes, for support, or to meet a legal obligation. After that window, records are deleted or anonymized.
Your rights (KVKK & GDPR)
You may request access to, a copy of, correction of, or deletion of the data associated with your installation, and you may object to processing. Requests are answered within 30 days.
- In-app: Settings → About → Privacy & Legal → Request Data Deletion / Request Data Export
- By email: privacy@texant.app
Data controller
TeXAnt is an independent product built and operated by a solo developer based in Türkiye, who is the data controller for the processing described on this page. TeXAnt is not a company; there is no corporate entity behind it and no staff other than its developer. The developer's identity and address are verified by Apple as part of App Store seller registration, and the developer's legal name is shown as the seller on the TeXAnt App Store listing. If you need those registered details in writing for a formal request, ask at the address below and they will be provided.
For any privacy question, or to exercise the rights described above, write to privacy@texant.app. Messages are answered by the developer personally.
Children
TeXAnt is a professional authoring tool and is not directed at children under 13. We do not knowingly collect personal data from children.
Updates
This page may be updated as the app and supporting services evolve. Material changes will be reflected by publishing an updated version here with a new revision date.