your data, your rules.
Last updated: October 22, 2026.
◆ TLDR
- We collect only what's needed to run the service.
- We don't sell your data. Ever.
- We don't use it to train external AI models.
- You can request data export or deletion at any time.
- We use cloud providers in Chile and the US with proper agreements.
→ Data deletion
Request deletion of all your data at heysteff.com/data-deletion →
1. Who we are
Andes USA Investment LLC, a Florida limited liability company with its registered address at 2602 E Hallandale Beach Blvd, Hallandale Beach, FL 33009, United States, operating from Santiago, Chile, is the data controller for heysteff. Contact: [email protected].
2. Data we collect
Account data: name, email, company name, and billing information to operate your workspace.
Usage data: activity logs, performance metrics, and technical records to maintain and improve the service.
Your customers' data: messages, conversations, and contact information your customers send you through connected channels (WhatsApp, Instagram, Messenger, Gmail). We are processors of this data, not primary controllers.
OAuth access tokens: connection tokens for Meta (Facebook/Instagram), Google, and Shopify are stored encrypted in our database to operate channels on your behalf.
3. How we use your data
We use your data exclusively to: deliver and operate the service, process payments, send service communications (changes, incidents, invoices), and comply with legal obligations. We don't use customer data to train global AI models or share it with third parties beyond providers necessary to operate the service.
4. Sub-processors
We use trusted providers to operate the service: cloud infrastructure (servers and database), payment processor (Whop), transactional email provider (Resend), and AI models (Anthropic, OpenAI, DeepSeek, and OpenRouter). All have appropriate data processing agreements. In workspaces that imported data from Google Sheets or Google Contacts, AI only uses Anthropic and OpenAI (see section 7).
5. Meta Platform Data (Facebook & Instagram)
When you connect your Facebook Page or Instagram account to heysteff using Facebook Login, we receive and store the following data through Meta's official APIs (Graph API) and Meta webhooks:
What we receive (Platform Data):
- Direct messages and comments your customers send via Instagram DM, Facebook Messenger, and comments on your Page's posts.
- Conversation metadata: message IDs, timestamps, channel type, and the sending end-user identifier (PSID/IGSID).
- Basic information about the connected Page or account: name, ID, picture, and the permissions you granted us.
How we use this Platform Data: exclusively to deliver incoming messages into the unified inbox of the client that connected the account, allow their team to reply from within our app, and operate the optional AI assistant that the same client trained with their brand voice. Processing is per-tenant and isolated via Row Level Security at the database layer.
What we do NOT do with Platform Data: we do not sell, rent, or share it with third parties; we do not use it to build advertising audiences or marketing profiles; we do not use it to train global or third-party AI models; we do not combine it with data from other tenants.
Retention and deletion: messages are retained per the client's plan and deleted when the channel is disconnected or the workspace is deleted. To request immediate deletion of your Meta data processed by heysteff, visit heysteff.com/data-deletion.
6. Shopify Store Data
When you install the heysteff: WhatsApp Marketing app on your Shopify store, we access and store the following data through Shopify's official APIs (Admin API, App Proxy, and webhooks):
What we receive:
- Order and checkout data: order number, products, amounts, fulfillment status, and abandoned checkouts, to know who to ask for a review and when.
- Customer contact data: the name, email, and/or phone tied to the order, used only to send the review request over the relevant channel (WhatsApp, email).
- Review content: the rating, text, and any photos or videos your customer chooses to submit, along with the associated product.
- Basic store information: name, domain, plan, and owner email, to set up your account.
- Shopify access token: stored encrypted to operate the app on your behalf.
How we use this data: exclusively to request, collect, moderate, and display reviews on your store, and for the notifications and flows you configure. Processing is per-tenant and isolated via Row Level Security at the database layer.
Protected Customer Data: we handle your customers' personal data in line with Shopify's Protected Customer Data requirements: least-privilege access only, encryption at rest and in transit, and no selling or use for advertising or third-party model training.
What we do NOT do: we do not sell or rent your store or customer data; we do not use it to build advertising audiences; we do not use it to train global or third-party AI models; we do not combine it with data from other tenants.
Retention and deletion: data is retained per your plan and deleted when the app is uninstalled or the workspace is deleted. We automatically process Shopify's compliance webhooks (customers/redact, shop/redact, customers/data_request). For immediate deletion, visit heysteff.com/data-deletion.
7. Google User Data (Gmail, Calendar, Sheets and Contacts)
Gmail
When you connect a Gmail account as a heysteff channel using Google Sign-In (OAuth), we access that mailbox through the official Gmail API, only with the permissions you grant:
- Read, send, and modify email (
gmail.modify): to bring the emails that arrive in your inbox into the heysteff inbox, to send from your account the replies written by your team or approved or sent by your workspace's AI assistant (in the same thread, with any attachments included), to mark as read the emails heysteff has already processed and, only if you enable it in the mailbox settings, to create and apply theheysteff/Sin responderandheysteff/Respondidolabels. We do not delete emails or change your filters, account settings, or other labels. - Your Google Account email address (
userinfo.email), to show you which mailbox is connected.
What we store: for each email that arrives in your inbox after you connect it (plus unread emails from the previous half hour), we store the sender, recipients and people in copy, subject, message body, date, Gmail identifiers, and thread headers (Message-ID and References), to display it as a conversation in heysteff and reply in the same thread. Attachments are downloaded and stored on our servers alongside the other files in your inbox, with the same access restricted to your workspace. We do not import automated emails or newsletters (for example, those carrying the Auto-Submitted or List-Unsubscribe headers), or emails from senders or domains you exclude in the channel settings; those emails are discarded without being stored. The exception is bounce notifications: we read them only to mark the bounced reply as undelivered. We also do not import your drafts or the emails you sent from Gmail.
How we use this data: exclusively to provide your workspace's unified customer support inbox. Your team sees the emails in heysteff and replies from there. If you enable the AI assistant, we send the conversation content to our AI providers (see section 4) only to draft the reply to that email and, if you configured who the assistant replies to in that mailbox, to classify the sender (for example, customer or supplier).
Google Calendar
When you connect your Google Calendar account to heysteff using Google Sign-In (OAuth), we access the following data through the official Google Calendar API, only with the permissions you grant:
What we access:
- Your list of calendars (
calendar.readonly), so you can choose which one to connect. - Events on the calendar you choose (
calendar.readonly), to show them in the heysteff calendar view and avoid booking appointments on top of your existing commitments. - Your busy and free times (
calendar.freebusy), to offer only available time slots. - Permission to create, update, and delete events (
calendar.events), so appointments booked, rescheduled, or cancelled in heysteff are reflected on your calendar. - Your Google Account email address (
userinfo.email), to show you which account is connected.
How we use this data: exclusively to keep your workspace's appointments in sync with the calendar you connected and to show your availability inside heysteff. Calendar events that were not created by heysteff are not stored: we read them when you open the calendar view and cache them for at most 90 seconds. Your busy times are checked whenever time slots are offered for booking. In addition, Google notifies us in the background when your calendar changes, and we review those changes only to keep appointments created in heysteff up to date: if you move or delete one of those appointments in Google, we store the new date and time (or cancel it) in heysteff along with a record of the change. All other events are discarded without being stored. Your workspace's AI assistant may use your available time slots to offer and book appointments for your customers; to do so, we send our AI providers only the time slots needed to answer that conversation.
Google Sheets
When you connect a Google account to import a contact list from a spreadsheet, we access Google Sheets with these permissions:
- Access only to the files you choose (
drive.file): you pick the spreadsheet in the Google picker inside heysteff, and we can only read those spreadsheets. We cannot see the rest of your Google Drive, and we do not create, edit, or delete spreadsheets. - Your Google Account email address (
userinfo.email), to show you which account is connected.
What we store and how we use it: from that tab we read the header row and any new rows every few minutes, and we store only the columns you map (first name, last name, phone, email, birthday, or variables you choose) as members of your workspace's contact list, so your team can message them. All other columns are ignored. You can pause syncing or disconnect the account at any time.
Google Contacts
If you choose to import your Google contacts, we access Google Contacts once with the contacts.readonly permission (read-only).
What we store and how we use it: for each contact with a phone number we store the name, phone number, and birthday (if any) as contacts in your workspace, so you can remember their birthdays and message them. Contacts without a phone number are discarded without being stored. It is a one-time import: we do not store the access token and we revoke the permission as soon as it finishes (unless that same Google account has Google Sheets connected in heysteff, because they share the permission; in that case the token still expires within an hour and is not stored). We also request userinfo.email to read the account email. To import again, Google will ask you to authorize again.
Artificial intelligence and Sheets or Contacts data: once a workspace imports data from Google Sheets or Google Contacts, every AI feature in that workspace (assistant replies, summaries, classifications and analytics) only uses providers whose commercial terms prohibit training models on the data they receive through their API: Anthropic and OpenAI (OpenAI also transcribes voice notes). That workspace never sends data to DeepSeek or OpenRouter. The restriction stays in place after the Google account is disconnected, because the imported contacts remain in the workspace.
What we do NOT do: we do not sell or share your Google user data with third parties, except the providers necessary to operate the service; we do not use it for advertising or profiling; we do not use it to develop, train, or improve artificial intelligence or machine learning models, whether our own or third-party, generalized or not; and no person on our team reads it unless you give us explicit consent, it is necessary for security purposes, or it is required by law.
Limited Use: heysteff's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.
Retention and deletion: Google access tokens are stored encrypted. If you disconnect Gmail in heysteff, we delete the tokens, stop accessing your mailbox, and revoke access with Google (if the same account is still connected in another heysteff channel, access is revoked when you disconnect the last one). If you disconnect the calendar, we delete the tokens and stop accessing your calendar. If you disconnect Google Sheets, we delete the tokens and revoke access with Google (as with Gmail, if that account is still connected in another connection, access is revoked when you disconnect the last one); lists already imported are kept. Emails already imported remain in your workspace inbox for the retention period described in section 8, until you delete them or request deletion of the workspace; you can also revoke access at any time from your Google Account. For immediate deletion, visit heysteff.com/data-deletion.
8. Data retention
We retain account data while it's active. Conversation messages are retained per your plan. Upon cancellation, you may request full export and deletion within 30 days. Billing data is retained as required by Chilean law.
9. Your rights
You have the right to access, correct, port, and delete your data. To exercise these rights, email us at [email protected] or use the deletion option at /data-deletion. We respond within 30 days.
10. Cookies
We use strictly necessary cookies for session and authentication. We don't use advertising tracking cookies or share behavioral data with ad platforms.
11. Security
Channel credentials are stored encrypted with XChaCha20-Poly1305. The database uses Row Level Security (RLS) with strict per-tenant isolation. More details at /security.
12. Changes to this policy
For material changes, we'll notify you by email at least 15 days ahead. Questions: [email protected].