Privacy policy
Last updated Oct 10, 2026
Who runs moore
moore is a private, invitation-only vault run for one household and the companies it owns. It is not a public service: nobody can sign up, and only people the vault's owner invites can sign in.
This policy explains what the vault holds about the people who use it, what it does with that information and the choices they have. It covers this website, the installed app and the accounts a member connects to it.
What the vault holds
Only what members put in it or connect to it:
- Account details: name, email address, language, the access the owner has given, sign-in methods such as a password or passkey, sign-in sessions and, if the member turns on face sign-in, a face template used only to recognise them.
- Documents and files members upload, with the text read from them and the details filed from them.
- Records members create or that are filed from their documents, such as people, companies, property, bills and dates.
- Conversations with Ask: questions, answers, files attached to them and the steps Ask took.
- Voice notes and recordings a member sends or connects, for example from a Plaud recorder or a Teams meeting, and their transcripts.
- Data from accounts a member connects, described in the sections below.
- If a member installs the desktop companion: the folders they choose to share and their computer's status (free disk space, battery, operating system version, disk encryption and installed browsers).
- An audit log of what happens in the vault: sign-ins, documents viewed, downloaded, uploaded, changed or deleted, messages sent and actions Ask takes.
How it is used
Everything the vault holds is used to give its members the service: to store, read, file, search and show their information, to answer their questions and to carry out what they ask for.
Nothing is sold, rented or traded. Nothing is used for advertising or to build profiles for anyone outside the vault. The vault runs no analytics or advertising trackers.
Google user data
A member can choose to connect their own Google account. The vault then asks Google for these permissions and uses each only as described:
openid- Confirms which Google account was connected.
email- Reads the account's email address, to show which account is connected and to match mail to the member.
profile- Reads the account's name and picture, to label the connected account.
https://www.googleapis.com/auth/gmail.modify- Reads the member's mail so the vault can list it, open a message when they ask and file a message or its attachments into the vault. Marks messages read or unread, archives them or moves them to the bin when the member asks.
https://www.googleapis.com/auth/gmail.send- Sends mail and saves drafts as the member, only when they ask or a routine they set up does so.
https://www.googleapis.com/auth/gmail.settings.basic- Reads and changes the member's Gmail filters, signature, vacation reply and label settings when they ask.
https://www.googleapis.com/auth/gmail.settings.sharing- Reads and changes the member's forwarding addresses and send-as addresses when they ask.
https://www.googleapis.com/auth/calendar- Reads the member's calendars and events to answer their questions; creates, changes or removes events, makes calendars and shares them when they ask; checks when they are free to suggest meeting times.
https://www.googleapis.com/auth/drive- Searches and reads the member's Google Drive and the shared drives they belong to when they ask, files a copy of a file into the vault when they ask, and uploads, renames, moves or bins files when they ask.
https://www.googleapis.com/auth/tasks- Reads the member's Google Tasks lists and adds, changes or completes tasks when they ask.
https://www.googleapis.com/auth/contacts- Reads the member's Google contacts to find people, and adds or changes contacts when they ask.
https://www.googleapis.com/auth/contacts.other.readonly- Reads the "other contacts" Gmail keeps for the member, to find an address they have written to.
https://www.googleapis.com/auth/directory.readonly- Looks up people in the member's Google Workspace organisation by name.
https://www.googleapis.com/auth/documents- Reads the member's Google Docs and edits one in place when they ask.
https://www.googleapis.com/auth/spreadsheets- Reads the member's Google Sheets and changes cells in one when they ask.
https://www.googleapis.com/auth/presentations- Reads the member's Google Slides and adds or changes slides when they ask.
https://www.googleapis.com/auth/forms.body- Reads the member's Google Forms and makes or changes a form when they ask.
https://www.googleapis.com/auth/forms.responses.readonly- Reads the answers to the member's Google Forms when they ask.
https://www.googleapis.com/auth/youtube- Lists the member's YouTube videos and playlists, changes a video's title or description, and uploads a video from the vault when they ask.
https://www.googleapis.com/auth/meetings.space.readonly- For a Google Workspace member: reads their Meet meetings, recordings and transcripts when they ask, to answer about a meeting or file it into the vault.
https://www.googleapis.com/auth/chat.spaces- For a Google Workspace member: lists the Google Chat spaces they are in when they ask.
https://www.googleapis.com/auth/chat.messages- For a Google Workspace member: reads messages in their Google Chat spaces and sends a message as them, only when they ask.
https://www.googleapis.com/auth/admin.directory.user.readonly- For a Google Workspace admin: reads the organisation's users when they ask.
https://www.googleapis.com/auth/admin.directory.group.readonly- For a Google Workspace admin: reads the organisation's groups and their members when they ask.
To keep the member's inbox quick, the vault keeps a short index of their mail (subject, sender, recipients, date, a short preview and read state), refreshed in the background while the account is connected. Message bodies and attachments are fetched from Google when the member opens or files them, and are stored only when they file them into the vault. Calendar events are read when needed and not copied. Drive files, contacts, tasks, forms and other Google data are read when the member asks, and stored only when they file them into the vault.
Google user data is acted on only at the member's request or by routines they set up. It is visible to the member who connected the account and to the vault's owner. If the member shares a mailbox with another member, that person sees only the messages they sent or received.
Google user data is never sold, never used for advertising and never used to develop, improve or train generalised AI or machine learning models. It is not shared with anyone except the AI model provider the vault is configured to use, which processes a request on the member's behalf when they ask Ask about their Google data; as needed to keep the service secure; and as required by law.
OAuth tokens are stored on the vault's own servers, encrypted with AES-256-GCM. Apart from the people named above, nobody reads a member's Google data unless the member asks for help with specific messages, it is needed for security, or the law requires it.
moore's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements: https://developers.google.com/terms/api-services-user-data-policy
Microsoft 365 data
A member can connect their own Microsoft 365 account. With their permission the vault reads and manages their Outlook mail, calendar and contacts, their OneDrive and SharePoint files, Planner tasks, Teams chats and channels, and Teams meeting recordings and transcripts, and sends mail and messages as them when they ask. Mailboxes and calendars others have shared with them are reached only as far as Microsoft already allows.
Microsoft data is handled the way Google data is above: kept in the same short mail index, acted on only at the member's request or by their routines, sent to the AI model provider only to answer their request, never sold or used for advertising, and with its tokens stored encrypted.
The vault can be linked to WhatsApp as a linked device: the household's own number, and a member's own number if they choose to link it. It then keeps the messages of linked chats (sender, chat, text and time) so members can ask about them, and reads photos and voice notes sent to it, keeping a description or transcript.
Messages from a member's own linked WhatsApp are visible only to that member and the vault's owner. Linking can be ended at any time from the linked devices list in WhatsApp.
Odoo and other connections
A member can also connect business systems and services such as Odoo, a Plaud recorder, Canva, an email server or file storage. The vault reads from them and makes changes in them as that member, only when the member asks.
Ask and AI model providers
Ask, reading documents, transcribing recordings and reading answers aloud are done by AI models from the providers the vault is configured to use, such as OpenAI, Anthropic, Google Gemini, ElevenLabs or OpenRouter, or a model server run by the operator. When a member asks something, the parts of their information needed to answer it are sent to that provider to produce the answer, and for nothing else.
moore does not use members' information to train AI models and does not send it anywhere for that purpose.
Storage and security
The vault runs on a private server operated for the household. Every read and write in its database is limited by row-level security to what the signed-in person is allowed to see, so the database itself decides each person's access. Documents are encrypted at rest with a key of their own, uploads are scanned for malware, and connected-account tokens are encrypted.
Every document opened, downloaded or changed is recorded in an audit log that cannot be edited. Backups are taken several times a day and encrypted before they are stored off the server.
How long it is kept
Documents, records and conversations with Ask are kept until they are deleted, and the audit log is kept permanently. Temporary chats are removed after 30 days unless the owner sets another period, sign-in sessions end after 30 days and logs of model calls are removed after 91 days. Database backups are kept for 14 days; backed-up document files are kept even after they are deleted from the vault.
When a member unlinks an account, the vault stops using it at once and retires its token; unlinking a Google account also revokes the vault's access at Google. The account's mail index is no longer shown to anyone and is deleted on request. Anything the member filed into the vault stays until they or the owner delete it.
Your choices
A member can unlink a Google or Microsoft account at any time: in moore, open Workspace, then Accounts, choose the account and press Unlink.
Unlinking a Google account also revokes the vault's access at Google. A member can check this, or revoke access from Google's side themselves, at https://myaccount.google.com/permissions
To have their information, a connected account's data or their whole account deleted, or to get a copy of it, a member can ask the owner or write to privacy@mofeed.info
Children
moore is not directed at children and is not offered to them. Nobody under 13 is invited to use it, and it does not knowingly collect information from them.
Changes to this policy
When this policy changes, the new version is published here with a new date.
Contact
Questions or requests about this policy or your data: privacy@mofeed.info