Privacy Policy

yeskite ("yeskite", "we", "us") runs the website at yeskite.com and the funnels and booking pages served from it. This policy covers two groups of people:

• Sellers: people who create a yeskite account to run funnels and take booked calls.
• Leads: people who fill in a seller's funnel or book a call with a seller.

For a seller's account, we decide how the data is used. For leads, the seller who owns the funnel decides what to ask and how to follow up, and we process the answers on the seller's behalf. If you're a lead with a question about how a seller uses your information, ask that seller first. We'll help if you contact us too.

What we collect

From sellers

• Your email address and password. The password is stored only as a hash.
• Your workspace name and the address of your funnels.
• What you put in your funnels: headings, text, qualifying questions and rules, links, video addresses, and any PDF you upload.
• Your schedule: time zone, weekly hours, call length, breaks between calls, minimum notice, and time off.
• The accounts you choose to connect, described under Google, Zoom, and other services below.
• What you write to us when you ask for support.

From leads

• Name, email address, and phone number.
• Answers to the seller's qualifying questions.
• The time of any call booked, rescheduled, or cancelled.
• Reminder choices: whether you want email reminders and, if you turn on text reminders, the phone number for them and a record of your consent.

Automatically

• To stop abuse, we count how often each network address submits a funnel. We store a one-way hash of the address, not the address itself, and delete the count after a day.
• Our hosting providers keep standard request logs, which include IP addresses and browser details, to run and secure the service.
• Cookies that are strictly needed: one keeps you signed in, and short-lived ones protect the sign-in step when you connect Google, Zoom, or Telnyx. They expire after 10 minutes. We don't use advertising or analytics cookies, and there are no third-party trackers on the site.

How we use it

• To run the service: show funnels, qualify leads by the seller's rules, offer open times, book calls, create meetings, and send the emails and texts a seller has turned on.
• To keep accounts and the service secure, and to prevent abuse.
• To answer support requests and tell sellers about changes to the service.

We don't sell personal information. We don't use it for advertising, and we don't use it to train artificial intelligence or machine learning models.

Google user data

A seller can connect a Google account for two optional features: Google Calendar and Gmail. Each asks for its own permissions, and you can connect one without the other.

Google Calendar

When you connect Google Calendar, yeskite can:

• See the list of your calendars, so you can choose which ones count as busy (calendar.calendarlist.readonly).
• See when you're busy on the calendars you choose, but not what your events say, who's invited, or any other detail (calendar.events.freebusy).
• Add, update, and remove events for calls booked through yeskite(calendar.events.owned). We only write to your main calendar, and only change the events we added.
• See your Google account's email address, to show which account is connected.

We store your Google account email, an encrypted token that lets us reach your calendar, your calendars' names and IDs, the calendars you chose, and the start and end of each busy period in your booking window. Busy periods are replaced each time we check, which is when leads look for a time and at most once a minute.

Each event we add is titled "Call with" and the lead's name. Its description has the lead's email address and phone number and a link to your dashboard, and its location is the Zoom link. We don't add the lead as a guest, so Google doesn't email them.

Gmail

When you connect Gmail, yeskite can send email as you (gmail.send) and see your account's email address. It can't read, search, change, or delete any of your email. We use it to send booking confirmations, change and cancellation notices, and reminders to your leads, the booking notices you turn on for yourself, and one test email to you when you connect. Gmail keeps a copy in your Sent folder. We store your Gmail address and an encrypted token.

How Google user data is used and shared

• We use Google user data only to provide the features above to you.
• We don't sell it, use it for advertising, or use it to build user profiles, and we don't use it to train artificial intelligence or machine learning models.
• We don't transfer it to anyone except the infrastructure providers who run yeskite for us (see who we share with), or where the law requires it.
• No person reads it unless you ask us to for support, it's needed to investigate abuse or a security issue, or the law requires it.

yeskite'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.

Disconnecting Google

Disconnecting Google Calendar or Gmail in yeskite deletes its saved token, and for Google Calendar also deletes your saved busy periods and any calendar updates still waiting to be sent. We then revoke our access at Google. Google grants one access for both features, so if you still use the same Google account for the other one, we wait to revoke it until that's disconnected as well. Events already on your calendar and emails already sent stay where they are. We keep the account's email address and the names of your calendars so the dashboard can show what was connected. They're deleted with your account. You can also remove yeskite at any time from your Google Account. Then disconnect in yeskite too, so the saved token is deleted. Step-by-step instructions are in the Google guide.

Zoom user data

Sellers connect a Zoom account so that every booked call gets its own meeting. When you connect Zoom, yeskite can:

• See your Zoom user ID and email address, to know which account is connected (user:read:user).
• Create a meeting for each booked call, move it when the call is rescheduled, and delete it when the call is cancelled (meeting:write:meeting, meeting:update:meeting, meeting:delete:meeting).
• List your scheduled meetings, only to find a meeting we created when Zoom's reply was lost, so we don't create it twice (meeting:read:list_meetings).

We don't access recordings, transcripts, chat, contacts, participant lists, or anything said in a meeting.

We store your Zoom user ID, your Zoom email address, encrypted tokens that let us reach your account, and for each booked call, the meeting's ID and join link. Each meeting we create is titled "Call with" and your workspace name, has the waiting room on, and has a description containing the lead's private link to change or cancel the call. The join link is shown to the lead and to you, and goes in the calendar invite and booking emails.

Disconnecting or removing Zoom

• Disconnecting in yeskite revokes our access at Zoom and deletes the saved tokens. We keep your Zoom user ID and email address, and the meeting links on your bookings, so existing links keep working and reconnecting the same Zoom account picks up where it left off.
• Removing the app from the Zoom App Marketplace makes Zoom notify us. We then delete your Zoom connection, including your Zoom user ID, email address, and tokens, remove the Zoom meeting IDs and links from your bookings, and drop any meeting updates still waiting to be sent. The bookings themselves stay. Meetings already in your Zoom account stay there until you delete them.

Step-by-step instructions are in the Zoom guide.

Other services sellers connect

• Telnyx, for text reminders. We send Telnyx the lead's phone number and the reminder text, and receive delivery updates.
• Resend, Postmark, or SendGrid, instead of Gmail. We store your API key encrypted, plus your sender address, and send each email's recipient and content through your account.

These services handle the data under their own terms and privacy policies, and bill your own account for anything they charge.

Who we share it with

• The seller. A lead's details and answers go to the seller whose funnel they filled in.
• Infrastructure providers who run yeskite for us: Supabase for the database, sign-in, and file storage, and Render for hosting. They may process data in countries other than yours.
• Services the seller connects, as described above, and only for the features the seller turned on.
• When the law requires it, or to protect the rights, safety, or property of our users, the public, or yeskite.
• A buyer or successor, if yeskite is sold or merged. This policy will keep applying to your data, and we'll tell sellers before it changes.

Security

Data travels over HTTPS. Tokens and API keys for connected accounts are encrypted with AES-256-GCM before they're stored, and the database only lets each workspace reach its own records. Uploaded PDFs are kept in private storage and reached through short-lived links. No system is perfectly secure. If we learn of a breach that affects your data, we'll tell you without undue delay.

How long we keep it

• Account and funnel data: for as long as the account exists.
• Lead data: until the seller deletes the lead, or the seller's account is deleted.
• Connection tokens: until the account is disconnected, as described above.
• Google busy periods: until the next check, and deleted when you disconnect.
• Abuse counters: one day.
• Support emails: as long as they're needed to help you.

To delete your account, email passbyappsupport@gmail.com from the address you sign in with. We'll delete your workspace and everything in it, including leads, bookings, connections, and uploaded files, within 30 days. Copies in our providers' backups are overwritten on their normal schedule.

Your rights

Depending on where you live, including under the GDPR, the UK GDPR, and California law, you may have the right to:

• see the personal information we hold about you and get a copy of it,
• correct it,
• delete it,
• object to or limit how we use it,
• withdraw consent you gave, such as for text reminders, and
• complain to your data protection authority.

To use any of these rights, email passbyappsupport@gmail.com. We'll reply within 2 business days and finish within 30 days. We may ask you to confirm the request from your account's email address. We won't treat you differently for using them. Where the GDPR applies, we rely on our contract with sellers to run their accounts, on legitimate interests for security and abuse prevention, and on consent for text reminders.

Leads can also reply STOP to any text reminder, turn text reminders off from their booking page, or ask the seller to delete their details. Sellers can delete a lead from the Leads page in the dashboard.

Children

yeskite isn't meant for anyone under 16, and we don't knowingly collect their information. If you think a child has given us personal information, email passbyappsupport@gmail.com and we'll delete it.

Changes to this policy

When this policy changes, we'll update the date at the top. If a change affects how we use data you've already given us, including data from Google or Zoom, we'll email sellers before it takes effect and ask for consent where the law requires it.

Contact

Questions or requests about privacy: passbyappsupport@gmail.com. See also our Terms of Service.