Privacy Policy
We collect the minimum, keep it no longer than needed, and never sell it. This policy explains exactly what that means, in the same plain language we use everywhere else. We review it periodically and whenever the product changes in a way that affects your data.
The short version
We need your name and email to give you an account, and a few request headers to count clicks. We do not use advertising or analytics cookies, we do not fingerprint, we do not store the IP address of people who click your links, and we do not sell or rent personal data.
This policy covers two groups of people: account holders who use zerosoft, and people who interact with what our account holders publish: people who click a short link, book a meeting, or write in a chat widget.
Who is responsible for your data
zerosoft is the controller (the party that decides how and why data is used) for account data, data about the use of zerosoft.ai, and the communications we send to account holders.
For data that account holders collect through the products (CRM contacts, booking guests, chat visitors and link clicks), the account holder is the controller and zerosoft processes the data on their behalf. If you booked a meeting, chatted with a business or clicked a link and want to exercise your rights, please contact that business first; we will help them respond, and you can also write to us.
If you self-host zerosoft, you are the controller of everything in your instance and we never see it.
What we collect
- Account data: your name, email address and profile picture, provided by Google when you sign in, plus your workspace memberships and settings.
- Sign-in and security records: when you sign in we record the session (time, IP address and browser), sign-in and two-step events, and, if you turn it on, an encrypted two-step secret and hashed recovery codes. Workspace owners and admins can see these events for their members in the workspace audit log.
- Workspace content: the links, contacts, deals, bookings, issues, conversations, documents and files you and your team create.
- Link click data: when someone follows a short link we record the time, the link, the referrer's domain, the approximate country, the device type, the browser and the operating system. We do not store the IP address or the full user-agent string with the click.
- Video view data (Rec): when someone plays a video shared from Rec we record the time, how much of the video they watched and which parts, button clicks, the name they choose to give, and, if they are signed in, their account. We also record the approximate country, region and city provided by our hosting provider, the device type, the browser, the operating system and the domain of the site they came from. We do not store the IP address or the full user-agent string with the view. Only the person who recorded the video and workspace admins who manage it can see this data.
- Booking data: when someone books through a Cal page, the name, email, answers to the host's questions, time zone and language they provide, and the booking details.
- Chat data: messages written in a Chat widget, the name and email if the visitor chooses to give them, attachments they upload, satisfaction ratings, and a random visitor identifier stored in the visitor's browser so the conversation continues across visits.
- Google integration data, only if you connect it: for Gmail, the emails exchanged with your CRM contacts (sender, recipients, subject, date, message and thread IDs, and the message body: plain text plus a sanitized copy of the HTML, size-limited, without attachments or remote images), and the emails you send from the CRM through your Gmail; for Google Calendar, your busy and free times and the events that bookings create in your calendar.
- Integration secrets: OAuth tokens for Google, and webhook signing secrets, stored encrypted. API keys are stored only as hashes. A Bitly token you give us for an import is used for that import and not stored.
- Technical data: IP addresses are used briefly for rate limiting and appear in our hosting provider's request logs (see Retention). Email delivery status for the transactional emails we send.
- Messages you send us: emails to our support, privacy, abuse or security addresses.
- Bookings and CRM: when someone books a meeting through Cal, their name, email, the meeting time and their answers are also saved as a contact and a meeting activity in the host's CRM. When an agent chooses to, a Chat conversation is saved to the visitor's CRM contact.
- Email tracking for emails sent from the CRM, when the account holder keeps it on (it can be turned off for the workspace or for each email): an invisible image and rewritten links record when the email is opened or a link is clicked: the time, the link and the browser user agent, not the IP address. Sequence emails include a link to unsubscribe; unsubscribing stops further sequence emails to that address.
- Feedback: if you send feedback through the site or the app, we keep the message, the type and product you picked, the page you were on, your browser's user agent, and your email if you give it or are signed in.
What we do not collect
- No advertising or analytics cookies, and no third-party trackers on zerosoft.ai.
- No device fingerprinting and no cross-site tracking.
- No IP addresses stored with link clicks.
- No passwords: you sign in with Google or a one-time email code. Link passwords are stored only as salted scrypt hashes.
- Nothing from emails that do not involve your CRM contacts, and no attachments.
- No payment card details: we do not charge today. When paid plans launch, payments will be handled by a payment processor that we will name here first.
Cookies and local storage
We use only what is needed for the service to work: a session cookie that keeps you signed in, a language-preference cookie, a short-lived cookie that remembers you unlocked a password-protected link (up to 7 days), and browser local storage for interface preferences such as a collapsed sidebar. We also set a time-zone cookie so dates show in your local time, and a cookie with a hash of the signed-in account so pages saved for offline use are only shown to the person who saved them.
The Chat widget, when a business installs it on its website, stores a random visitor identifier in that website's local storage. It does not track the visitor on other sites. Because these are strictly necessary for features people asked for, we do not show a cookie banner; businesses that install the widget should mention it in their own privacy notice.
How click analytics work without cookies
When a browser follows a short link, it tells us where it came from (the Referer header, of which we keep only the domain), what it is (the User-Agent header, which we reduce to device type, browser and operating system) and roughly where it is (a country code provided by our hosting provider at the network edge, or resolved from the IP address on self-hosted instances).
We save those few fields and never save the IP address with the click. That is enough for honest statistics (clicks per day, per referrer, per country) without following anyone around the internet.
How we use data
- To provide the service: show your dashboard, count your clicks, schedule your bookings, deliver chat messages, sync the integrations you connect, and send the emails the products are designed to send, such as booking confirmations with calendar files.
- To keep it secure: rate-limit requests, detect and stop abuse such as phishing links, block attacks, and debug errors.
- To communicate with you: service and security notices, and changes to these policies. We do not send marketing emails today; if we ever do, you will be able to opt out at any time.
- To comply with the law and respond to valid legal requests.
- Never to sell, rent or share personal data for advertising, and never to train AI models on your content.
Google user data
If you connect Gmail or Google Calendar, zerosoft requests only the access each feature needs: Gmail read access to show the emails exchanged with your CRM contacts in their timeline (and to detect replies that stop a sequence), Gmail send access to send the emails and sequence steps you write in the CRM from your own address, and Google Calendar free/busy plus event access to avoid double bookings and to add, update or cancel the events your bookings create. Gmail data is used only for these features: it is not used for advertising, not sold, and not used to train AI models. You can disconnect at any time from the product settings or from your Google account.
zerosoft'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.
In practice: we use Google user data only to provide and improve the user-facing features that use it; we do not transfer it to others except as needed to provide those features, to comply with the law, or as part of a merger or acquisition with notice to you; we do not use it for advertising; we do not use it to train generalized AI or machine learning models; and no human at zerosoft reads it unless you give us explicit permission for specific messages, it is necessary for security purposes such as investigating abuse, or it is required by law.
Legal bases
Under the GDPR (EEA and UK) and Brazil's LGPD, we process account data and workspace content to perform our contract with you; security data, rate limiting, logs and abuse prevention under our legitimate interest in running a safe, reliable service (and to prevent fraud); and data needed to meet legal obligations under those obligations. Where we rely on consent, such as optional integrations, you can withdraw it at any time by disconnecting them.
Under Argentina's Personal Data Protection Law (Law 25,326), we process data with your consent or because it is necessary for the contractual relationship with you, within the exceptions the law provides.
Who we share data with
We do not sell personal data. We share it only with the service providers (subprocessors) that run the cloud for us, under contractual confidentiality and data-protection terms, and only as needed for their job: The current list, with what each provider processes, is on our subprocessors page (/subprocessors).
- Vercel: hosting, serverless functions, file storage for uploads (Vercel Blob), scheduled jobs and the AI Gateway.
- Turso: the database where account and workspace data is stored.
- Railway: runs the WhatsApp gateway used by Lines and Inbox when you connect a WhatsApp number.
- Resend: delivery of transactional emails, such as sign-in codes, workspace invitations, notifications and booking confirmations.
- Google: sign-in, and Gmail and Google Calendar only when you connect them.
- AI model providers, through the Vercel AI Gateway or OpenRouter, only for AI features you use, under terms that do not allow training on your content.
- Destinations you choose: if you configure webhooks or the API, data is sent to the URLs and tools you set up.
- Authorities, when the law genuinely requires it; we will push back on requests that are overly broad.
- A successor, if zerosoft is merged or acquired; we will notify you before your data becomes subject to a different privacy policy.
International transfers
Our providers process data in the United States and possibly other countries, which may not offer the same level of protection as yours. Where the GDPR, the LGPD or Law 25,326 require it, we rely on appropriate safeguards for these transfers, such as standard contractual clauses offered by our providers. If we change providers or the region where data is stored, we will update this page in advance.
Retention
- Account data and workspace content: kept while your account is active.
- After you close your account: exportable for 30 days, then deleted from the production database. Remaining copies in provider backups expire on the providers' backup schedules, and we aim for full deletion within 90 days.
- Link click data: kept as individual records without IP addresses while the link and account exist, so you can see your history.
- Video view data (Rec): kept without IP addresses while the video exists. Deleting the video deletes its views.
- Rate-limit records: they contain the IP address and are deleted automatically shortly after their window ends (at most 10 minutes).
- Sessions and the security audit log (IP address and browser): sessions are deleted 90 days after they end; audit log entries after one year.
- Hosting request logs: they include IP addresses and are kept by our hosting provider for a limited period under its retention settings; we do not copy them into long-term storage.
- Booking, chat and CRM data: kept as long as the account holder keeps it, or until they or you request deletion.
- We may keep limited data longer when the law requires it or to resolve disputes and prevent abuse, for example records of accounts suspended for phishing.
Security
We protect data with HTTPS, encryption of secrets at rest, hashing of keys and passwords, and least-privilege access. Details are on our Security page. No system is perfectly secure; if a breach affects your personal data, we will notify you and the competent authorities as the applicable law requires.
Your rights
Wherever you live, you can ask us to access, correct, delete or export your personal data, to restrict or object to its processing, and to withdraw consent. Depending on your country you may have additional rights, such as confirmation that we process your data and information about who we share it with (LGPD), or free access to your data at intervals of at least six months (Law 25,326).
You can download all your data as a ZIP and delete your account or workspace yourself in Settings › Profile, and each app has its own export. For anything else, write to privacy@zerosoft.ai. We may need to verify your identity. We answer within the deadline set by your local law (for example, 10 calendar days for access requests under Argentine law) and in any case within 30 days.
Businesses that need a data processing agreement (GDPR art. 28) can request ours at privacy@zerosoft.ai.
You also have the right to complain to a data protection authority: in the EEA or UK, your local supervisory authority; in Brazil, the ANPD; in Argentina, the Agency for Access to Public Information (AAIP), which, as the enforcement body of Law 25,326, is empowered to handle complaints from anyone whose rights are affected by non-compliance with data protection rules. We would appreciate the chance to fix things first.
Children
Accounts are for adults. The service is not directed at children under 16, and we do not knowingly collect their data. If you believe a child has given us personal data, write to privacy@zerosoft.ai and we will delete it.
Self-hosted instances
If you run zerosoft on your own servers, your data stays wherever you put it and this policy does not apply to it. We receive nothing from your instance: license keys for enterprise features are verified offline.
Changes and contact
We review this policy periodically. Changes will be posted here with a new date; material changes will be announced to account holders by email at least 15 days before they take effect.
Privacy questions, requests and complaints: privacy@zerosoft.ai.