Privacy policy
This policy explains what Accessible Database Manager collects, why, who it is shared with, and how you can get a copy of your data or delete it. It is written in plain language on purpose.
Last updated: 16 July 2026
Who is responsible for your data
Accessible Database Manager is provided by Full Circle AT LLC (“we”, “us”), a limited liability company registered in Minnesota, United States. We are the data controller for the information described here, and your data is stored on servers in the United States.
Questions, requests, or complaints: accessible.db@fullcircleat.com. We aim to answer within 30 days.
What we collect
Your account
- Your email address and display name.
- Your password, stored only as a bcrypt hash. We never store or see the password itself.
- If you turn on two-factor sign-in: your two-factor secret and backup codes.
- Account status, whether your email is confirmed, when you signed up, and when you last signed in.
The content you create
- The databases, fields, and records you make — including everything you type into them.
- File attachments you upload. These are stored on our server outside the public web folder and can only be downloaded through a check that confirms you may read that database.
- Who you have shared a database with, at what permission level, and any invitation email addresses you enter.
Security and audit records
- An activity log of actions taken on your databases (what happened, when, and the IP address it came from). This exists so you can see who changed what, and so we can investigate abuse.
- Sign-in attempts (the email address tried, the IP address, and whether it worked), kept so we can slow down password-guessing attacks.
- API tokens you or the apps create: a hash of the token, the device name, and when it was last used.
What we do not do
- We do not sell or rent your data to anyone.
- We do not use advertising, ad networks, or third-party trackers.
- We do not run analytics on you, and we have added no analytics tool of our own to the website or the apps. (One exception, described below: the Android text scanner is built on a Google component that reports its own diagnostics to Google.)
- We do not read your records to train anything.
What stays on your device (the iOS and Android apps)
- Camera scanning recognises text entirely on your device. The picture is never uploaded to us or to anyone else — only the text you choose to keep is saved, as a normal record. On Android, that on-device recognition is done by a Google component (ML Kit). Your photo and the recognised text stay on your phone, but the component reports its own technical diagnostics to Google — things like which version ran, whether it succeeded, and how long it took. We do not receive that information. The iPhone app uses Apple's own on-device scanner and sends nothing to a third party.
- Face ID, Touch ID, and fingerprint never leave your device. The app only ever receives a yes/no answer from the operating system. We never receive or store biometric data.
- Offline copies of your databases and records are cached on your device so the app works without a connection. They are removed when you sign out or delete the app.
- Your sign-in token is held in the iOS Keychain or Android’s encrypted storage.
Who else sees your data
- Microsoft — we send email (confirmation codes, password-reset codes, sharing invitations) through Microsoft Graph, so the contents of those emails pass through Microsoft.
- Google — only in the Android app, and only if you use the camera scanner: the Google component that reads text on your device reports technical diagnostics about itself to Google, as described above. It does not send your photos, your text, or anything about your account.
- Our hosting provider — the server that stores the database and your uploaded files.
That is the complete list. We may also disclose data if the law requires it.
How long we keep things
- Your content — until you delete it. Deleted databases and records go to a recycle bin first so you can undo a mistake; emptying the bin removes them for good.
- Sign-in attempt records — cleared out automatically after a short period.
- Activity log — kept as your database's history. When you delete your account it is stripped of anything identifying you (see below).
Your rights
Get a copy of your data
Use Backup & restore on the website, or
GET /api/v1/me/export from the API, to download everything you own as a JSON file.
Correct your data
You can change your name, email address, and password yourself in Settings, or on the Account screen in the apps.
Delete your account
You can delete your account yourself — in Settings on the website, or on the Account screen in the iOS and Android apps. It asks for your password, cannot be undone, and immediately removes:
- your account and sign-in details,
- every database, field, and record you own,
- your uploaded files, deleted from the server's disk,
- your shares, saved views, webhooks, and API tokens,
- your sign-in attempt records.
One thing is kept rather than deleted: entries in the activity log. Those are the history of databases that other people may still be sharing, so instead of removing them we strip out anything that identifies you — your user ID and IP address are erased from them permanently.
If a database was shared with you but owned by someone else, it stays with its owner; you simply lose access.
Other rights
Depending on where you live, you may have further rights — for example, residents of California and several other US states can ask what personal information we hold and request its deletion, and people in the UK or European Economic Area can additionally object to or restrict how their data is used and complain to their data protection regulator. We apply the rights above to everyone regardless of where they live. Email us and we will help.
We do not sell or share personal information as those terms are used in US state privacy laws, and we do not use your data for targeted advertising or automated decision-making.
Cookies
The website sets one cookie: the session cookie that keeps you signed in. It is essential, it is not used for tracking, and there are no advertising or analytics cookies. The apps use a token instead of cookies.
Children
Accessible Database Manager is not directed at children and we do not knowingly collect data from them.
Changes
If this policy changes we will update the date at the top of this page, and tell you in the app or by email if the change is significant.
This policy and our service are governed by the laws of the State of Minnesota and the United States, without regard to conflict-of-law rules. If you use Accessible Database Manager from outside the United States, your data is transferred to and stored in the United States.