Privacy Policy

This site and the Tensvia service are operated by Tensvia LLC, a Delaware limited liability company with operations in New York. Tensvia is the brand; Tensvia LLC is the legal entity responsible for the processing described below and is the data controller for account data.

Privacy questions and requests: privacy@tensvia.com. Full contact details are at the end of this policy and on the contact page.

Account data is about the businesses that use Tensvia — your name, work email, company, billing details, and how you use the product. We decide how that is handled, so we are the controller for it.

Customer Data is your customers' information that flows through the Service — their messages, contact details, bookings, call audio. You decide what happens to that; we only process it to run the Service for you. There we are a processor, and the Data Processing Addendum governs.

If you are someone who messaged a business that uses Tensvia: that business, not Tensvia, decides how your information is used. Contact them first. We will help them respond.

• Account & identity — name, work email, business name, role, authentication records.
• Billing — plan, invoices, payment method reference. Card numbers go to Stripe directly; we never hold them.
• Business facts you supply — services, prices, hours, policies, uploaded documents and media.
• Customer Data — inbound and outbound messages, contact records, consent state, bookings, and where you enable it, call audio and transcripts.
• Operational — logs, request metadata, IP address, error reports, audit records of who approved what and when.

This is the most sensitive category we handle, so it is set out separately rather than folded into a list.

• Messages. Inbound and outbound content on the channels you connect — Instagram, Messenger, SMS and MMS, WhatsApp, email — together with timestamps, sender and recipient identifiers, delivery receipts and thread history.
• Calls. Where you enable call features, call metadata, and audio recordings and transcripts only where you have turned recording on. Recording is off unless you enable it.
• Consent and suppression state. Opt-ins, opt-outs, revocations, the channel and time each was recorded, and the source. This is retained even after a contact is otherwise deleted, because honouring an opt-out permanently requires remembering it.
• Drafts and decisions. What the Service proposed, what it cited, whether it was approved, edited, held or blocked, and by whom.

Recording a call is subject to consent laws that vary by state. Whether you may record, and what disclosure is required, is your responsibility — see the Terms.

We do not run advertising cookies or third-party ad pixels on this site. Nothing here follows you around the web, and we do not sell or share personal information for cross-context behavioural advertising.

What we do use:

• Strictly necessary cookies — session and authentication cookies that keep you signed in and protect against request forgery. The Service cannot function without these.
• Preference storage — for example your light or dark theme choice, kept in your browser and not sent to us.
• Optional website analytics — only after you choose “Allow analytics,” we store a random visitor and session identifier, page path, referrer host or campaign source, and demo milestones. We do not put form content, names, email addresses, or raw IP addresses in the analytics ledger. Anonymous website events are scheduled for deletion after no more than 395 days.
• Server-side operational logs — request metadata, IP address and error reports, used to run and secure the Service and to understand aggregate usage.

Your browser can block or clear cookies. Blocking strictly necessary cookies will prevent you from signing in.

Subscription billing is handled by Stripe. When you pay, your card details go to Stripe directly — they do not pass through and are never stored on Tensvia systems. We hold a billing contact, a payment method reference (such as a card's last four digits and brand), and invoice history.

Stripe processes that information as an independent controller under its own privacy policy for fraud prevention and regulatory purposes, in addition to acting for us.

To run the Service, authenticate you, bill you, keep the system secure, detect abuse, meet legal obligations, and support you when you ask. For customers in the UK and EEA, our lawful bases are performance of a contract, legitimate interests in securing and improving the Service, and compliance with legal obligations.

Message content and business context are sent to our model provider to produce a classification or a draft, and are used for that inference only.

We do not use your Customer Data to train general-purpose models, and we do not permit our providers to. We do not sell personal information, and we do not share it for cross-context behavioural advertising.

We use the sub-processors below. Each is bound by contract to confidentiality and to process only on our instructions.

We will give notice before adding a sub-processor that processes Customer Data. We also disclose information where legally compelled, and we will tell you unless we are prohibited from doing so.

Connected accounts (Google)

When you connect a Google account, Tensvia accesses only the data you authorize through Google's OAuth consent screen — for example, read-only Google Calendar events to sync your bookings, and your Google account email address to identify the connection. We access this data solely to provide the features you enabled.

Tensvia's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell Google user data, do not use it for advertising, do not use it to train generalized AI models, and do not transfer it except as necessary to provide or improve the feature you connected, to comply with law, or with your consent. Google tokens are held in a restricted, service-role-only store (row-level-security protected and encrypted at rest by our infrastructure), scoped per tenant, and never exposed to other tenants or to the browser. You can revoke Tensvia's access at any time at myaccount.google.com/permissions.

Customer Data is kept while your account is active. On termination you have 30 days to export, after which we delete within 30 days. Billing records are retained as long as tax and accounting law requires. Audit and security logs are retained for up to 24 months, because a log you have already deleted cannot tell you what happened.

Data is encrypted in transit and at rest. Tenant isolation is enforced at the database with row-level security rather than by application code remembering to filter. Provider credentials are stored as vault references — never written to logs, never placed in model context, never sent to the browser. Access to production data is limited to personnel who need it and is logged.

We hold no SOC 2 report or ISO certification at this time and do not claim one. Report a vulnerability to security@tensvia.com.

Depending on where you live you may have rights to access, correct, delete, port, or restrict processing of your personal information, to object to processing based on legitimate interests, and to be free from discrimination for exercising them. California residents have the rights set out in the CCPA/CPRA; UK and EEA residents those in the UK GDPR and GDPR.

Email privacy@tensvia.com. We will verify your identity and respond within the period the applicable law requires. For Customer Data, we forward the request to the business that controls it.

We operate in the United States and our sub-processors are located there. If you access the Service from outside the U.S., your information is transferred to and processed in the U.S. Where required for UK/EEA transfers we rely on Standard Contractual Clauses.

The Service is for businesses. We do not knowingly collect personal information from anyone under 18. If you believe a minor's information has reached us, write to privacy@tensvia.com and we will delete it.

We will post updates here and, for material changes, notify account holders at least 30 days before they take effect.

Privacy questions, access requests and deletion requests go to privacy@tensvia.com. Security reports go to security@tensvia.com.

The data controller for account data is:

We aim to acknowledge requests within five business days. Where you are a customer's contact rather than our customer, send your request to the business that messaged you — they control that data and we act on their instructions. Tell us anyway if you cannot reach them.