Privacy Policy
Last updated November 21, 2026
Shelya (“we”) puts a “Talk to the founder” button inside software products. This policy explains what we collect from founders who sign up at shelya.si and from the people (“visitors”) who start a call through a founder’s app, why, and what control you have.
Signing in with Google
When you sign in with Google we receive your name, email address, profile photo and Google account ID. We use them only to create and secure your Shelya account, show who you are in the dashboard, and email you when someone calls. We don’t ask for access to your Gmail, Drive, contacts or any other Google data. Calendar access is separate and optional (below).
Shelya’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 don’t sell Google user data, use it for advertising, or use it to train AI models.
Connecting Google Calendar
Founders can choose to connect a Google Calendar, so a visitor whose call was missed can book a time, and so the founder can promise to call back later. When you connect it, we ask for two permissions and use them only for this:
- See when you’re busy (calendar.freebusy): when a visitor opens “Pick a time”, we read the busy and free times on your primary calendar for the next two weeks and hide the times you’re busy. We get only start and end times, never event titles, guests or details, and we don’t store them.
- Create events (calendar.events): when a visitor books a time, or you choose “call back in 30 minutes”, we create one 30-minute event with a Google Meet link on your primary calendar and invite the visitor’s email. We don’t read, change or delete any of your other events.
- We keep the Google refresh token encrypted, plus the time, Meet link and visitor email of each booking on that call’s record. Disconnecting the calendar or deleting your account revokes the token right away. You can also remove access at any time in your Google account settings.
Who we share Google user data with
We don’t sell, rent or share Google user data with anyone, and we don’t use it for advertising. The only disclosures are these:
- The visitor who books: the calendar invite we create (its time and Google Meet link) is sent to the visitor’s email address, because that’s the point of the booking. Visitors never see your other events or your busy and free times, only which open slots they can pick.
- Our infrastructure providers: Google Cloud (where the Shelya API runs) and MongoDB Atlas (where the encrypted token and booking records are stored) process this data only to run Shelya for you, under their data processing terms.
- When the law requires it: if we’re legally compelled to disclose data, we’ll disclose only what’s required and tell you unless we’re prohibited from doing so.
AI and Google user data
Shelya uses AI services (listed below) to answer calls and write transcripts. Google user data is never sent to any AI service. Your calendar’s busy and free times, your events and your Google account details are handled only by Shelya’s own servers, and are never given to the AI that answers calls, the speech-to-text service or the voice service, or used in any prompt.
We don’t use Google user data, raw, aggregated, anonymized or derived, to create, train or improve any machine learning or AI model, ours or anyone else’s.
The use of raw or derived user data received from Google Workspace APIs will adhere to the [Google User Data Policy](https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
How we protect your data
- Encryption in transit: all traffic between your browser, our apps, our servers and Google uses HTTPS (TLS).
- Encryption at rest: the Google Calendar refresh token is encrypted with AES-256-GCM before it’s stored, using a key held separately in Google Secret Manager, so a copy of the database alone can’t be used to reach your calendar. Our database (MongoDB Atlas) and recording storage (Google Cloud Storage) are also encrypted at rest.
- Least data: we ask only for the two calendar permissions above. We read busy and free times when a visitor needs them and don’t store them.
- Access control: production systems and secrets are available only to Shelya’s own staff, and only to run and support the service. Recordings are served only through private links that expire after an hour.
- Revocation and deletion: disconnecting the calendar or deleting your account revokes Google access right away and deletes the stored token.
- How long we keep it: busy and free times are never stored. The refresh token is kept until you disconnect the calendar or delete your account. Booking details stay on the call’s record until the call or your account is deleted. Events already created in your Google Calendar are yours and stay there unless you delete them.
What we collect
- Founder account: the Google profile above, your widget settings, Shelya instructions, allowed websites and billing status.
- Visitor details: the fields the founder’s app chooses to share when a visitor starts a call (for example name, email, company and plan), the page address, and a one-way hash of the visitor’s IP address for abuse limits.
- Calls: the voices of the people on the call, and a live copy of the visitor’s page in that app (its layout and text, with password fields always hidden and anything the founder marks private left out). The page is copied only during a call the visitor started.
- Recordings and transcripts: every call is recorded, and both people are told before it starts. We keep the video of the page, the audio and a written transcript.
How we use it
- To connect the call, ring the founder and show the founder the visitor’s page.
- When the founder can’t pick up, to let Shelya answer for the founder, using the founder’s instructions and the live page.
- To store recordings and transcripts so the founder and the visitor can rewatch them.
- To bill founders, prevent abuse and keep the service running.
Who processes it for us
We use these providers to run Shelya, each only for the purpose listed:
- Google Cloud: hosting, recording storage and task scheduling
- LiveKit: real-time audio and data for calls, and recording
- MongoDB Atlas: account and call data
- Cloudflare: website hosting and email delivery
- Deepgram: speech-to-text for transcripts and Shelya
- Anthropic and ElevenLabs: Shelya’s reasoning and voice
- Stripe (through Autumn): payments
- The AI providers (Anthropic, Deepgram and ElevenLabs) receive only what’s said on a call and the visitor’s page, never Google user data. We use their paid APIs. Anthropic doesn’t train on API data, and we opt out of Deepgram’s model improvement program on every request.
How long we keep it, and deleting it
Recordings and transcripts stay until the founder or the visitor deletes them. Either of them can delete a recording at any time from its page, and it’s removed from storage right away. Founders can delete their account and all its calls at any time from the Shelya iPhone app (Delete account), which removes them right away and revokes Google access, or by emailing hello@shelya.si; we do it within 30 days. Visitors can also ask us directly, or ask the founder whose app they used.
Your rights
You can ask for a copy of your data, a correction, or deletion, and you can object to how we use it. Email hello@shelya.si and we’ll answer within 30 days.
Changes
If this policy changes in a way that matters, we’ll email founders before it takes effect and update the date above.