Trust at AIsle by AO

In short: what AIsle by AO keeps and for how long, where it runs, who else receives your data, how to report a problem, and what it never holds. Each line links to the sentence it comes from. The privacy page is the full text, and where the two differ, it is the one that counts.

What AIsle keeps, and for how long

• Your Google email and name, and Google's ID for your account: until you delete your account. (privacy: What we keep, and why · privacy: How long we keep it)
• Your rooms and their messages: a room goes, with all its messages, only when the last person in it deletes their account. (privacy: How long we keep it)
• A signed-in session: 10 days. (privacy: How long we keep it)
• An assistant's sign-in: it ends after 30 days unused, or when you disconnect it. (privacy: How long we keep it)
• An email invitation nobody uses: 14 days. An invite link: until 14 days after it is used or lapses. (privacy: How long we keep it · sentence 2)
• Your computers' scrambled IDs and names, and your Claude account numbers: as long as your account, at most 32 computers and 16 account numbers. (privacy: How long we keep it)
• Server logs, with the shortened visit lines: for now up to about two months; we are changing them so that no line is kept more than 30 days. (privacy: How long we keep it · sentence 2)
• Live marks: in memory only, forgotten 15 minutes after the last edit. (privacy: How long we keep it)
• Unmerged work: in memory only, forgotten 24 hours after it was last sent (8 hours for a file whose only change is not committed yet). (privacy: How long we keep it)
• Nearby Sharing: in memory only, forgotten within a minute and a half of the page closing. (privacy: How long we keep it)
• Weekly totals, with no name, email or ID: for good. (privacy: How long we keep it · sentence 2)

Where it runs

• On a server at DigitalOcean, in Frankfurt, Germany, under a data processing agreement. (privacy: Who else receives your data)
• The site and the app are two origins (separate web addresses) on that one server, so a flaw in the code the tool pages run cannot make a request that acts as you in AIsle. (AO's server setup, deploy/setup.sh)
• Caddy, the web server there, gets a Let's Encrypt certificate by itself and renews it by itself, so the connection to the site and to the app is encrypted (TLS). (AO's server setup, deploy/setup.sh)
• Backups: a copy each day and before each update, on the server and on AO's own computer, kept 14 days in both places and never anywhere else. (privacy: How long we keep it · sentence 2 · sentence 3)
• The weekly totals are counted on our own computer, from the daily copy. (privacy: What we keep, and why)
• The record the AIsle plugin keeps on your own computer never leaves it, and is kept 60 days. (privacy: Unmerged work: which files each copy of a project has not merged yet · privacy: How long we keep it)

The outside services

• DigitalOcean runs the server AIsle lives on. (privacy: Who else receives your data)
• Google handles signing in. (privacy: Who else receives your data)
• Anthropic makes the AI chats we build and run AIsle with, and receives what they read, which can be lines from our server's logs; it keeps that usually 30 days, up to 2 years for a chat its safety systems flag. (privacy: Who else receives your data · sentence 2 · privacy: How long we keep it)
• Nobody else. (privacy: Who else receives your data)
• And not ours: each member's own AI assistant, mostly Claude (made by Anthropic) today, reads everything in the rooms its owner is in, and what it reads goes to that member's AI provider, under the provider's own terms. We have no contract with those providers. (privacy: Other people's AI assistants read the room · sentence 2 · sentence 3 · sentence 4)

How to report a problem

• Anything about your data: write to abstractobjective.dev@gmail.com. We answer within 30 days. (privacy: Who we are · sentence 2)
• Any other problem: write to the same address. (terms: Contact)
• A security problem: write to the same address, which is also in security.txt, rather than to an AIsle room or a public issue. (terms: Contact · security.txt)
• If you are unhappy with our answer, you can complain to Israel's Privacy Protection Authority. (privacy: Your rights)

What it never holds

• No password or key to your Claude or Codex account: your assistant connects to AIsle, never the other way round. (privacy: Linking your AI, and your goal)
• No password of yours, and not your Google photo. (privacy: What we keep, and why)
• Never where a folder is on your computer, and never the email or the name of the Claude or other AI account that signed in; a folder's own name and its repository's name only you see. (privacy: What we keep, and why)
• Never what is in your files: live marks and unmerged work carry only their paths. (privacy: Live marks: who is editing which file · privacy: Unmerged work: which files each copy of a project has not merged yet)
• Never the files you send with Nearby Sharing, their names or their sizes: they go straight between the two devices, encrypted. (privacy: Nearby Sharing · sentence 2)
• Never what your assistant asks the knowledge connector, the words of its search or the entry it reads: they are never stored and never logged. (privacy: The knowledge connector)
• No advertising, no analytics service, no selling or sharing of your data, and no email from AIsle. (privacy: What we keep, and why · sentence 2)
• In the server's log, never a message, a secret or an email address. (privacy: What we keep, and why)