notex privacy policy
Effective October 4, 2026. This policy covers the notex mobile app for Android and iOS, which turns PDFs of notes into LaTeX, and the service behind it. notex is operated by Jacob Wadzinske (“we”).
1. What we collect
| Data | Where it comes from |
|---|---|
| Account identifiers: a user ID, your email address, your name (as your Google or Apple account provides it), the link to your Google profile photo (Google sign-in only) and your Google or Apple account ID | Signing in with Google or Apple. notex has no passwords and accepts no other sign-in method. |
| Your documents: the PDFs you upload, and the LaTeX source, PDF and page-1 thumbnail we generate from them | You, when you create a project |
| Project details: project name, the options you choose (including any notation notes you type), status, page count, error messages, and usage (which model ran, how many tokens, when) | You and the service |
| Credits and limits: your credit balance and a count of conversions started each day | The service |
| Push-notification token for your device, if you allow notifications | Your device, through Expo’s push service |
| Technical logs: the IP address of each request to our servers, the time, the request made, your user ID and project IDs | Our servers, automatically |
We do not use advertising, analytics or crash-reporting tools, we do not track you across other apps or websites, and we do not sell or rent your data. We do not collect your location, contacts, photos library or device identifiers such as advertising IDs.
On your device the app keeps a copy of files you download, thumbnails, copies of PDFs you picked, and your sign-in session; signing out or deleting your account clears them. If you sign in with Apple, the app also keeps the name and email address Apple shares on your first sign-in (Apple shares them only once) in the device’s secure storage; signing out keeps them, deleting your account clears them.
2. How we use it
- To provide the service: sign you in, store your projects, convert your PDFs to LaTeX with an AI model, and show you the results.
- To run the credit system and limits: charge and refund credits, cap conversions per day, and allow the free starter credit only once per Google or Apple account.
- To notify you when a conversion finishes, if you allowed notifications.
- To keep the service secure and working: prevent abuse and investigate errors, using the technical logs.
Your documents are sent to the AI model only to convert them. We do not use your documents to train models.
3. Who processes it for us
These providers process data on our behalf, only to run notex:
- Google Firebase Authentication (Google LLC): signs you in with Google or Apple and holds your sign-in account (user ID, email, name, Google profile-photo link, linked Google or Apple account).
- Amazon Web Services (Amazon Web Services, Inc.), in the United States (region us-east-2, Ohio): stores your profile and projects (Amazon DynamoDB) and your files (Amazon S3), runs the API (API Gateway, AWS Lambda) and the conversions (AWS Batch), and keeps the logs (Amazon CloudWatch).
- Amazon Bedrock (AWS), running Anthropic’s Claude model: reads the page images of your PDF and the options you choose (note type, organization level and any notation notes) and returns LaTeX; when the LaTeX needs a correction, the request also includes your project name, which is the document’s title. Requests go through a United States cross-region profile, so they may be processed in us-east-1, us-east-2 or us-west-2.
- Expo push service (650 Industries, Inc.) with Firebase Cloud Messaging (Google) and the Apple Push Notification service: issue your device’s push token and deliver notifications. A notification carries a fixed message (“Conversion finished” or “Conversion failed”) and the project’s ID, never your project name or document content.
- Google Sign-In and Sign in with Apple: confirm your identity to Firebase when you sign in. Their own privacy policies apply to your Google or Apple account.
We may disclose data if the law requires it. If notex is transferred to another operator, this policy continues to apply to data collected under it.
4. How long we keep it
| Data | Kept |
|---|---|
| Uploaded PDFs | 30 days after upload (long enough to re-run a conversion), or until you delete the project or account |
| Generated LaTeX, PDF and thumbnails; project details | Until you delete the project or your account |
| Profile (email, credits, push token) and sign-in account | Until you delete your account |
| Technical logs (IP address, user ID, project IDs) | 90 days |
| Daily conversion counter | About 3 days |
| Previous versions of stored files | Up to 30 days after a file is replaced, deleted or expires (so an uploaded PDF can exist for up to about 60 days in total) |
| Database backups | 35 days (point-in-time recovery) |
| Pseudonymous starter-credit marker (see below) | Indefinitely |
5. Deleting your account and data
You can delete a single project in the app (open it, tap Delete), or your whole account: Account › Delete account. You can also ask us by email, without the app; see Delete your notex account for both ways.
Deleting your account removes your sign-in account, your profile, every project and its files, and any remaining credits (credits are forfeited). Uninstalling the app does not delete your account.
What remains after deletion, and for how long:
- Previous versions of your files in storage, for up to 30 days (a PDF still uploading when you deleted the account, for up to about 60 days).
- If a device is still signed in to your account during the hour after deletion (for example another phone you did not sign out of), it can create a new empty profile with your email address and no credits. It is not removed automatically; email us and we will delete it. Sign out of notex on your other devices before deleting to avoid this.
- Database backups, for up to 35 days.
- The daily conversion counter (user ID, date, count), for about 3 days.
- Technical logs with your user ID, project IDs and IP addresses, for up to 90 days.
- Conversion job history (project ID, user ID) held by AWS Batch, until the service removes it automatically.
- A pseudonymous identifier kept to prevent repeat free-credit sign-ups: a one-way hash of your Google or Apple account ID, with no email, name, user ID or date, kept indefinitely so that a deleted and re-created account gets no second free starter credit. Anyone who already knows your Google or Apple account ID could compute the same hash.
6. Security
All traffic between the app and our servers uses HTTPS. Every request is checked against your Firebase sign-in, and you can reach only your own projects. Files are encrypted at rest in Amazon S3, and file links the app receives expire after a short time. No method is perfectly secure, but we work to protect your data.
7. Children
notex is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has given us data, contact us and we will delete it.
8. Your choices
- Notifications are optional: refuse or turn them off in your device settings; the app still works.
- You can delete projects or your account at any time (section 5).
- You can ask us for a copy of your data, or to correct it, by email. Wherever you live, you can also ask us to delete your data or to stop using it; we answer within 30 days.
9. Changes to this policy
If we change this policy we will update the effective date above, and for significant changes tell you in the app or by email before they apply.
10. Contact
Jacob Wadzinske · support@notex.us