Privacy Policy

Who we are and what this covers

Cogmenta, Inc. (“Cogmenta,” “we,” or “us”) provides applications that help you organize information and receive personalized AI assistance. This policy covers our website and the Cogmenta products that link to it, including Loop Personal and our integrations with connected services. Individual Cogmenta products and connector applications may have different names.

This policy explains both local and hosted use. Customer-managed and on-premises enterprise deployments may have separate agreements and privacy notices describing their processing, administrator access, and deletion commitments. Those deployment-specific commitments, including any shorter deletion deadline, continue to apply. They do not expand our permitted use of Google data.

Information we handle

Depending on the product and features you choose, we handle:

• Account and support information: details you provide when creating an account or contacting us, such as your email address and the contents of your request.
• Information you provide: prompts, uploaded content, preferences, and feedback you choose to give the product.
• Connected account information: information retrieved from services you authorize, together with account identifiers and authorization tokens needed to maintain those connections.
• Personalized content: responses, summaries, retrieval indexes, embeddings (representations used to find relevant information), and memories derived from your content.

When you visit our website, its hosting and font providers receive the technical information needed to serve the page, such as your IP address and browser request information. The public website is hosted on GitHub Pages and loads fonts from Google Fonts. This website traffic is separate from access to your connected accounts.

Connected services and permissions

Our current connectors support Slack, GitHub, Notion, Gmail, Google Drive, and Google Calendar. Availability varies by product. You choose which accounts to connect and authorize access through each provider. Creating a Cogmenta account does not itself grant access to any of these services. Workspace or organization administrators may also control which connections are allowed.

Across these services, we handle account or workspace identifiers and authorization tokens needed to maintain the connection. We use retrieved content to provide the summaries, retrieval, context, and personalized assistance you enable.

Slack

We can access workspace and user identity information, the public and private channels and direct or group messages available to your authorized account, and message text and associated information such as senders, conversation identifiers, and timestamps. This supports conversation summaries and relevant context. Collection uses the conversations selected in the product. The current connector imports message text; it does not download attached files or images.

GitHub

We can access your account identity, readable organization feeds, and account activity events, including activity associated with private repositories when authorized. Events can include repository names, actors, timestamps, and details such as commit messages or issue and pull-request titles. We use these to summarize development activity and provide project context. The current connector reads activity feeds; it does not clone repositories or retrieve their source files.

GitHub's authorization permissions may allow broader access than the activity reads this connector performs. We use the granted access only for the disclosed features; the current connector does not write to your repositories.

Notion

We can access workspace and user information and the pages and data sources shared with the connection, including their titles, supported properties, and available top-level text blocks. This supports retrieval and personalized context from your notes and documents. The current connector does not collect data-source rows or recursively read nested blocks. Access is limited by what is shared with the connection and the capabilities granted in Notion.

Google: Gmail, Drive, and Calendar

Our shared Google authorization application may be identified as Loop. The following disclosures apply specifically when you connect Google services.

You decide whether to connect Google and which requested permissions to grant. Creating a Cogmenta account does not itself authorize Google access. Depending on the product and the connection you enable, our read-only integrations can access:

• Gmail: account information, labels, message headers and participants, message bodies, and attachments, to retrieve relevant correspondence and provide summaries and personalized context.
• Google Drive: file names, identifiers, ownership and other metadata, and file contents, including supported exports of Google Docs, Sheets, and Slides, to find and use relevant documents.
• Google Calendar: calendar information and event details, such as titles, descriptions, times, locations, organizers, and attendees, to provide scheduling context and briefings.

These Google integrations read information; they do not send email, edit or delete Google files, or create or change calendar events.

Permissions across connectors

The connectors described above currently read information; they do not post Slack messages, modify GitHub repositories, or edit Notion pages. We request permissions needed for the features you enable. Where a product offers resource selection, that selection controls what it retrieves; a provider permission may cover a broader set of data. Enabling one connector does not authorize another.

We use connected account data only to provide the authorized features described in this policy and the product. Adding a connector or requesting new permissions requires a separate authorization where applicable.

We use Google data only for the authorized, user-facing features described here and in the product. We do not sell Google data, use it for advertising, or use it to assess creditworthiness.

Local and hosted processing

Installed applications

Connected account data is stored and processed on your device by default. The application communicates directly with services you connect to retrieve authorized information. You can separately opt into uploading data to Cogmenta-controlled servers to enable hosted AI features. The opt-in explains the information that will be transferred.

Browser applications

Our browser products use hosted processing. When you start a hosted home, you choose this service by accepting the Terms of Service and the accompanying Hosted Data Notice. Information you provide and data from accounts you subsequently connect are stored and processed on Cogmenta-controlled infrastructure to provide the service.

Hosted AI

Hosted AI runs on servers and infrastructure controlled by Cogmenta. We do not send your connected account content to external AI model APIs for processing. Infrastructure providers that support our hosting act on our behalf; operating on our infrastructure does not mean that no infrastructure provider is involved.

Personalization and AI

We use your information as context for responses, to retrieve relevant material, and to maintain memories that personalize your experience. These features can create derived information, such as summaries and retrieval indexes.

We do not currently use connected account data to train or fine-tune model weights. If we introduce personalized model training, we will first explain the feature, update the applicable disclosures, and obtain the required consent. Acceptance of today's service is not consent to future training.

Google data and information derived from it will not be used to train or improve general-purpose models or models shared across users. Any future permitted personalized training will be limited to the specific user's model for an appropriate, clearly disclosed feature.

Sharing and human access

We do not sell your personal information. We share information only as necessary to provide the service you choose, operate and protect it, or meet legal obligations. For hosted use, this can include infrastructure providers acting on our instructions. Support correspondence is handled by the staff and communication services needed to respond.

Access to connected account content by people is limited. We may access specific content with your affirmative permission, such as when you request support, when necessary to investigate a security issue or abuse, or when required by law. Permission to connect an account is not blanket permission for staff to read its contents.

Transfers of Google data are limited to providing the authorized features with your consent, security purposes, legal requirements, or a business transfer after obtaining your explicit prior consent. These restrictions also apply to information derived from Google data.

Provider requirements and Limited Use

Our access to Slack, GitHub, Notion, and Google is subject to each provider's applicable terms, permissions, and data-use restrictions. Your authorization and our terms do not override those restrictions. The local and hosted processing, personalization, sharing, and deletion provisions in this policy apply to data from all the connectors described above.

Google Limited Use

Cogmenta's use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including its Limited Use requirements, and the applicable Google Workspace API user data and developer policy.

These commitments cover both the original information and information derived from it. Neither hosted-processing consent nor an enterprise agreement authorizes uses prohibited by these policies.

Retention and deletion

We retain information only while needed for the features you choose and the purposes described in this policy, subject to each connected service’s applicable storage and caching restrictions. You can request deletion at any time.

• Disable hosting or delete hosted data: we stop new uploads and hosted AI processing for the affected data when you disable hosting or request its deletion. We delete the affected source data, stored credentials, and derived content—including indexes, embeddings, and memories—from active hosted systems within 30 days of that action or request.
• Backups: remaining copies expire within 90 days of the same action or request. They are unavailable for ordinary use. If a backup must be restored for recovery, the deletion is reapplied before the affected data returns to ordinary use.
• Local copies: disabling hosting does not delete information stored on your device. Use the installed product's data controls to remove it. Copies or backups you create remain under your control.
• Original content in connected services: deleting Cogmenta's copies does not delete the original messages, files, events, repository activity, or pages in Slack, GitHub, Notion, or Google.

If law requires us to retain particular records, we retain only what is required, restrict it to that purpose, and delete it when the obligation ends. A separate enterprise agreement may require a shorter deadline for the deployment it covers.

Your choices and requests

You can choose which services to connect, use available data and connection controls, and contact us to request access, correction, export, or deletion of information we hold. Depending on your location, you may have additional rights to object to or restrict processing, withdraw consent, or complain to a data protection authority. We may need to verify your identity before fulfilling a request.

You can manage or revoke connections in the provider's own settings. For Slack, use the workspace's app-management controls; you may need a workspace owner to remove the app. For GitHub, review authorized OAuth apps in your account settings. For Notion, manage the connection in workspace settings or remove its access to shared pages.

Provider instructions: Slack app removal and authorization, GitHub authorized applications, and Notion connection management.

You can remove Google's authorization through your Google Account's third-party connections. For any connector, revocation prevents future access under that authorization but does not automatically erase information already retrieved. To remove stored copies, use the product's deletion controls or contact us.

For a hosted-data deletion request, email support@cogmenta.biz and identify the product and account involved. Do not include passwords, access tokens, or sensitive source content. We can delete copies on our infrastructure; we cannot remotely remove copies held only on your device.

Because browser products depend on hosted processing, withdrawing from hosting means the affected hosted features can no longer be provided.

Security

We use access controls and safeguards appropriate to the information and the environment in which it is processed. Our connections to Slack, GitHub, Notion, and Google use secure network communications. For installed applications, protecting your device, operating-system account, and local backups remains important. Credential protection does not mean every local file is independently encrypted.

If you believe your account or information has been exposed, contact support@cogmenta.biz. Do not send credentials or private source content with the initial report.

Changes to this policy

We will update the date on this page when this policy changes. We will notify affected users of material changes and obtain consent before using connected account data for a new purpose where required. New processing will not begin merely because we publish a revised policy.