Legal

Privacy policy

This policy describes how Tyrell processes personal data on Striker’s public site and in the product.

Updated 29 September 2026

Email support: contact@tyrell.so
On this page

Who handles your data

Tyrell, in Chile, is the controller of the public site, accounts, billing, and platform operation.

For content each customer uploads or generates in Striker — contacts, conversations, campaigns, and files — the customer is generally the controller and Tyrell acts as processor on the customer’s instructions.

Product data is isolated by organization.

What data we process

Depending on how you use Striker, we may process:

  • Account data: name, email, phone, credentials, organization settings, and billing.

  • Customer content: contacts, messages, templates, campaigns, notes, and files.

  • Channel identifiers: WhatsApp number, Instagram username or ID, email, and voice.

  • Tokens and identifiers Meta provides when an admin connects WhatsApp or Instagram.

  • Google Calendar and Gmail data when a user connects those features (see “Google user data” below).

  • Technical security, operations, and usage logs.

Why we use it

We use personal data to provide and protect Striker: authenticate accounts, isolate data by organization, send and receive messages on channels the customer connects, support commercial follow-up, allow human handoff, coordinate meetings when the customer configures them, bill, provide support, and meet legal obligations.

Sharing and processors

We share data only when needed to provide the service, comply with law, protect rights, or follow the customer’s instructions.

Tyrell uses processors that handle data on our behalf for hosting, messaging channels, email, voice, and inference. When a customer connects WhatsApp or Instagram, Meta is involved.

Some processors may process data outside Chile.

Google user data

Connecting Google Calendar or Gmail is optional. When you connect either one, Striker receives an access token and your Google account email address, which it uses to show which account is connected.

Google Calendar: Striker reads the free/busy times of your calendar, not the details of your events, so it can offer real open slots. When a seller books a meeting with a lead, Striker creates that event, and it only reads, moves or cancels the events it created.

Gmail: Striker only asks Google for permission to send. It sends from your address only the emails you authorize, one by one or by letting your agent write to your leads for you. It never reads, lists, modifies or deletes the email in your mailbox. Striker keeps the emails it sent, which it wrote itself, and the Gmail message and thread IDs so replies stay in the same conversation.

Google access tokens are stored encrypted. We do not sell Google user data, use it for advertising, or use it to train general AI models. You can disconnect Calendar or Gmail in Striker, or revoke Striker’s access in your Google Account, at any time.

Striker’s use of information received from Google APIs adheres to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

Security

We apply reasonable technical and organizational measures to protect personal data against unauthorized access, loss, alteration, or improper disclosure.

Retention

Account data is kept while the organization is active and for a reasonable period after closure, unless law requires longer retention.

Customer content is kept while the customer keeps it in Striker or until a verified deletion request is completed, subject to applicable legal exceptions.

Your rights

Under Law 19.628, you may exercise the rights below. We rule on requests within two business days.

If your data is in Striker because a customer contacted you, that customer is usually the controller; we will coordinate with them when we act as processor.

For data deletion, use this site’s data deletion page.

  • Access to your personal data.

  • Rectification of inaccurate data.

  • Erasure where applicable.

  • Blocking of processing where the law allows.

  • Objection to processing in the cases provided by law.