Iron Bind is a writing app for worldbuilders, novelists and game masters, made by AHEM Studios (“we”, “us”), based in Alberta, Canada. Iron Bind is built local-first: your manuscripts, world bibles, maps and notes live on your device and belong to you. This policy explains what information the Iron Bind app, the ironbind.app website and its forms handle, why, who else is involved, and the choices you have.
1. Your Writing Stays on Your Device
- All project data, including manuscripts, Codex entries, maps, timelines, spells, session logs and settings, is stored on your device. On Android it is kept in a SQLite database in the app’s private storage, plus a second, complete copy in the app’s own web storage (IndexedDB) that the app falls back to if the database can’t be read. On the web it is kept in your browser’s storage for the site (IndexedDB and localStorage), which the app asks the browser to keep.
- Your author profile is stored the same way, including any contact details you add for manuscript title pages (legal name, address, phone, email). They appear only in the files you export and in your backups (on a book you write with someone, the backups the app puts in a cloud leave the profile out): the profile stays on your device, and no sync file or passed book carries it (see Sections 3 and 4).
- We don’t run servers that receive or store your writing, and there is no Iron Bind account. This also means we can’t recover your data if your device is lost or the app is removed, so please back up regularly.
- Iron Bind doesn’t encrypt this data itself. It is protected by your device: Android’s app sandboxing, your screen lock and your device’s own storage encryption where it is turned on; in the Windows app, your Windows user account and the drive encryption (such as BitLocker) where it is turned on; or your browser’s site isolation on the web. Anyone who can use your unlocked device, or who has a copy of your backups or exports, may be able to read your projects.
- Permanently deleting a project in the app removes it from both copies on your device. Uninstalling the app, or clearing the site’s data in your browser for the web version, removes everything stored on that device. On Android, if your phone backs up apps to your Google account, Android’s own backup keeps a copy of your projects and the settings the app keeps with them (your Lore Scan key among them), which a reinstall or a new phone restores; the app’s random install id, its license on that device, its cloud sign-ins and its sync state are never in it.
2. AI Features: Lore Scan (Google Gemini, Optional)
- Lore Scan scans your manuscript for names and extracts reference notes about your characters, places and lore. It is optional, and it only works with your own Google Gemini API key, entered in Bindings. Store builds of Iron Bind don’t include an API key of ours.
- Your API key is stored on your device: on Android and the web in the app’s local storage (and, on Android, its database, which Android’s own backup copies if you have it on: see Section 1), not encrypted by the app; in the Windows app, encrypted with Windows’ data protection for your user account. It is never sent to us, only to Google with each AI request.
- When you run an AI feature, the manuscript or entity text it needs, along with your chosen writing genre, is sent directly from your device to Google’s Gemini API. This is the only time your writing leaves your device, apart from backups and exports you start, the sync you turn on for a project (Section 3) and the books you pass (Section 4). It does not pass through us and we cannot see it.
- Google handles that text under the terms for your API key (the Gemini API Additional Terms of Service and Google’s Privacy Policy). On Google’s free (unpaid) tier, Google may use what you send to improve its products, which can include human review; Google says data sent with a paid-tier key is not used that way. Check which tier your key is on, and don’t send anything you aren’t comfortable sharing under those terms.
- Lore Scan is designed to record only what you have already written. It doesn’t invent lore. Extracting notes for an entry sends only the scenes that name it or are told from its point of view, and re-running it merges new facts into your notes, dropping a note only when those scenes no longer support it.
3. Cloud Accounts: Google Drive and OneDrive Backups and Sync (The Astral Link, Optional)
- If you turn on cloud backup or sync, you link a Google account (for Google Drive) or a personal Microsoft account (for OneDrive). You can link more than one account, and each project chooses which linked account it backs up to and syncs through. Iron Bind asks for your basic profile (name and email address) and permission to see and manage only its own files: on Google Drive the files it creates, not the rest of your Drive; on OneDrive its own folder, Apps/Iron Bind, and nothing else in your OneDrive. Work and school Microsoft accounts aren’t supported yet.
- To keep you linked between visits, the app stores on your device the list of linked accounts (which cloud, and each account’s email address and name) and, for each project, which account it uses. Access tokens are kept only on your device and last about an hour: in memory while the app runs, and on Android and the web also in the Google sign-in’s own storage until you disconnect (never in Android’s backup). On Android, Microsoft’s sign-in library keeps its sign-in on the device so OneDrive stays linked. In the Windows app, the sign-in opens in your browser, and the app keeps a refresh token (a credential that renews the access token) for each linked account on the PC, encrypted with Windows’ protection for your user account, so the account stays linked between launches; disconnecting an account removes it.
- Backups are written to your own Google Drive or OneDrive. Each backup is kept with its project’s name and ID (and, on Google Drive, the app version), so the app can find it again on another device: as file tags on Google Drive, in the file and folder names on OneDrive. The app keeps the 20 newest backups of each project and removes older ones it made when you create a new backup. On a project with Co-writing on, these backups (and the one made before a device’s first sync) leave your author profile out, as the account may be one you share; a single writer’s cloud backups keep it. We never receive your credentials or your backups.
- If you turn on sync for a project (Bindings → Backup & Sync), the app keeps one sync file of that project in the account it chose, in your own Google Drive or OneDrive: the project as a backup holds it, a list of what was deleted and when, and the name of the device that last wrote it (such as “Windows PC”; on OneDrive the file’s name carries the project’s name and ID and the device’s name). Once sync is on, the app reads and writes that file by itself: when the project opens, every few minutes while it is open and online, and when the app goes to the background or closes. Before the first sync on a device it saves a backup of the project to that account. The sync file carries no author profile (a sync file an earlier version wrote with one is written again without it); it names the writer who last wrote it (the profile’s name on that device, and that device’s own random id). A pen name a project is written under (its name, bio and photo, in Bindings → Project → Written As) is part of the project and travels with it. On a project with Co-writing on (Bindings → Backup & Sync, for a book two people write through an account they both link), the book’s authors’ names, bios and photos you enter in Bindings → Project → Authors are part of the project and travel with it too, and each scene and comment keeps the name of the writer who last changed or made it, so your co-writer sees your name there. Each device keeps its own note of the last sync. Turning sync off stops it; the sync file stays in your cloud until you remove it (the ✕ beside it in the Library’s On Your Drive, or deleting the project for good on a device that syncs it) or delete it in Google Drive or OneDrive yourself. We never receive it.
- You can disconnect an account in the app, and remove Iron Bind’s access at any time in your Google Account (Security → Third-party apps & services) or your Microsoft account (Privacy → Apps and services, at account.live.com/consent/Manage). Google and Microsoft handle your account and your files under their own privacy policies.
4. Backups and Exports You Control
Project backups and all file exports (PDF, DOCX, EPUB, ODT, dossiers and more) are made on your device. On Android they open your device’s share sheet so you choose where the file goes; on the web they download in your browser. Once you send a file somewhere, that service’s or person’s own policies apply. Pass the Book (Bindings → Backup & Sync → Passing the Book) makes a file of a project for whoever you hand it to: the project as a backup holds it (with its pen name, or a co-written book’s authors and their photos), the deletions since your last exchange, your writer’s name, and this device’s random id and general name (such as “Android phone”). It carries no author profile and none of this device’s own settings (its cloud account, its theme), and it goes only where you send it.
5. When the App Goes Online
Iron Bind’s fonts and code are bundled with the app, so it makes no network requests of its own beyond the ones in this section. It goes online only for the optional AI and cloud (Google Drive, OneDrive) features above, when you use them, to send a report you write (below), to check your Archmage License (below), and to load a font from a Custom Font URL if you enter one in Bindings; like any web request, that server sees your device’s IP address. In the Windows app, the spell checker may download the dictionary for your language from Google’s servers the first time it needs it; that request carries your device’s IP address and the language’s name.
Send a report (in Help, at the foot of Bindings and on the error screen) sends us what you write in it: the kind of report and the part of the app you pick, an optional subject, your message and, if you give them so we can reply, your name and email address. It adds the app version, the page you were on and your device (Android app, Windows app or web browser, the screen size and the browser’s or system’s user-agent text) and, from the error screen or after an error in the last half hour, the error message, which you can leave out. The form lists all of it before you send, and none of your writing or project content is included. Without a connection, the report waits on your device and is sent when you’re back online; Help shows a waiting report and lets you delete it. Your name and email address are remembered on your device for your next report until you clear them. Reports are kept in our internal support tools as Iron Bind bug reports; your name is kept with the report and your email address separately, only our team can see either, and we remove both from a report if you ask. The form can also open your own email app with the same details instead.
The Archmage License. When you enter a license key, buy the license on Google Play or in the Microsoft Store, or restore a purchase, the app sends our license server the key (or, for a Google Play purchase, Google’s purchase token for it and the product; for a Microsoft Store purchase, a Microsoft Store ID key, which the Store makes for the Microsoft account signed in to it and which identifies that account to our app only), a random ID the app makes for this installation (not a hardware ID), a general name for the device such as “Android phone” or “Windows · Chrome”, and the platform. For each license we keep its key, how it was obtained (Google Play, the Microsoft Store, or issued by us), for a Google Play purchase its order number, purchase token and product, for a Microsoft Store purchase the Store’s order and item numbers, the add-on and the Microsoft Store ID key (renewed at each check), an email address only if you give us one (for example to find a lost key), and its devices: each one’s random ID, general name and platform, and when it was added and last checked. We use these to unlock your devices, to keep a key to five devices at a time, and to ask Google or Microsoft whether a purchase was refunded. About once a week, when your device is online, the app checks its license with the server. The key and the signed license are kept on your device; releasing a device removes it from the license. No account is needed, and none of your writing is involved.
6. The ironbind.app Website and Its Forms
- Support form (on the Help and Insiders pages of ironbind.app): your name, email address, the category, subject and details of your report, and your app build version. We use it to investigate the issue and reply to you. The report is kept in our internal support tools as an Iron Bind bug report; your name is kept with the report and your email address separately, only our team can see either, and we remove both from a report if you ask.
- Email: if you email support@ironbind.app, we receive your message and email address and use them to reply.
- The website loads fonts from Google Fonts. These requests share your IP address and basic browser details with Google. Our web host keeps standard server logs (such as IP address and pages requested) for security and to keep the site running. The website sets no cookies of its own and uses no analytics or advertising trackers.
7. Google Play and the Microsoft Store
Iron Bind is distributed through Google Play, which collects information under Google’s own policies. Google gives us install statistics and, if you’ve allowed it on your device, crash reports, which help us fix problems. We don’t use these to identify you. If you buy the Archmage License there, Google handles the payment: we receive the purchase’s order number and token, never your payment details. The Windows app is also distributed through the Microsoft Store, under Microsoft’s own policies. If you buy the Archmage License there, Microsoft handles the payment: we receive the purchase’s order and item numbers and a Microsoft Store ID key, never your payment details.
8. What We Don’t Do
- No advertising or ad identifiers, and no selling or renting of personal information.
- No analytics, telemetry, automatic crash-reporting or tracking tools inside the app: a report reaches us only when you write and send it.
- No access to your location, contacts or microphone, and no camera permission. The Vault’s 📷 button opens your device’s own camera app; photos you take there, and images you pick from your device, are kept in your projects without their location, time and camera details (taken out of JPEG, PNG and WebP pictures; a file you attach in another format, a HEIC photo among them, is kept as it is), and go only where a project goes: its backups, its sync file, a book you pass and your exports.
9. Who Else Handles Information
- Supabase, our database provider, stores the reports sent from the website and the app, and Archmage License records.
- Google processes your text when you use AI features with your key, your backups and sync files when you link a Google account, the website’s font requests, and app distribution and purchases through Google Play.
- Microsoft processes your backups and sync files when you link a Microsoft account (OneDrive), distributes the Windows app and handles purchases through the Microsoft Store.
- Our web host serves ironbind.app and keeps its server logs.
- We may disclose information if the law requires it.
- These providers may store or process information outside Canada, including in the United States, where it may be subject to local laws.
10. How Long We Keep Information
- Your projects and author profile: on your device until you delete them. We hold no copy.
- Issue reports: as long as we need them to fix the issue and keep a record of the app’s development. We delete your name and email from a report if you ask.
- Archmage License records: as long as the license exists, so it keeps working on your devices. A released device is removed from it at once, and we delete a license’s email address if you ask.
- Support emails: as long as we need them to help you.
11. Your Choices and Rights
Under Canadian privacy law (including PIPEDA, and Alberta’s Personal Information Protection Act where it applies), you can ask what personal information we hold about you, ask us to correct it, withdraw your consent, or ask us to delete it. Email support@ironbind.app and we’ll respond within 30 days. If you’re not satisfied with our answer, you can contact the Office of the Privacy Commissioner of Canada or the Office of the Information and Privacy Commissioner of Alberta. If you live elsewhere, such as the EU or UK, you may have similar rights; contact us and we’ll help.
12. Security
Your projects are protected mainly by your device, as described in Section 1; the app doesn’t add its own encryption to your data, nor to your API key except in the Windows app (Section 2). Google’s and Microsoft’s account security, including any two-step verification you set up, protects your backups and sync files in Drive or OneDrive. Form submissions are sent over encrypted HTTPS connections, and only our team can access them, through accounts with role-based permissions. No method of storage or transmission is completely secure, so we can’t guarantee absolute security.
13. Children
Iron Bind is a general-audience creative writing tool. It is not directed at children under 13, and we don’t knowingly collect personal information from them. If you believe a child has sent us personal information, contact us and we’ll delete it.
14. Changes to This Policy
If we change this policy, for example when new optional online features ship, we’ll update the effective date and point out important changes in the app’s Legal Grimoire and at ironbind.app/privacy.
Contact Us
AHEM Studios · Alberta, Canada
support@ironbind.app