← Overview
<aside> 🔒
With the default engine, converting your document happens entirely in your browser — your notes are never sent to an Obsitex server.
</aside>
The default Native engine runs the whole Markdown→LaTeX conversion locally in your browser. Your content leaves your device only when you choose to export it (to Overleaf, GitHub or OneDrive).
If your project folder is on your local drive, Obsitex opens it through the browser's File System Access API. You pick the folder yourself, access is read-only, and nothing leaves your device until you export. No Microsoft account is involved.
If your project folder is on OneDrive, Obsitex asks for two Microsoft permissions — and only the ones you actually need:
| Permission | Why |
|---|---|
| Read access to your OneDrive files | To read your vault's Markdown files for 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. |
Signing in with Microsoft establishes only your identity — it requests no file access by itself. File permissions are granted separately, in the M365 Permissions & Storage dialog, and only when a feature needs them.
You can permanently revoke Obsitex's access at any time via your Microsoft account settings (account.microsoft.com). Microsoft removes all granted permissions at once.
<aside> 📸
Screenshot needed: the "M365 Permissions & Storage" dialog showing the two permissions and the temporary-storage selector.
</aside>