Privacy Policy

Effective Date: April 1, 2026
Last Updated: November 14, 2026


1. Introduction

This Privacy Policy describes how MF0 (mf-lab) ("Service", "we", "us", or "our") collects, uses, and protects your information when you use our platform.

By using the Service, you agree to the practices described in this Policy.


2. Information We Collect

We collect information in the following categories:

2.1 Information You Provide

2.2 Automatically Collected Technical Data

Once per day per authenticated session, we collect the following technical data. This collection is based on our legitimate interest in improving service quality and security. It does not require cookie consent.

This data is stored in our database and is not shared with advertising networks. It is used exclusively to understand how the platform is used and to improve reliability and performance.

2.3 Usage Data

2.4 Local Storage and Project Data

MF0 is designed with local-first principles:

2.5 Connected Gmail Data

If you choose to connect Gmail in My services, we request permission to read and modify your mailbox and create drafts. MF0 does not send email or permanently delete email. Moving a message or a selected group of up to 50 messages to Trash is performed only after your explicit confirmation and can be reversed in Gmail.

Gmail data is used only to provide the features you request: reading and summarizing mail, changing read/unread status, adding labels, archiving, moving messages to Trash after your explicit confirmation, and creating reply drafts. One confirmation can apply a Trash action to the entire reviewed group; per-message success and failure results are returned so a partial failure does not cause the whole group to be repeated blindly. We do not use Gmail content for advertising, lending or sale. Disconnecting Gmail deletes locally stored OAuth credentials and requests revocation from Google; you can also revoke access in your Google Account.

Raw Gmail content is processed only for the requested feature and is retained as part of the corresponding conversation until you delete it. Aggregated or anonymized service metrics, such as token counts, model selection, timestamps and request costs, are used for billing, reliability and abuse prevention. Gmail content is not used to train, retrain, fine-tune or otherwise improve any AI/ML model beyond the requesting user's personalized model.

2.6 Connected GitHub Data

If you choose to install our GitHub App, we process only the repositories you make available to that installation. Metadata remains read-only. Contents, issues, pull requests, Actions and repository creation may have write permission solely for the confirmed actions described below.

GitHub data is used only to provide the repository features you request. A repository must be accessible both to the App installation and to your connected GitHub user; if your user access is revoked, MF0 no longer treats the repository as available. After explicit confirmation, MF0 may create a private repository with an initial text-file commit, create one atomic commit on a new branch and open a pull request, add one commit to an existing same-repository mf0/* pull request branch, comment on or triage an issue, publish a pull request review, rerun a completed workflow (optionally failed jobs only), or clone a pull request for an isolated install and standard npm test run. Issue, pull request head and workflow state are revalidated before writing. Test workspaces are deleted afterward; install and test commands receive no GitHub token, database credentials or production secrets. MF0 does not merge pull requests, force-push, delete repositories or branches, change repository settings, modify workflow files or write directly to a repository's default branch. Disconnecting deletes the local identity and installation connection, cancels pending previews and requests revocation of the GitHub OAuth authorization and current installation token; you can also uninstall the GitHub App or change its repository selection in GitHub.

2.7 Connected WordPress.com Data

If you choose to connect a WordPress.com site, MF0 requests the global OAuth scope to provide full site-building and administration features. MF0 binds every operation to the site you enter and does not use the connection to manage your other sites. We do not collect your WordPress.com password.

When you select WordPress and ask the agent to work on your site, MF0 executes the requested tool action immediately: creating and publishing content, editing content and metadata, restoring revisions, generating images through the existing billed image-generation provider and uploading media, moderating comments, creating terms and updating menus, settings, templates and reusable template parts, launching the site and creating an export with a time-limited download link. Image-generation prompts and resulting files are processed to provide the requested media and record the corresponding usage charge. New content is published by default unless you explicitly request a draft. There is no additional confirmation window. Current revision state is revalidated before writing to avoid overwriting a newer external edit. Permanent deletion of a post, page, media item or navigation menu is available only when your current request explicitly asks for permanent deletion; MF0 cannot undo it. MF0 does not provide the model with your OAuth token or permit arbitrary endpoint calls. Disconnecting deletes the local connection and cancels pending actions. You can also revoke the application in your WordPress.com account settings.

2.8 Connected Dropbox Data

If you choose to connect Dropbox in My services, MF0 requests access to your account information, folder and file metadata, and file contents, including permission to create, replace and move files after your explicit confirmation. MF0 does not permanently delete files.

Dropbox data is used only to provide the folder, search, reading, download and confirmed file-management features you request. File content returned by the AI becomes part of the corresponding conversation and is retained under the same rules as that conversation until you delete it. Disconnecting Dropbox cancels pending previews, deletes locally stored OAuth credentials and requests revocation from Dropbox; you can also revoke access in your Dropbox account settings.

2.9 Connected Google Calendar Data

If you choose to connect Google Calendar in My services, MF0 requests permission to read your calendar list and read, create, update and delete your events. Event changes are performed only after your explicit confirmation. Guest invitations and update notifications are disabled by default.

Calendar data is used only to provide the event reading, creation, update and deletion features you request. Recurring-series management is not supported in this version. Calendar content returned by the AI becomes part of the corresponding conversation and is retained under the same rules as that conversation until you delete it. Disconnecting Google Calendar cancels pending previews, deletes locally stored OAuth credentials and requests revocation from Google; you can also revoke access in your Google Account.


3. How We Use Information

We use information to:


4. AI Processing and Third-Party Providers

The Service may send your Input to third-party AI providers (e.g., language model APIs) to generate Output.

Gmail and Google Calendar content is sent only to the AI provider you select from this Limited Use-compatible list: OpenAI, Anthropic, Google paid Gemini API, Perplexity, xAI, DeepInfra, Cerebras, Z.AI and BytePlus. Their current public API terms state that they do not use your content to train models or do not retain it, with limited processing for safety, billing, legal compliance and abuse prevention. We do not send Gmail or Google Calendar content to Moonshot/Kimi while their API training terms remain unconfirmed.

The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements. Gmail and Google Calendar content is not sold, used for targeted advertising or lending, or transferred to third parties for any purpose other than to provide or improve the features you request. Aggregated or anonymized data is not used to train AI/ML models either.

Third-party providers may process your data according to their own policies. We review these policies and restrict Gmail and Google Calendar access to compatible providers, but we are not responsible for independent changes to third-party services or their policies.


5. Analytics and Usage Tracking

We collect and store usage-related data such as:

This data is used for:


6. Data Sharing

We do not sell your personal data.

We may share data only in the following cases:


7. Data Retention

We retain data:

Expired Gmail, Dropbox and Google Calendar action previews are periodically deleted. Gmail, GitHub, WordPress, Dropbox and Google Calendar content that becomes part of an AI conversation is retained under the same rules as that conversation until you delete it. OAuth credentials are deleted when you disconnect the corresponding service or delete your account.

You may:


8. Your Rights and Controls

Depending on your location, you may have the right to:

You can manage your data via:


9. Security

We implement reasonable technical and organizational measures to protect your data.

However:


10. Children

The Service is not intended for children under 13.

We do not knowingly collect data from children under this age.


11. International Data Transfers

Your data may be processed in different jurisdictions depending on:

We apply appropriate safeguards where required.


12. Changes to This Policy

We may update this Privacy Policy from time to time.

We will update the "Last Updated" date and provide notice if changes are material.


13. Contact

For questions or requests related to this Privacy Policy:

info@mf0.ai