Privacy policy
Last updated: November 7, 2026
Your data is yours. You can export all of it, or delete your account yourself, anytime. Here's what GiggedIn keeps, who else touches it, and why.
What we collect
Your account. There are no passwords. You sign in one of two ways:
- With Google. Google shares your name, email address, profile picture link, and account ID, and our sign-in service stores them. GiggedIn itself uses only your email address and name. Your picture is never shown. Signing in keeps no access to your Google account. Connecting a Google calendar is a separate step, with its own permission (see "Calendars you connect").
- With an emailed link. We have your email address.
Your business data. The gigs, clients, contacts, invoices, rates, locations, travel, and expenses you put in. Plus two kinds of upload, both stored privately: receipts on your expenses, and your invoice logo. When you import a spreadsheet, GiggedIn reads it and never stores the file.
Cloud links. A cloud link stores an address, never a file, and never connects to your cloud storage provider.
The interest list. If you joined the interest list on our home page, we keep your email address, where you signed up, and when. We use it for one thing: telling you when GiggedIn opens up.
Cookies and your browser. No analytics and no tracking. GiggedIn's cookies are for signing in, nothing else. The ones that keep you signed in last up to 400 days, or until you sign out. A short-lived one finishes a sign-in. Your browser also remembers two small things, on your device:
- your ticks on the guide checklists, if you're signed out
- each list's view (its tab, filters, sort, and search text), for that browser tab only
Server logs. Our hosting providers keep standard technical logs (such as IP addresses and request times) to run the service and keep it secure.
What we don't do
- We never sell your data, and we run no ads.
- We never handle your payment card or bank details.
- No AI service sees your data.
The email GiggedIn sends
Only what it needs to:
- your sign-in links
- the link that confirms you want to delete your account
- when a tester signs in for the first time, an internal notice to us with that tester's email address
If you joined the interest list, you also get one note when GiggedIn opens up. Nothing else.
Calendars you connect
If you connect your own calendars, GiggedIn checks them so the rest of your life counts when you look at a date. It reads them and never adds, changes, or deletes anything in them.
How they connect. Google and Outlook calendars connect through Google's or Microsoft's own sign-in. There, you give GiggedIn permission to see your list of calendars and the events on them, and nothing else. Other calendars connect by a calendar link you paste in, and GiggedIn's server fetches it from wherever that calendar lives. GiggedIn never asks for your calendar password.
You choose which ones. Every calendar starts off. You turn on the ones you want, one by one, and choose how each one counts.
What GiggedIn uses, and what it keeps. GiggedIn reads your calendars only when you look at a date or at your calendar in GiggedIn. From each event, it uses the title, the times, which calendar it's on, whether it's marked free or tentative, and whether it's been declined or cancelled. Anything else that comes with an event is dropped. Events stay in GiggedIn's server memory for a few minutes at most and are never saved to our database or its backups. What GiggedIn stores is the connection (an encrypted key that lets it read your calendars) or the link you pasted (encrypted), plus your settings for each calendar.
Turning off and disconnecting. In Settings, open "Profile & preferences" and use the "Outside calendars" card. Turn a calendar off and GiggedIn stops reading it. Remove a pasted link and GiggedIn deletes it. Disconnect a Google account and GiggedIn deletes its key and asks Google to end its access. Disconnect an Outlook account and GiggedIn deletes its key, so it can't read those calendars after that. You can also remove GiggedIn's access in your Google or Microsoft account's own settings, anytime.
Export and deletion. Your export includes your settings for each calendar, but not the key or any link you pasted. Deleting your account deletes both and asks Google to end GiggedIn's access.
Data from Google. GiggedIn never uses data from Google, your calendars included, to develop, improve, or train AI or machine learning models. GiggedIn's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Your calendar link
Your calendar link works the other way: it sends from GiggedIn to your calendar app. If you subscribe to it, your calendar app (Google Calendar, Apple Calendar, or Outlook) fetches your gigs and travel from GiggedIn, and nothing else. The link never carries money.
Anyone who has the link can see that schedule. If it ever ends up somewhere it shouldn't, go to Settings, open "Profile & preferences", and choose "Regenerate link" on the "Calendar feed" card, then confirm with "Regenerate". That locks the old link out.
Who touches your data
Every account sees only its own data, and the database itself enforces that.
GiggedIn is in beta, and we can access the database directly. We look at your records only when you ask for help and agree to a look, and only at what the problem needs. Each look is noted: who, when, what, and why. Running the service (backups and updates) works on the database as a whole, without anyone reading your records.
These services run GiggedIn. Any data they handle, they handle only to run GiggedIn:
- Supabase: the database, sign-in, and file storage, in the US.
- Vercel: hosting.
- Cloudflare: the domain name. App traffic doesn't pass through it.
- Google: sign-in, if you choose it, and your Google calendars, if you connect them. Address search, timezones, and driving distance, for everyone.
- Microsoft: your Outlook calendars, if you connect them.
- Resend: delivers GiggedIn's email. It receives the sender, recipient, reply-to address, subject, and body.
How addresses reach Google. When you work with addresses, GiggedIn's server talks to Google for you. It sends what you type in an address search once it's 3 or more characters, the ID of the place you pick, that place's coordinates (to find its timezone), and both addresses when you calculate a drive. Your browser never talks to Google's map services.
Keeping and deleting your data
Export everything, anytime. In Settings, open "Profile & preferences" and choose "Export my data" in the "Your account" card.
Delete your account yourself, in two steps. In Settings, open "Profile & preferences" and find "Delete your account".
- "Delete account" emails you a link. It works for 30 minutes.
- The link opens a page that asks you to type your email address. Then choose "Permanently delete my account".
Your uploaded files are removed at once. Everything else is gone from everywhere within 30 days, backups included, with one exception.
If you were invited to the beta, your invitation (just your email address) stays on our list so you can come back. Email hello@giggedin.io and we delete that too.
Leave the interest list. Email hello@giggedin.io and we delete your entry.
Contact
Questions about your data, or anything on this page? Email hello@giggedin.io.
Changes
When this policy changes, the new version lands on this page with a fresh date at the top. No quiet goalpost moves.