Legal

Privacy policy

Last updated 11 November 2026About 5 minutes to read

Draft, to be reviewed before launch. Operator details, contact, governing law and hosting are still to be confirmed and are marked on this page.

This page explains what Microooo stores when you use it, why, who else sees it and the choices you have. It describes how Microooo works today; we will update it when that changes.

On this page

Who is responsible

Microooo (operator details to be confirmed) runs Microooo and is responsible for your personal data in it. You can reach us at to be confirmed.

What we store

WhatDetails
AccountYour email address, your name if you give it, how you signed in (email or Google), when the account was created and when you last signed in. With email sign-in, your password is stored only as a salted scrypt hash, never as the password itself.
SessionsA random session ID in a cookie. Our server keeps only a SHA-256 hash of it, linked to your account.
Your workspaceYour chats, projects, settings, app list, AI Team, Vault entries and the rest of your workspace are saved to your account on our server so every device you sign in on sees the same work. Your browser keeps a cached copy.
Files and Your LLMFiles you upload, files your AI saves, pages you save with Save to LLM and the search index built from them, kept per account.
Apps you buildThe files of each app, saved to your workspace so it can run in Microooo and be downloaded.
Browser sign-insCookies from sites you sign in to inside Microooo's browser, kept per account and encrypted at rest with AES-256-GCM. A private browser session saves none.
Connected appsThe access token from each work tool you connect, encrypted at rest with AES-256-GCM, the account name it belongs to, when you connected and the access granted. Content is copied in only when you import it.
MCP tokensWhen you connect an AI, its token is shown to you once. We keep only a SHA-256 hash, the AI it is for and when it was made. Disconnecting the AI or signing out revokes it.
Phone previewsA random link token, the app it opens and when it expires (7 days).
Usage countsTimestamps used to apply usage limits, such as how often private guidance was requested in the last day.

What we do not do

  • We do not sell your data or use it for advertising.
  • Microooo's website and app carry no advertising or analytics trackers.
  • Microooo does not run its own AI model on your content. Your connected AI processes what it is sent, under its provider's terms.
  • We do not read the chats you have inside other AI products, and we do not copy content from a connected tool unless you import it.

Why we use it

  • To run your account and keep you signed in.
  • To save, sync, search, back up and export your work.
  • To connect the AI accounts, tools and services you choose, and to show their estimated costs.
  • To keep Microooo secure, apply usage limits and prevent abuse.
  • To meet legal obligations.

Where data protection law asks for a legal basis, we rely on running our agreement with you, our legitimate interest in keeping Microooo secure, and legal obligations.

Who else sees it

  • Your connected AI. When your AI uses Microooo's tools, the results it asks for (for example a project plan or library search results) go to that AI, under its provider's terms.
  • Services you choose. When you connect a service for an app, Microooo sends that service what is needed to set it up for you.
  • Work tools you connect. Requests go to the tool with your access token, only for what you ask.
  • Sites you open in Microooo's browser. Pages are fetched by Microooo's server, so those sites see the server's address rather than yours.
  • Google. If you continue with Google, Google tells us your email address and name. This website and the app load the Inter Tight font from Google Fonts, so your browser sends Google its IP address.
  • Hosting. The company that will host Microooo's servers will be named here before launch.
  • The law. If we are legally required to share data, we will share only what is required.

Where it is kept

Your data is stored on Microooo's servers. Where those servers run, and any transfers outside your country that follow from that, will be named here before launch, together with the safeguards we use.

How long we keep it

  • Account data, workspace, files and apps: while your account is open.
  • Sessions: until you sign out (the session is then deleted) or for up to one year.
  • MCP tokens: until you disconnect that AI or sign out.
  • Phone preview links: 7 days.
  • After you ask us to delete your account, we delete its data within 30 days, except anything the law makes us keep.

How it is protected

  • Passwords are stored as salted scrypt hashes; session and MCP tokens as SHA-256 hashes.
  • The session cookie is HttpOnly and SameSite=Lax, so page scripts cannot read it.
  • Browser sign-ins and connected-app tokens are encrypted at rest with AES-256-GCM.
  • Apps you run in Microooo open in a sandbox, apart from your account. Phone previews are served by a separate server on your local network that serves nothing else.

Being honest about today: your workspace, files and Vault entries are stored on our server as part of your account but are not separately encrypted by Microooo yet. No system is perfectly secure, so use a strong, unique password.

Your choices and rights

  • Download any project, or all of them, as a zip from Files.
  • Disconnect any AI or work tool at any time; its token is revoked.
  • Use a private browser session to save no sign-ins at all.
  • Ask us to access, correct, export or delete your data, or object to how we use it, at to be confirmed.

Depending on where you live, you may also complain to your data protection authority.

Children

Microooo is not meant for children under 16, and we do not knowingly collect their data. If you think a child has given us data, contact us and we will delete it.

Changes to this policy

We will update this page when Microooo's practices change and change the date at the top. If a change is important, we will tell you in Microooo.

Contact

Privacy questions and requests: Microooo (operator details to be confirmed), contact to be confirmed.