MoMa.CS

Draft in progress: this text describes how the platform works today and is awaiting final legal review. This is not the final version.

Privacy Policy

Last updated: August 31, 2026

  1. 1. Who we are
  2. 2. What this Policy covers
  3. 3. Data we collect
  4. 4. Why we use it, and on what legal basis
  5. 5. Processing by artificial intelligence
  6. 6. Integrations with other services
  7. 7. Who we share data with
  8. 8. International transfers
  9. 9. Security
  10. 10. How long we keep data
  11. 11. Your rights
  12. 12. Cookies
  13. 13. Audience and minors
  14. 14. Changes to this Policy
  15. 15. Contact and data protection officer

This Policy explains what data MoMa.CS handles, why we handle it, who we share it with, and how you exercise your rights.

It is written in plain language and describes only what the platform actually does today.

1. Who we are

MoMa.CS is the AI agent platform operated by AGLAB TECNOLOGIA E CONSULTORIA LTDA, registered under company number 67.291.829/0001-61, with offices in São Paulo, Brazil (“MoMa Labs”, “we”). The app is available at app.momalabs.ai.

For questions about this Policy or about how your data is handled, write to contato@momalabs.ai.

Roles: for account and operational data, we act as the controller. For the content your company enters into the platform or connects through integrations, we act as the data processor (operador, under the LGPD), handling data under the instructions of the contracting company.

2. What this Policy covers

This Policy covers the MoMa.CS app (app.momalabs.ai) and the services provided through it.

The corporate website momalabs.ai has its own policy, published at momalabs.ai/privacidade; what you read here does not apply to it.

We apply Brazil's General Data Protection Law (LGPD). The service is intended for companies in Brazil and is not directed at users in the European Economic Area or the United Kingdom.

3. Data we collect

We collect what is needed to create the account, run the platform, and keep it secure. We do not ask for a phone number, we do not use audience analytics tools, and we do not collect data for advertising.

  • Account data: email, password, first name, last name, company name, company website (optional), and preferred language. The password is managed by our authentication provider (Supabase Auth) and is never stored by us in clear text.
  • Invitation data: when someone joins through a company invitation, we handle the invitation token and the email bound to it.
  • Company website: if you provide a website at sign-up, we read its public pages to build your company's 2nd Brain (knowledge base).
  • Usage content: messages exchanged with agents, documents and content added to the 2nd Brain, agent, flow and routine settings, run and activity history, human approvals, and the memories an agent accumulates within the account — each memory can be deleted individually.
  • Integration data: information retrieved from the services your company connects, and the credentials and tokens for those connections.
  • Technical security records: authentication events, credential access records, and audit events in our backend. The application does not collect geolocation; hosting providers may keep their own technical connection logs.

4. Why we use it, and on what legal basis

Each purpose rests on a legal basis.

  • Creating and maintaining the account, authenticating access, and delivering the contracted service — performance of a contract.
  • Running agents, flows, and routines under your company's instructions — performance of a contract.
  • Protecting the platform: containing fraud and abuse, limiting access attempts, and keeping an audit trail — legitimate interest in security.
  • Diagnosing failures and improving service quality — legitimate interest.
  • Sending transactional messages: sign-up confirmation, password reset, and invitations — performance of a contract.
  • Meeting legal obligations and responding to requests from authorities — legal obligation.
  • Processing that depends on your express authorization — consent, where required.

5. Processing by artificial intelligence

To answer questions and carry out tasks, the platform sends content to language model providers we contract: OpenAI, Anthropic, and Google (Gemini). Semantic search over the knowledge base uses embeddings generated by OpenAI (model text-embedding-3-small).

What may be sent to those providers: the messages and instructions you write, the session history, the knowledge base excerpts retrieved to answer, the integration data needed for the task, and the tool calls the agent makes.

When an agent searches the internet, the query is sent to the Serper search service. In the sourcing and recruiting feature, profile data may be enriched through RapidAPI (LinkedIn Sales Navigator).

Agents accumulate memories and learnings inside your account to improve later answers. Those memories stay within the account and can be deleted individually.

MoMa Labs does not train its own models on your content, and the model providers we contract do not use content sent by the platform to train their models, under the data-use terms we maintain with each of them.

AI-generated output can be wrong, outdated, or incomplete — review it before you use it. Meaningful actions and decisions can be gated on human approval: the platform supports requiring approval before write actions, and your company configures that requirement per agent.

6. Integrations with other services

Integrations are optional and initiated by your company. Connecting a service authorizes the platform to access it on your behalf, within the scope granted in that authorization.

Credentials and tokens for those connections are encrypted at rest. A connection can be removed at any time from within the platform; once disconnected, we stop accessing the service.

On GitHub, the platform reads repositories; changes are only proposed, subject to human approval.

Using each connected service remains subject to that provider's own terms and privacy policy.

  • QuickBooks Online (Intuit) — accounting and financial data, read-only within the authorized scope.
  • Thera — contractor agreement data, read-only.
  • Greenhouse — recruiting and application data.
  • GitHub — repository reads and proposed changes.
  • Slack and Telegram — messages in the channels where the agent operates.
  • Email through the company's own mailbox (IMAP/SMTP), using credentials the company provides.
  • MCP servers reached through a governed gateway, limited to the tools registered for the account.
  • Available integrations may vary by account and deployment.

7. Who we share data with

We do not sell personal data and we do not share it for advertising. Sharing is limited to the vendors needed to run the platform, which handle data under our instructions:

  • Supabase — database and authentication, in the São Paulo region.
  • Vercel — web application hosting, in the configured gru1 region (São Paulo).
  • Google Cloud (Cloud Run) — backend hosting and operational telemetry, in the São Paulo region (southamerica-east1).
  • OpenAI, Anthropic, and Google — AI model and embedding providers.
  • Resend — transactional email delivery, such as invitations.
  • Serper — web search requested by agents.
  • RapidAPI (LinkedIn Sales Navigator) — data enrichment, only in the sourcing and recruiting feature.

We may engage other equivalent vendors when needed to operate the platform.

Material changes to the vendor list will be announced through an in-app notice.

We may also disclose data when required by law, court order, or a request from a competent authority, and to exercise or defend legal claims.

8. International transfers

The web application is served from the São Paulo region (Vercel, gru1) and the backend runs on Google Cloud infrastructure in the São Paulo region. The database is located in the São Paulo region.

AI model providers and some other vendors process data outside Brazil, including in the United States. In those cases, the international transfer relies on contractual clauses entered into with those providers and the other safeguards provided for in article 33 of the LGPD.

9. Security

We apply technical and organizational measures appropriate to the nature of the service:

  • Integration credentials encrypted at rest with AES-256-GCM, using envelope encryption.
  • Account isolation in the database through Row Level Security, with role-based access control (RBAC).
  • HttpOnly session cookie with encrypted contents, and origin verification on routes that change data — protection against cross-site requests.
  • Rate limiting on failed authentication attempts and on invitation sending.
  • Backend event audit trail.
  • Invitation links encrypted at rest.
  • Secrets and credentials are never written to logs.
  • Encryption in transit (TLS) is provided by the hosting providers.

No measure removes risk entirely. In the event of a security incident that may cause relevant risk or harm, we will notify affected individuals and the competent authorities as required by applicable law, within a reasonable time.

10. How long we keep data

We keep data while the account is active and for as long as needed for the purposes in this Policy or to meet legal obligations. Specific periods are still being defined:

  • Account and profile data: up to 3 (three) months after termination.
  • Run history and agent conversations: up to 5 (five) years.
  • Security and audit records: up to 5 (five) years.
  • Credential access records: up to 5 (five) years.
  • Backups: up to 1 (one) month.
  • Short-lived operational data is already discarded automatically: idempotency keys and execution checkpoints are removed after roughly seven days, and abandoned runs are closed out and cleaned up.

11. Your rights

As a data subject, you can exercise the rights set out in article 18 of the LGPD:

  • confirmation that processing exists, and access to the data;
  • correction of incomplete, inaccurate, or outdated data;
  • anonymization, blocking, or deletion of unnecessary data or data processed unlawfully;
  • data portability;
  • information about who we share your data with;
  • withdrawal of consent, where processing relies on it;
  • objection to processing based on legitimate interest.

The platform does not currently offer self-service account deletion or a general data export: requests are handled on demand at contato@momalabs.ai, and we respond within 15 (fifteen) days. We need to verify your identity before acting on a request.

If your data was entered into the platform by a customer company, that company decides on the processing: send your request to them directly, and we will support them in answering it.

You may also file a complaint with Brazil's data protection authority (ANPD).

12. Cookies

We use only first-party cookies, strictly necessary for the service to work. There are no analytics, advertising, or third-party cookies, and the application does not store data in the browser's local storage.

  • cc_session — keeps the authenticated session. Valid for 7 days, renewed on use; HttpOnly, with encrypted contents.
  • cc_locale — stores the interface language. Valid for 1 year; mirrors the preference saved on the account.
  • Transient cookies for authentication and integration authorization flows — for example, connecting QuickBooks Online. They exist only for the duration of the flow and are discarded afterwards.

13. Audience and minors

MoMa.CS is a business product, intended for companies and their professionals. It is not directed at people under 18, and we do not knowingly collect their data. If we identify an account in that situation, we will close it and delete the data.

14. Changes to this Policy

We may update this Policy to reflect changes in the product or in the law. The version in force is always the one published on this page, with the update date shown at the top. Material changes will be announced through an in-app notice.

15. Contact and data protection officer

To exercise your rights, ask a question, or report a privacy problem, write to contato@momalabs.ai.

Data protection officer (DPO): dpo@momalabs.ai.

Read the Terms of Use · Back to sign in