# Privacy Policy
URL: https://samva.dev/legal/privacy
> How Samva collects, uses, shares, retains, and protects personal information and customer data, and how to make a privacy request.
- Version: 1.5
- Effective: 2026-10-28

## 1. Roles [#1-roles]

This Privacy Policy explains how Arya Labs, Inc. (“Arya Labs,” “Samva,” “we,” “us,” or “our”) handles personal information relating to Samva websites, dashboards, APIs, email Services, and related communications.

Arya Labs is generally a controller for account, identity, billing, website, security, abuse-prevention, service-improvement, and direct-support information.

When a customer submits contacts, message content, templates, events, or related recipient information to use the Services, the customer generally determines the purposes and means of processing and Arya Labs acts as a processor or service provider. The customer is responsible for providing notices, obtaining permissions, responding to recipient requests, and giving lawful instructions. The Data Processing Addendum governs that processing.

## 2. Information We Collect [#2-information-we-collect]

We may collect:

- account names, email addresses, organization details, authentication records, and support communications;
- billing, subscription, invoice, tax, payment-status, and usage information; payment-card details are handled by payment providers rather than stored by Samva as the card number;
- domains, senders, API keys, contacts, templates, message content, attachments, campaigns, and other Customer Content;
- delivery, bounce, complaint, unsubscribe, suppression, open, click, timestamp, IP-address, user-agent, clicked-URL, and provider-webhook information;
- if you connect a WhatsApp Business Account, the account identifiers, access credentials, messages, and templates described in Section 5;
- if you connect Google Calendar to a Samva agent, the calendar data described in Section 6;
- security, authentication, audit, quota, abuse, reputation, and operational telemetry;
- website, device, browser, cookie, analytics, and session-replay information as described in the Cookie and Analytics Notice; and
- information provided when you contact us, request support, report abuse, or exercise a privacy right.

Do not submit payment-card data, protected health information, special-category personal data, children’s data, or other regulated data through the Services unless Arya Labs has approved that use in a separate written agreement.

## 3. How We Use Information [#3-how-we-use-information]

We use information to:

- provide, authenticate, maintain, and support the Services;
- process messages and delivery events;
- manage billing, limits, subscriptions, and invoices;
- operate unsubscribe, suppression, bounce, complaint, and anti-abuse controls;
- secure accounts, investigate misuse, and protect recipients and infrastructure;
- communicate about accounts, changes, incidents, support, and product operations;
- measure and improve the Services, including analytics and session replay where permitted and configured;
- comply with law, respond to lawful requests, resolve disputes, and enforce agreements; and
- create aggregated or de-identified information that does not reasonably identify a person.

## 4. Engagement Tracking [#4-engagement-tracking]

Samva may process email opens and clicks, including timestamps, IP addresses, user agents, clicked URLs, and link metadata, when engagement tracking is enabled for the relevant message or organization. Tracking may be enabled by default in some contexts and will be disabled or require consent where applicable law requires prior consent.

Customers are responsible for providing recipients with required notices and obtaining required permissions. A recipient’s engagement preference is separate from an unsubscribe or suppression record. Suppression data may be retained to prevent future contact even after other data is deleted.

## 5. WhatsApp Business Accounts Connected Through Meta [#5-whatsapp-business-accounts-connected-through-meta]

This section applies only if your organization connects a WhatsApp Business Account to Samva.

When you connect an account through Meta’s Embedded Signup, Meta Platforms provides Samva with the WhatsApp Business Account ID; the phone number ID, phone number, and display name; the ID of the Meta user who completed the signup; and an access token that lets Samva operate the account through the WhatsApp Business Platform. Samva encrypts that access token, and the two-step verification PIN it sets when it registers the number with Meta, through its key-management service before storing them.

While the account is connected, Samva exchanges data with Meta through the WhatsApp Cloud API: the content, media, and templates you send; the messages and media your recipients send to your number, with their phone numbers and WhatsApp profile names; delivery and read statuses; Meta’s review decisions on your templates; and the account’s verification status, quality rating, and messaging limit. Samva copies media your number receives into its own storage while Meta still serves it.

We use this data only to connect and operate the account, send and receive messages for you, show them in the dashboard and API, deliver your webhooks, measure and bill WhatsApp usage, and keep the account’s status current. For messages and recipient information, Arya Labs acts as a processor as described in Section 1.

Samva keeps this data while the organization exists. Disconnecting a number stops Samva sending and receiving through it but does not by itself delete the stored data; deleting the organization does. [Data Deletion](/legal/data-deletion) explains each option and how to ask us to delete this data.

## 6. Google Calendar Connected to Samva Agents [#6-google-calendar-connected-to-samva-agents]

This section applies only if your organization connects a Google Calendar to a Samva agent.

When an administrator connects a calendar, Samva asks Google for free and busy times and for events on calendars the Google account owns. Samva receives a refresh token and encrypts it through its key-management service before storing it. Signing in to Samva does not request this calendar access.

While the calendar is connected, Samva reads free and busy times on the connected calendar for a window of at most 31 days, and shows the agent open times on the quarter hour. It also reads the primary calendar’s title and time zone. For the primary calendar, that title is the account’s email address, and Samva stores the title and time zone with the connection. The connected calendar starts as that account’s primary calendar. Before booking or moving a meeting, Samva checks whether an event on a calendar the account owns already occupies that time. Samva does not keep titles, attendees, or descriptions from the free and busy read or from that check. Samva creates, updates, and cancels events on calendars the account owns. Each event it writes has a title, optional notes, a start and end, and a private marker that identifies the agent, the contact, and the booking. Samva changes or cancels only an event that same agent created for that contact. Creating or changing an event does not send email to attendees through Google.

We use this data only so a Samva agent can offer a customer open meeting times and book, move, or cancel a meeting the agent arranges with that customer. Every booking waits for your confirmation before Samva creates it. Moving or canceling a meeting waits for your confirmation the same way. For this calendar data, Arya Labs acts as a processor as described in Section 1.

The free times and the booking’s title, notes, and times are included in the prompt that asks a model to write the agent’s reply. That request goes to OpenRouter and then Fireworks AI, or to Anthropic, depending on the model the organization selects, through Cloudflare AI Gateway. Full prompts and responses sent to AI models for Samva Agents are logged in Cloudflare AI Gateway. Logging is on, and zero data retention is off, so those prompts and responses are stored there. Calendar data included in a prompt is part of that log. Cloudflare also stores the conversation, including these calendar actions. Samva does not sell this data, use it for advertising, or use it for credit decisions.

Samva keeps the encrypted refresh token, the calendar title, and the time zone until an administrator disconnects the calendar. Disconnecting asks Google to revoke the token and deletes the stored credential. Records of the calendar actions, including the times offered and the booking details, are stored with the conversation. Deleting the contact erases that conversation, including these records, when Samva can find the conversation. If the mailbox, or the Samva agent’s access to that mailbox, was already removed, Samva may not find the conversation, and these records may remain. Section 10 describes contact and organization deletion.

An administrator can disconnect the calendar in Samva. You can also remove Samva’s access at [https://myaccount.google.com/permissions](https://myaccount.google.com/permissions). Events already written stay on the Google Calendar. To ask us to delete the calendar data Samva stores, contact [privacy@samva.dev](mailto:privacy@samva.dev).

Samva does not use information received from Google APIs to develop, improve, or train generalized or non-personalized AI or machine-learning models.

Samva's use and transfer of information received from Google APIs to any other app will adhere to the [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.

## 7. Cookies, Analytics, and Session Replay [#7-cookies-analytics-and-session-replay]

Essential cookies and similar technologies support authentication, security, routing, preferences, and core functionality.

The public Samva website is measured by default without cookies and without any identifier stored in your browser: PostHog groups visits under a daily identifier it computes on its servers and that we cannot reverse, and the Google Analytics tag runs with every storage permission denied, so it writes no cookie and reads none. Accepting analytics cookies adds a first-party identifier stored in your browser for each processor, grants Google its advertising storage permissions in the same answer, and turns on session replay for public marketing and documentation pages, with typed input masked. Rejecting them returns both processors to the cookieless measurement and deletes the Google Analytics cookies from your browser. The [Cookie and Analytics Notice](/legal/cookies) describes both modes, what each one collects, and how to change your choice at any time.

When you create an account you accept the Terms of Service, and that acceptance permits us to link what you do inside the Services to your account for product analytics, through an opaque account identifier and never your name or email address. You can withdraw it at any time in Settings → Profile → Privacy, under **Product analytics**; withdrawing stops the linking and ends the identity we hold for you in our analytics provider. The Samva dashboard and mailbox send no automatic page views and run no session replay.

PostHog, Inc. processes this analytics and replay data on our behalf on infrastructure in the United States. Google LLC processes website analytics on our behalf through Google Analytics. We connect no advertising product to that measurement: Google Signals and ad-personalization signals are turned off, and no advertising or remarketing audience is built from your visit.

Withdrawing consent does not affect processing already completed and does not disable essential functionality.

## 8. Sharing [#8-sharing]

We may share information with:

- infrastructure and service providers that process information for us, including AWS, Cloudflare, PlanetScale, Upstash, Autumn, Stripe, Axiom, PostHog, Google, and Cloudflare Turnstile;
- customer-authorized recipients, providers, or integrations necessary to deliver a customer’s messages, including Meta Platforms when a customer connects a WhatsApp Business Account;
- professional advisers, auditors, insurers, financing parties, and transaction counterparties subject to appropriate confidentiality;
- authorities, courts, or other parties when required by law or necessary to protect rights, safety, the Services, or recipients; and
- a successor in a merger, acquisition, financing, reorganization, or sale of assets.

Full prompts and responses sent to AI models for Samva Agents are logged in Cloudflare AI Gateway. Logging is on, and zero data retention is off, so those prompts and responses are stored there.

Our current subprocessor list and notice process are available at [/legal/subprocessors](/legal/subprocessors).

## 9. International Processing [#9-international-processing]

Samva uses providers and infrastructure that may process information in the United States and other countries. Provider location and transfer mechanisms vary by service. Where data-protection law requires a transfer safeguard, Arya Labs will use an applicable lawful mechanism, such as an adequacy decision, contractual safeguard, or other legally recognized measure.

## 10. Retention and Deletion [#10-retention-and-deletion]

We do not promise one uniform retention period for all information. Retention varies by data type, operational purpose, customer configuration, legal obligation, security need, billing requirement, backup lifecycle, and provider behavior.

Website analytics events and session recordings are retained according to the configuration of our analytics provider. Specific retention periods for those categories are under review and will be stated here once fixed.

You may request account deletion through available controls or by contacting us. [Data Deletion](/legal/data-deletion) describes the deletion controls and what each one removes. Organization deletion may not immediately remove every copy and may not remove data that must remain for billing, legal compliance, security, abuse prevention, audit, backups, or suppression. Suppression data may be retained specifically to prevent re-contact.

Deleting one contact, or more than one at once, first erases the memory Samva keeps for each contact and the Samva Agents conversations Samva can find for that contact, and then deletes the contact. If an erasure does not succeed, Samva keeps every contact in that request, so the deletion can be tried again. Deleting an organization erases the memory kept for each contact, the Samva agent conversations Samva can find, and the knowledge the organization’s Samva agents share, before the final deletion of the organization’s data. Samva finds a conversation from the mailboxes a Samva agent can currently use. A conversation whose mailbox, or the agent’s access to that mailbox, was already removed may not be found, and that conversation may remain. Samva erases the memory kept for the contact even when it cannot find the conversation.

Customers must handle deletion and correction requests for recipient data and may ask Samva for reasonable assistance where technically available.

## 11. Security [#11-security]

We use technical and organizational measures appropriate to the nature of the information and the Services. These include encryption in transit, access controls, tenant isolation, credential protection, key-management controls, logging, operational monitoring, and provider security controls. No system or transmission is completely secure, and we do not promise that unauthorized access will never occur.

If we determine that a security incident requires notice, we will provide prompt notice through an appropriate channel, subject to law, investigation, security, and provider constraints.

## 12. Rights and Requests [#12-rights-and-requests]

Depending on location and applicable law, individuals may have rights to access, correct, delete, restrict, object to, or receive a copy of personal information, and to withdraw consent.

We do not sell personal information, and we do not share it for cross-context behavioral advertising, as those terms are used in California law. We do not use analytics data to build advertising profiles or to target you on other services.

For account and website information, contact [privacy@samva.dev](mailto:privacy@samva.dev). For recipient and Customer Content held on behalf of a customer, contact the relevant customer first. We will assist customers with legally required requests where appropriate and technically possible. We may verify identity and authority before responding.

## 13. Children [#13-children]

The Services are not directed to children. Do not use Samva to collect or process children’s data without a separate written agreement and all required protections.

## 14. Changes [#14-changes]

We may update this Policy by posting a new version and effective date. For material changes, we will provide reasonable notice through the Services or email where required.

## 15. Contact [#15-contact]

Privacy requests: [privacy@samva.dev](mailto:privacy@samva.dev)

Legal notices: [legal@samva.dev](mailto:legal@samva.dev)

Arya Labs, Inc. <br /> 1111B S Governors Ave #29161 <br /> Dover, DE 19904