Privacy Policy

This Privacy Policy explains how Tengri Vertex ("Tengri Vertex," "we," "us," or "our"), operating the Chamter product, collects, uses, discloses, and protects personal information when you visit our websites, create an account, or use our software services (collectively, the "Service").

This document is designed for production use and Google OAuth verification. It is not a substitute for advice from your counsel. You should have it reviewed before relying on it for regulated markets or enterprise contracts.

1. Who we are

Chamter is a go-to-market platform focused on generative engine optimization (GEO), citable public answers, inbound lead handling, outbound campaign research, and email Sequences that send as you from your connected mailbox.

2261 Market Street San Francisco, CA 94114 United States

Privacy and legal requests: legal@chamter.com
Product support: support@chamter.com

2. Scope

This Policy applies to:

• Visitors to https://chamter.com and related marketing pages
• Customers and workspace members who use the authenticated product
• People who submit forms or contact requests on public answer pages
• Personal information processed when you connect third-party accounts (for example Gmail) to the Service

This Policy does not govern websites, products, or AI systems we do not control, including search engines or large language model providers that may independently discover public content you choose to publish through the Service.

3. Information we collect

3.1 Account and workspace data

• Name, work email address, and authentication identifiers
• Workspace, team membership, roles, and invitation records
• Billing and plan metadata (if and when you purchase paid features)
• Settings such as language preference and product configuration

3.2 Customer content you provide

• Owned website URLs, crawled page text, metadata, and evidence used to form answers and intents
• Campaign briefs, account names, research notes, and playbook content
• Sequence lists, recipient email addresses, merge fields, templates, and send status you create
• Messages, drafts, and annotations you enter in the product

3.3 End-customer and lead data (customer-controlled)

If you use Inbox, public answer pages, or Sequences, you may import or receive personal data about third parties (for example a buyer who contacts you, or a recipient on a sequence). For that data, you are typically the controller (or "business") and we act as your processor (or "service provider") under applicable law, except where we determine purposes independently (for example security, billing, or product analytics about Service usage).

3.4 Connected account data (Gmail and similar)

• When you connect Google: OAuth tokens, the Google account email we send as, granted scopes, connection status, and technical logs needed to maintain the connection
• For Sequences v1 we request only send capability plus basic identity scopes. We do not use Restricted Gmail scopes to read your full mailbox as part of the default product
• Message identifiers, subjects, and bodies of emails the Service originates on your instruction, plus delivery status we can observe through the send path

3.5 Automatically collected technical data

• IP address, device and browser type, approximate location derived from IP
• Pages viewed, feature usage events, referrers, and diagnostic logs
• Cookies or similar technologies as described below

3.6 Public sources

To power GEO and outbound research features, we may process publicly available information (for example public web pages, registries, or other sources you or the product lawfully access). We do not claim that public availability alone is always a lawful basis for every outreach use; you remain responsible for how you use results in your market.

4. How we use information

We use personal information to:

• Provide, operate, secure, and improve the Service
• Authenticate users and manage workspaces
• Crawl, analyze, and publish content you authorize
• Generate product outputs (answers, intents, research, personalization) using automated systems
• Send email on your instruction when you connect a mailbox and approve a send
• Process inbound contacts and route them to your workspace
• Enforce limits, detect abuse, prevent fraud, and protect rights and safety
• Communicate about the Service (transactional messages; product updates you can control where required)
• Comply with law and respond to lawful requests
• Establish, exercise, or defend legal claims

Where GDPR or similar laws apply, we rely on one or more of: performance of a contract; legitimate interests (for example securing and improving the Service); consent (for example certain cookies or optional connections); and legal obligation.

5. Google user data (Gmail API) and Limited Use

If you connect a Google account, our use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

• What we access: With Sequences, we request gmail.send and standard OpenID identity scopes so we can send email as you and identify the connected account. We do not request full mailbox read scopes for the default Sequences product.
• How we use it: Only to provide and improve user-facing features that you enable (sending approved sequence messages, showing send status, maintaining the connection, security, and abuse prevention).
• What we do not do: We do not use Google user data to serve advertisements. We do not sell Google user data. We do not allow humans to read Google user data unless (a) you give affirmative consent for specific messages for support, (b) it is necessary for security or legal compliance, or (c) the data is aggregated and does not identify users. We do not use Google user data for training generalized AI or ML models outside the Limited Use rules.
• Transfer: Google user data is not transferred to third parties except to subprocessors who help us provide the Service under contracts that protect the data, or as required by law.
• Storage: OAuth refresh tokens are stored encrypted at rest using application-layer encryption and are accessible only to service components that need them. You may disconnect Gmail in the product; we then revoke or delete stored tokens as described under Retention.

6. AI processing

The Service uses third-party model providers to generate and transform content (for example drafting answers, personalizing sequence copy, or classifying messages). Inputs you provide and system prompts may be sent to those providers to produce outputs. We configure providers under our agreements and policies; we do not use your Google user data to train generalized models in violation of Google Limited Use rules.

AI outputs can be wrong or incomplete. You are responsible for reviewing outputs before publishing or sending them.

7. How we share information

We share personal information with:

We do not sell personal information as "sale" is commonly defined under the CCPA/CPRA. We do not share personal information for cross-context behavioral advertising. If that ever changes, we will update this Policy and provide required opt-out mechanisms.

Public answer pages and other content you choose to publish are visible on the open web and may be indexed or cited by third parties, including AI systems. That is an intended function of GEO features.

8. Cookies and analytics

We use cookies and similar technologies for:

• Essential session and security functions
• Remembering preferences (for example language)
• Product analytics and performance measurement

Where required by law, we will obtain consent for non-essential cookies. You can control cookies through your browser settings; blocking essential cookies may break login or core features.

9. Retention

• Account data: for the life of the account and a reasonable period afterward for backups, disputes, and legal retention
• Customer content: until you delete it or close the workspace, subject to backup cycles and legal holds
• Gmail tokens: while the connection is active; deleted or invalidated on disconnect
• Sequence and send records: as needed to operate the product, show history, prevent abuse, and meet legal duties
• Logs and analytics: typically for shorter operational windows unless needed longer for security or compliance

10. Security

We implement administrative, technical, and organizational measures appropriate to the risk, including encryption in transit, access controls, encryption of sensitive tokens at rest, and least-privilege service roles. No method of transmission or storage is completely secure. You are responsible for protecting account credentials and for configuring workspace access carefully.

11. Your rights

Depending on your location, you may have rights to access, correct, delete, export, restrict, or object to certain processing, and to withdraw consent where processing is consent-based. California residents may have additional rights under the CCPA/CPRA, including the right to know, delete, correct, and not be discriminated against for exercising rights.

To exercise rights, email legal@chamter.com. We may need to verify your identity. If you are an end user of a customer (for example someone who filled a form on a customer's public answer page), contact that organization first; we will assist them as their processor.

You may disconnect Google access from your Google Account permissions page and from the Service. Disconnecting stops future sends via that connection.

12. International transfers

We are based in the United States and use infrastructure that may process data in the United States and other countries. If you access the Service from outside the United States, you understand that your information may be transferred to jurisdictions with different data-protection rules. Where required, we use appropriate transfer mechanisms (for example standard contractual clauses) with processors.

13. Children

The Service is for business use and is not directed to children under 16 (or the higher age required in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided personal information, contact us and we will take appropriate steps to delete it.

14. Changes

We may update this Policy from time to time. We will post the updated version with a new "Last updated" date and, where required, provide additional notice. Continued use of the Service after the effective date constitutes acceptance of the updated Policy where permitted by law.

15. Contact

Privacy questions and requests: legal@chamter.com

2261 Market Street San Francisco, CA 94114 United States

Related: Terms of Service