Privacy Policy

SiteLaunch Studios operates the SiteLaunch Marketing Cockpit and the website at sitelaunchstudios.com. In this policy, “we” and “us” mean SiteLaunch Studios, and “the Cockpit” means the SiteLaunch Marketing Cockpit application.

This policy covers both the Cockpit and this website. It explains what we collect, what we do with it, who else sees it, and how you get rid of it.

When you create a Cockpit account we hold the email address you sign in with. Authentication is handled by Supabase, and we do not store your password.

Everything else in this category is information you put into the Cockpit yourself. That includes the people and businesses you track as leads: names, organisations, email addresses, phone numbers and how you prefer to reach them. It includes the notes you write, the history of contact you record, the tasks and follow-ups you create, and the activity log those produce.

If you contact us through a form on this website, we receive what you typed into it, so that we can reply.

Running and securing a service produces some information whether anybody intends it or not: the network address a request came from, basic browser and device details, the time a request was made, and records of errors and of whether a scheduled sync succeeded or failed. We use it to keep the service working, to investigate faults, and to notice abuse.

This website uses Google Analytics to measure how visitors find and move through it.

Connecting Google Calendar is optional. The Cockpit works without it, and nothing below happens unless you connect an account yourself.

When you do, the Cockpit asks Google for one permission and no others: https://www.googleapis.com/auth/calendar.events.owned. That permits creating and updating events on calendars you own. It does not permit reading anybody else's calendar, changing your calendar settings, or sharing a calendar.

Two things are accessed under it. The first is the email address of the Google account you connected, so the Cockpit can show you which account is in use. The second is the follow-up events the Cockpit itself created on your primary calendar, so it can keep them up to date when a follow-up date moves.

What the Cockpit does not do is as specific as what it does. It never lists, searches or reads through your calendar. Every request it makes names a single event whose identifier it worked out from one of your own follow-up tasks, so an appointment it did not create is not something it can see. It never deletes a calendar event, for any reason, including when you disconnect. And it never treats an appointment on your calendar as evidence that you contacted somebody: an entry in a diary is not a record of a conversation, and counting it as one would invent history that did not happen.

Only to do the thing you connected the account for: putting your open follow-ups on your calendar as all-day entries, keeping those entries current, and telling you which Google account is connected.

We do not sell Google user data. We do not use it for advertising, and we do not pass it to advertising networks or data brokers. We do not use it to build a profile of you, and we do not use it to train machine learning models.

SiteLaunch Studios’ use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

We share information with the companies whose infrastructure the service runs on, and only as far as running it requires. There are three.

Supabase stores the database and handles authentication, so your account and everything you enter into the Cockpit lives there. Netlify hosts this website and the Cockpit's frontend, and therefore serves the pages your browser requests. Google holds the calendar you connect, and also provides the Analytics and Search Console figures the Cockpit reads for our own properties.

That is the whole list. We do not sell your information, we do not rent it, and we do not share it with anyone for their own marketing.

The token that lets the Cockpit write to your calendar is kept server-side, in Supabase Vault, reachable only by server-side functions. It is never sent to your browser, never included in the Cockpit's JavaScript, and never written into logs or error messages. The browser is told that a connection exists and which account it belongs to, and nothing more than that.

Traffic to the site and to the Cockpit is served over HTTPS, and access to your records is scoped to your own account at the database level rather than only in the application.

We take these measures because they are worth taking, not because they make anything certain. No service can promise that information sent over the internet or held on a computer is perfectly secure, and we are not going to tell you otherwise.

Information you put into the Cockpit is kept while your account exists, because the point of the Cockpit is that last year's contact history is still there this year.

Your Google authorization is kept until you disconnect it or until you ask us to delete your account, whichever comes first. Operational records such as error and sync logs are kept only as long as they are useful for running and securing the service.

In the Cockpit, open Data & Import, find the Follow-up calendar panel, and press Disconnect. That removes the stored authorization from our side immediately and asks Google to revoke it as well. Once it is gone the Cockpit cannot write to your calendar again unless you connect it a second time.

You can also revoke access from your Google account directly, at myaccount.google.com/permissions. Either route stops any further access.

Follow-up events the Cockpit already created stay on your calendar after you disconnect. That is deliberate: you may have planned a week around them, and removing entries from somebody's diary because a connection ended is not a decision this software should make for you. They are ordinary events on your own calendar, and you can delete them yourself at any time.

Write to sitelaunchstudio@gmail.com from the address on your account and ask us to delete it. We will remove your account, the leads, notes, tasks and activity stored against it, and any Google authorization still held, and we will confirm when it is done.

Deleting your Cockpit data does not remove events already on your Google Calendar, for the reason given in the previous section. Those are yours to keep or delete.

The Cockpit is a tool for running a business and is not directed to children. We do not knowingly collect information from anyone under 13. If you believe a child has provided us with information, contact us and we will delete it.

If this policy changes, the effective date at the top of the page changes with it, and the new version replaces this one here. Where a change materially affects what we do with information you have already given us, we will say so rather than rely on you noticing a date.

Questions about this policy, or about anything described in it, go to sitelaunchstudio@gmail.com or (786) 505-5791. We answer in English and Spanish.