GigcallPrivacy policy
Effective date: 2026-10-15
Who we are
Gigcall is operated by Yugwinderpal Singh ("Gigcall", "we", "us"), of 245 Fenton St, New Westminster, BC V3M 5H8, Canada. For the purposes of the EU/UK General Data Protection Regulation, Yugwinderpal Singh is the data controller for the personal data described in this policy.
Canada. We handle personal information under Canada's PIPEDA and British Columbia's Personal Information Protection Act. Yugwinderpal Singh is the individual accountable for our compliance (contact details below). You may also complain to the Office of the Privacy Commissioner of Canada or the Office of the Information and Privacy Commissioner for British Columbia.
What Gigcall does not do
Gigcall contains no advertising SDK, no analytics SDK, and no tracking of you across other companies' apps or websites. It does not access your device's location or your device's address book, and it does not request permission to do either.
What we collect, and why
| Data | Why we collect it |
|---|---|
| Email address | To create your account and let you sign in (a magic link or a password), and to send account-related email (confirmations, password resets). |
| Display name | Shown to the other people on a tour you share with them, so a roster reads as people rather than email addresses. |
| Tour content you enter | Tours, show days, schedules, notes, advance questions and answers, guest lists, lodging and travel details, and the contact details (names, phone numbers, emails, companies) of third parties you work with — promoters, venue staff, drivers and the like. This is the content of the service: it exists so your tour's day sheet can be built, shared and synced. |
| Files and photos you attach | Stage plots, riders, input lists and similar documents you choose to attach to a day or a schedule item. |
| Account id | A unique id for your account (also used as your subscription identity with our billing provider), so your data and your subscription both follow you across devices. |
| Referral information | If you joined Gigcall using someone's invite code, a record that they invited you. If you've invited others, their display name, when they joined, and whether they've since bought a paid plan — used to credit whoever invited a new subscriber with a free month of Solo, and to show you who you've brought in. Never shown to anyone but the two people involved. |
| Notification preferences | Whether you've muted a tour's alerts (or all of them), and any quiet hours you've set — a start time, an end time, and the time zone you chose for them, never your device's location. Used to decide when, and whether, to push you an alert. |
| Push notification token | Only if push notifications are enabled and you grant permission — used, together with which platform it's for (iOS, or Android once the Android app is released), to deliver an alert to your device when something on a tour you're on changes. Deactivated the moment you sign out on that device; deleted entirely when you delete your account. |
| Edit history | A before-and-after copy of edits to a tour's day sheets, schedule, advance answers, contacts, files and guest list — which can include the third-party contact details described above — so the in-app History screen can show who changed what, and so two people editing the same field at the same time are resolved fairly instead of one silently overwriting the other. Kept 90 days. |
| Overwritten-change notices | When your edit to a field is overwritten by someone else's more recent change, a note of the value you tried to save, the value that stands, and who wrote it — so you find out even if you're offline again by the time it happens. Kept 30 days. |
| Subscription status and purchase history | To know which plan you're on and enforce its limits — collected via the App Store (or Google Play, once the Android app is released) and our billing provider, never as card or bank details, which we never receive. |
| Crash reports and other diagnostic data | Only on builds with crash reporting configured — to find and fix bugs. Reports carry your account id and nothing else personal (no name, no email, no screenshots), plus device model, OS version, app version and anonymous release-health session data. Kept for up to 90 days. |
| Diagnostics report you choose to send | Not collected by us automatically: the app's "Send diagnostics" feature builds a plain-text report on your device (app version, sync status, your account id — no tour content, no names, no addresses) and hands it to your device's share sheet. It reaches only whoever or wherever you personally choose to send it; no Gigcall processor receives it. |
Legal bases for processing (EU/UK GDPR)
- Performance of a contract (Art. 6(1)(b)) — your account, your tour content, and your subscription, all of which exist to provide the service you signed up for.
- Legitimate interests (Art. 6(1)(f)) — crash reports and basic security logging, to keep the service working and secure, balanced against your right to privacy by collecting the minimum described above.
- Consent (Art. 6(1)(a)) — push notifications, which your device asks you to allow separately, and which you can withdraw at any time in the app or your device settings.
- Legal obligation (Art. 6(1)(c)) — where we are required to keep certain billing records for tax or accounting purposes.
Who we share it with
We use a small number of processors to run Gigcall. Each receives only what it needs to perform its function, under contract, and none of them may use your data for their own advertising.
| Processor | What it does |
|---|---|
| Supabase | Our database, authentication, file storage and server-side functions |
| PowerSync (JourneyApps) | Offline-first sync between your devices and our database |
| RevenueCat | Subscription management for the App Store (and for Google Play, once the Android app is released) |
| Apple (App Store, APNs) / Google (Firebase Cloud Messaging; Google Play, once the Android app is released) | In-app purchases, and push notification delivery. When the changed item is visible to everyone on the tour, the notification's own text — a short summary of the change and the display name of whoever made it — passes through FCM and, on iOS, APNs to reach your device; a notification about a restricted item is generic instead. |
| Sentry | Crash reports and other diagnostic data (on builds where it is configured) |
| Google (Gmail SMTP) | Sending sign-in, password-reset and confirmation email from gigcall01@gmail.com |
International transfers. Your account and tour data are stored in the United States (Supabase on AWS us-west-2; PowerSync's US region), and the other processors above also operate outside your own country, including in the United States. If you are in Canada, the EEA or the UK, your personal data is therefore transferred to and stored in the US. Where that is the case, we rely on the safeguards each processor provides for international transfers (such as the EU Standard Contractual Clauses or an equivalent adequacy mechanism). Contact us at gigcall01@gmail.com for details of the safeguards in place for a specific processor.
This website is hosted on GitHub Pages; GitHub may log visitor IP addresses under its own privacy statement.
We do not sell your data, and we do not share it with data brokers or for third-party advertising.
How long we keep it
- Your account and its content, while active — for as long as you keep the account.
- Deleting a single item (a schedule item, a contact, a whole tour) — recoverable for 30 days from "Recently deleted" in the app, then permanently removed by an automated nightly job. Attached files are removed from storage the same way.
- Edit history and change notices. The before-and-after copy behind the in-app History screen is kept 90 days, then permanently deleted; a notice that your edit was overwritten by someone else's more recent one is kept 30 days. The internal log used to deliver a push notification (its summary text and who made the change) is kept for up to 30 days after it is sent, then deleted.
- Deleting your account — handled immediately: your account, any tour you own that nobody else is still on, your membership on every other tour, your notification preferences, your push token, your subscription-status record, any referrals or rewards on your side as the referrer, and any unread overwritten-change notice addressed to you are all deleted as part of that one request (not held in a 30-day window the way a single deleted item is). If you own a tour — or an organisation — that other people are still active on, you'll be asked to transfer or empty it first, so their day sheets (or the organisation's roster) are not deleted out from under them. See Delete your account for the full detail, including what a few things (purchase records, Sentry events, an edit you made on a tour you've left) outlive the account by.
- Backups. Our infrastructure providers may keep routine backups for disaster recovery on their own standard schedules; we do not separately publish a fixed backup-retention number here because it is set by that infrastructure rather than by Gigcall's own code, and we recommend confirming current figures with us at gigcall01@gmail.com if this matters to you.
Your rights
Depending on where you live, you may have the right to access, correct, export, delete, or restrict our use of your personal data, and to object to processing based on legitimate interests. To exercise any of these:
- Access and export — the app's "Export my data" feature (account sheet) gives you a copy of your own tour content at any time.
- Deletion — delete individual items in the app, or your whole account from the account sheet, or by request at gigcall01@gmail.com or https://yuvibabbar-dev.github.io/gigcall/delete-account.html. See Delete your account.
- Correction — edit your display name, email or tour content directly in the app at any time.
- Other requests — write to gigcall01@gmail.com or 245 Fenton St, New Westminster, BC V3M 5H8, Canada. We will respond within the time required by applicable law.
If you are in the European Economic Area or the UK, you also have the right to lodge a complaint with your local data protection authority.
Children
Gigcall is a professional tool for touring and live-event production and is not directed at, or intended for, anyone under 16 years old. We do not knowingly collect personal data from children under 16. If you believe a child has provided us with personal data, contact gigcall01@gmail.com and we will delete it.
Security
Connections between the app and our processors are encrypted in transit (HTTPS/TLS). Sign-in, password-reset and confirmation emails are delivered by Google's mail service like any other email, so they are not end-to-end encrypted. Access to tour content is restricted by row-level security to the people invited onto that specific tour. No system is perfectly secure, and we cannot guarantee absolute security, but we design the service — offline-first, row-level access control, minimal data collection — to limit what there is to protect.
Changes to this policy
We may update this policy as the service changes. We will change the effective date above when we do, and for material changes we will make a reasonable effort to notify you in the app or by email.
Contact
Yugwinderpal Singh
245 Fenton St, New Westminster, BC V3M 5H8, Canada
gigcall01@gmail.com