Legal
Privacy policy
This policy describes how Tyrell processes personal data on Striker’s public site and in the product.
Updated 11 October 2026
Email support: contact@tyrell.soOn 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.
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 (gmail.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. Messages go out one at a time, with a minimum gap between sends and a daily limit per mailbox that starts low for a new mailbox and rises over its first days. Every message carries a one-click unsubscribe and a visible link, and a reply asking to stop is honored; both put the person on a suppression list that blocks later sends. Replies come back to Striker through a Reply-To address on Striker’s own domain, so the agent can continue the conversation; Gmail keeps each sent message in your Sent folder. 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. Striker uses Google user data only to provide the features you connect. We do not sell it, use it for advertising, or use it to train general AI models, and we do not transfer it to others except as needed to provide those features, for security, or to comply with the law. No person reads it unless you ask us to, for security, or when the law requires it. You can disconnect Calendar or Gmail in Striker, or remove Striker from the third-party access page of 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.
How we protect and delete Google user data
Encryption in transit: Striker’s website, app, and API are served only over HTTPS (TLS). Requests made over plain HTTP are redirected to HTTPS, and our application servers accept traffic from the internet only through our load balancer.
Encryption at rest: Google access and refresh tokens are encrypted with AES-256-GCM before they are stored. Each encryption uses a new data key, which is itself encrypted with a key held in Google Cloud Key Management Service. That key rotates every 90 days.
Access control: tokens are decrypted only on our servers and are never sent to your browser. The decryption key can be used only by the Striker API service and by the Tyrell administrators who own our Google Cloud project.
Separation between customers: every organization’s data is scoped to that organization. Each encrypted token is bound to its organization and cannot be decrypted in the context of another one.
Where data is stored: Striker’s servers run on Google Cloud in Santiago, Chile. Our database is hosted by Neon.
Retention: we keep the emails Striker sent for you and their Gmail message and thread IDs as part of the conversation, for as long as your organization keeps that conversation in Striker.
Revocation and deletion: when you disconnect Gmail or Google Calendar in Striker, we ask Google to revoke Striker’s access and we delete the stored tokens. You can also remove Striker at any time from your Google Account’s third-party access page (https://myaccount.google.com/connections). To delete other Google user data, email contact@tyrell.so with the subject “Data deletion request”. We aim to complete verified requests within thirty days, unless the law requires us to keep the data.
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.