Privacy Policy
Effective date: 13 November 2026
This Privacy Policy explains what happens to your data when you use Obsitex, available at https://www.obsitex.com (“the Service”). Obsitex converts the Markdown notes of an Obsidian vault into a LaTeX document.
Your notes are converted entirely inside your browser. They are never sent to an Obsitex server. Your content leaves your device only when you choose an export, and then it goes to the destination you picked.
1. Who is responsible
Obsitex is operated by Gregor Masshardt. For any question about this policy or about your data, please write to support@obsitex.com.
2. Conversion happens in your browser
The conversion from Markdown to LaTeX runs locally, in the browser tab you have open. Obsitex has no server that receives your notes, your attachments or the LaTeX document it produces. Nothing is stored on our side for the purpose of converting.
3. Signing in
You can sign in with a Microsoft account or with a Google account. Both are equal options. Obsitex requests three standard pieces of information from either provider: your account identifier, your name and your e-mail address (the scopes openid, profile and email).
Signing in tells Obsitex who you are. By itself it grants no access to any of your files, with neither provider. Obsitex never receives your password. The sign-in is handled by Microsoft, respectively by Google, and Obsitex only receives the resulting token in your browser.
Your name and e-mail address are used for two purposes: to show who is signed in, and to recognise your subscription (see section 7). They are kept in the memory of your browser tab for the duration of your session.
4. Reading a folder on your own drive
If your vault is on your local drive, Obsitex opens it through the browser's File System Access API. You pick the folder yourself, the access is read-only, and nothing leaves your device. No Microsoft or Google account is involved in this path. Your browser remembers which folder you picked, so that you can open it again on your next visit (see section 11).
5. Reading a folder on OneDrive
Using OneDrive is optional. If your vault is stored there, Obsitex asks for Microsoft permissions, and only for the ones the feature you use actually needs. Each permission is requested separately, the first time it is needed, not at sign-in.
| Permission | Why |
|---|---|
| Read access to your OneDrive files | To read the Markdown files of your vault for the conversion. Obsitex does not modify or delete your notes. Only requested if you pick your vault from OneDrive. |
| Access to the app's folder in OneDrive | To store temporary files and exports in the app folder /Apps/Obsitex/. Only requested if you use OneDrive for storage or export. |
6. Exporting your document
You choose the destination of an export, and that choice decides where your content goes:
- Browser download. The ZIP archive is built in your browser and saved to your device. Nothing is transmitted anywhere.
- OneDrive. The files are written to your own OneDrive, into the app folder /Apps/Obsitex/, using the permission described above.
- GitHub. If you connect a GitHub account, the files are written to the repository you name. The connection uses GitHub's OAuth flow. One of our backend functions (section 10) exchanges the one-time code from GitHub for the access token and hands the token straight back to your browser. It neither stores nor logs the token. The token stays in the memory of your browser tab and is discarded when you close it.
- Overleaf. Overleaf can only import a project from a public web address. Obsitex therefore uploads the ZIP archive to a temporary storage bucket on Amazon S3, under a random name that cannot be guessed, hands the address to Overleaf, and deletes the file again a few seconds later. This is the one export path in which your content passes through our infrastructure. If you would rather it did not, use one of the other three.
7. Payment and subscription
Payments are handled by Stripe. Obsitex never sees your card details. Stripe holds the customer record, which contains your name, your e-mail address and an account key derived from your sign-in. Obsitex uses that key to answer one question: does this person have an active subscription.
When you start your first purchase, a short notification with your name, your e-mail address, your Stripe customer number and your account key is sent to the operator by e-mail (through Amazon SES). It makes new customers and problems with a purchase visible. Error reports from the purchase step are sent the same way.
Stripe processes this data as an independent service. Their privacy statement applies in addition to this one and is available at stripe.com/privacy. For the cookies Stripe sets when you open the site, see section 11.
8. What we keep about you
Obsitex has no account database, no profile store and no archive of documents. Outside your browser, data about you exists in three places only:
- the customer record at Stripe, once you have started a purchase (section 7);
- the e-mail notification about that purchase in the operator's mailbox (section 7);
- the operational logs of our backend (section 10).
9. Services your browser contacts when you open the site
Opening www.obsitex.com makes your browser fetch parts of the page from other providers. Each of them receives your IP address and the technical information every browser sends with a request, such as the browser type and language. None of them receives your notes.
| Provider | What for |
|---|---|
| GitHub Pages (GitHub) | Hosts the website. GitHub logs the IP address of every visitor for security purposes. |
| Google Fonts (Google) | Delivers the typeface of the site. |
| Google Sign-In (Google) | Loaded on every visit, so that signing in with Google is ready. Your account data is only involved when you actually sign in (section 3). |
| jsDelivr, unpkg and cdnjs (Cloudflare) | Deliver three program libraries: Microsoft sign-in, OneDrive access and the creation of ZIP archives. |
| Stripe | Loads the payment library Stripe.js on every visit (section 11). |
| YouTube (Google) | Shows the video on the start page (section 11). |
| hits.sh | Counts visits, sign-ins, conversions, template downloads and views of the sample thesis (section 11). |
10. Our backend, and what it is for
A small set of AWS Lambda functions in the region us-east-2 (Ohio, United States) supports the app. They do five things: they ask Stripe whether a subscription is active, they open the Stripe checkout and the Stripe customer portal, they hand out the short-lived upload address for the Overleaf path, they delete that temporary file again, and they complete the GitHub connection (section 6). They receive the account key and, when a purchase is started, your name and e-mail address. They never receive your notes.
Operational logs of these functions are stored in Amazon CloudWatch, so that failures can be diagnosed. They may contain the account key, the e-mail address, and the IP address and browser identification that came with the request.
11. Cookies, counters and storage in your browser
Obsitex itself sets no cookies, shows no advertising and builds no profiles. Some of the services it uses do store or count something:
- Stripe. Stripe.js is loaded on every page, so that the checkout can start at once. On every visit, also if you never buy anything, it sets two cookies on www.obsitex.com, __stripe_mid (kept for one year) and __stripe_sid (kept for 30 minutes), and one cookie on its own domain m.stripe.com. Stripe uses them to prevent fraud.
- YouTube. The videos on the start page are embedded in YouTube's privacy-enhanced mode (youtube-nocookie.com). Your browser loads the player when the page opens, so Google receives your IP address. When you play a video, YouTube's privacy statement applies.
- hits.sh. To see whether the Service is used, Obsitex counts five events with the open-source counter hits.sh: a page view, a successful sign-in, a successful conversion, a downloaded template and an opened sample thesis on the start page. The request carries only the name of the event, no information about you and no referrer. Like every web server, hits.sh receives your IP address. hits.sh publishes no privacy statement of its own. You can switch the counting off for your browser: open www.obsitex.com/?notrack=1 once. Opening ?notrack=0 switches it on again.
- Your settings. Obsitex keeps your settings in the local storage of your browser, so that they are still there on your next visit: your document settings, the converter you chose, the folder you opened last, the names of your GitHub repository and project, which sign-in provider you used last, and whether you switched the counting off.
- Temporary files. The intermediate files of a conversion, and a reference to the folder you picked on your own drive, are kept in your browser's IndexedDB. Unless you choose OneDrive for temporary files in the settings, none of this leaves your device.
Your settings and temporary files stay until you delete them: clear the site data of www.obsitex.com in your browser. The sign-in itself lives in the session storage of your browser tab and ends when you close it.
12. Where your data is processed
Most of the providers named in this policy are based in the United States, and your data may be processed there: GitHub, Google (including YouTube), Microsoft, Stripe, Amazon Web Services and Cloudflare. The delivery networks jsDelivr and unpkg serve their files from locations around the world. hits.sh does not say where it runs. Each provider's own privacy statement applies in addition to this one:
- GitHub
- Google and YouTube
- Microsoft
- Stripe
- Amazon Web Services
- Cloudflare
- jsDelivr
- Overleaf (only if you export there)
- hits.sh (source code, no privacy statement)
13. Withdrawing access
You can revoke the access of Obsitex at any time, from the account you used:
- Microsoft: account.microsoft.com/privacy/app-access
- Google: myaccount.google.com/permissions
- GitHub: in your GitHub account settings, under Applications
Revoking removes all permissions granted to Obsitex at once. To remove what Obsitex keeps in your browser, clear the site data of www.obsitex.com (section 11). To have the Stripe customer record deleted as well, please write to support@obsitex.com.
14. Your rights
You may ask what data about you exists, ask for it to be corrected, or ask for it to be deleted. Because Obsitex keeps no user database, such a request concerns the three places named in section 8: the customer record at Stripe, the notification about your purchase and the backend logs. Send it to support@obsitex.com and it will be answered.
15. Changes to this policy
This policy may be updated. The effective date at the top shows the current version. Users will be notified via the website or by e-mail when a material change occurs.
16. Contact
For questions regarding privacy, please contact: support@obsitex.com
See also our Terms of Service.