Privacy Policy

11. Who is responsible for your data

Setgrid is an independent, non-commercial project operated by a private individual. It is not a company and does not sell your data or run advertising. For any privacy question or data request, contact us at privacy@setgrid.app. We will respond to verified requests as required by applicable law.

22. What data we collect

We only collect the data needed to provide the service.

Account data

When you create an account or sign in, we may collect:

• your email address;
• your public display name and email, if you sign in with Google or Apple;
• your sign-in method (Google, or Apple in the mobile app);
• technical authentication identifiers created by our authentication provider.

Setgrid does not store passwords. Sign-in uses Google (and Apple in the mobile app).

Festival and plan data

When you use Setgrid, we may store:

• festivals you create, import, or publish;
• the artists or sets you select, and your priority categories (Must, Want, Maybe);
• clash resolutions you make, such as dropped sets and manual splits;
• route settings, such as stage transfer times and your walking pace;
• plan titles, stage ordering, and any notes or custom timetable data you add;
• imported timetable data, if you upload, paste, or create your own festival timetable;
• group data, if you join a group: the display name you choose, which of your plans you attach, custom meeting points, and any chat messages, photos, or one-time location pins you send in that group (a location pin stores only the coordinates you explicitly chose to share at that moment — Setgrid never tracks your location in the background);
• your avatar, if you set one: a chosen emoji or an uploaded profile photo (photos are stored publicly);
• calendar sharing, if you use it: the one-time links you create (stored only as a scrambled fingerprint, with when they were made and when they expire) and which accounts you share calendars with;
• push notification identifiers (browser subscriptions and, in the mobile app, device push tokens), if you enable notifications.

You can also use Setgrid without an account. In that case, plans you create may be stored only on your device (in your browser’s local storage), together with a random identifier (stored in a cookie) that lets you keep editing the plans you created on that device. This identifier is not linked to your real identity unless you sign in.

Spotify connection (optional)

You can optionally connect your Spotify account to get personal recommendations (for example, which artists you listen to are playing a festival). If you do, we store the list of artists you listen to on Spotify (names and Spotify artist IDs from your top and followed artists) and a token that lets Setgrid refresh that list. We never see or store your Spotify password, playlists, or listening history, and we never post or change anything in your Spotify account. Your artist list is used only for your own recommendations and is never shown to other users. You can disconnect Spotify at any time from your account page, which deletes the stored artist list and token; you can also revoke Setgrid’s access at spotify.com under “Apps”.

Feedback and requests

If you report a problem, request verification of a festival, or propose a timetable change, we store the request and any message you include so an administrator can review it.

Technical data

• browser and device information;
• approximate usage timestamps and aggregate analytics;
• error logs;
• authentication and session data;
• IP address where necessary for security, abuse prevention, or service operation.

Usage measurement

To learn whether Setgrid is useful during a festival, we count when a saved plan is opened (and which view: plan, now or timetable), when a shared plan or a group invite is opened by someone else, and when the demo is opened. Each count holds the time, the festival, plan or group it was about, and, where there is one, the random identifier of your device or your account id. It holds no names, e-mail addresses, IP addresses or plan contents. Unsent counts wait in your browser’s local storage for up to 14 days. If your browser sends Global Privacy Control, we still count the open but store neither your device identifier nor your account id with it. We keep these counts for 13 months; deleting your account deletes the ones linked to it.

33. How we use your data

• create and manage your account;
• let you save and access your plans across devices;
• show your selected sets, clashes, and route plans;
• provide import, timetable, and planning functionality;
• secure the service and prevent abuse;
• fix bugs and improve Setgrid;
• measure whether Setgrid is useful before and during festivals (usage measurement);
• respond to support requests;
• comply with legal obligations, if required.

We do not sell your personal data.

44. Legal basis for processing

If you are in the European Economic Area, the United Kingdom, or another region with similar laws, we process your personal data on these grounds:

• Performance of a contract: to provide Setgrid, including login, saved plans, and cross-device access.
• Legitimate interests: to secure the service, prevent abuse, debug errors, improve the product, and measure whether it is useful (usage measurement).
• Consent: where we ask for it, for example for any optional analytics or communications.
• Legal obligation: where we must process or retain data to comply with the law.

55. Login and authentication

Setgrid supports Google sign-in (and Sign in with Apple in the mobile app).

If you sign in with Google, we only request the basic profile information needed to identify your account (your email address and public name). We do not request access to your Gmail, Google Drive, Calendar, contacts, or any other private Google data.

Authentication and our database are provided by Supabase, which acts as our processor for these services and publishes its own privacy and data-processing documentation.

66. Sharing and visibility of plans

Your plans are private by default: they are linked to you and are not publicly listed.

If you choose to share a plan, Setgrid creates a link that anyone holding it can open (read-only) and copy into their own plan. You can stop sharing at any time. Festivals can also be shared or published so other users can find and plan against them. Please don’t put personal or sensitive information into shared plans or published festival data.

Groups work the same way: the invite link (or QR code) is the access. Anyone holding it can see the group’s name, member display names and avatars, each member’s picked sets, meeting points, and the group chat. Only members can write. You can leave a group at any time, which removes your membership and picks from it, and you can delete messages and photos you sent at any time.

You can share your calendar with a friend. You create a one-time link (it works once and expires after 7 days); when a signed-in friend opens it and accepts, you both see each other’s calendar: which public festivals the other has a plan for, under the chat name they chose. Nobody sees your plan contents, private or unlisted festivals, your email address or anything else about your account, and there are no public profiles. Either of you can stop sharing at any time from My plans, which ends it for both.

A group chat can be end-to-end encrypted. In encrypted groups, message text and photos are encrypted on your device with a key that travels only inside the invite link — we store only ciphertext and cannot read the content. Information about who sent a message and when remains visible to us, and if every copy of the invite link is lost, that chat history becomes permanently unreadable.

Each festival can also have a public “festival chat”. It is readable by anyone, is NOT end-to-end encrypted (a public room cannot keep a secret key), and messages there carry your chosen chat name and avatar. Writing requires an account; moderators and admins can remove messages. Push notifications for it are off unless you turn them on, per festival.

77. Imported timetable data

If you import a timetable, upload festival data, or create a custom festival, the content you provide may be stored so the timetable can be displayed, edited, or reused in Setgrid. You are responsible for ensuring you have the right to upload or publish any timetable data you add.

88. Cookies and local storage

Setgrid uses cookies and your browser’s local storage to:

• keep you signed in (authentication session cookies);
• let you keep editing anonymous plans you created on a device (a random owner-identifier cookie);
• remember your language and settings;
• store local or temporary plans on your device;
• keep usage measurement counts on your device until they are sent (at most 14 days).

We use Vercel Analytics to understand aggregate usage. It is privacy-friendly and does not use cookies to track you across sites. Our own usage measurement is described in section 2; it is first-party, uses no extra cookies and is never shared or sold. If we add other analytics or tracking tools, we will update this policy.

99. Service providers

• Supabase — authentication, database, and backend infrastructure;
• Vercel — hosting, deployment, and privacy-friendly analytics;
• Email provider — sending login and transactional emails;
• Google / Apple — only if you choose to sign in with them;
• Expo — delivering push notifications for the mobile app, if you enable them;
• Spotify — only if you choose to connect it, to read your top and followed artists for personal recommendations;
• Google (Gemini API) or Anthropic (Claude API) — only when you import a timetable from a photo or PDF, or ask for a festival web page to be read with AI: the picture, PDF or page text is sent to them to read the timetable from it. They process it on our behalf and do not use it to train their models. Upload timetables only, nothing private.

These providers process data only as needed to provide their services to Setgrid.

1010. International data transfers

Some providers may process data outside your country or region. Where required, we rely on appropriate safeguards, such as the EU Standard Contractual Clauses or other legally recognized transfer mechanisms.

1111. How long we keep your data

• account data is kept while your account exists;
• saved plans are kept while your account exists or until you delete them;
• imported timetable data is kept while needed for the relevant festival or feature;
• technical logs are kept only as long as reasonably necessary for security and operation;
• usage measurement counts are kept for 13 months, then deleted automatically.

When you delete your account, we delete your account and associated personal plans, unless we must keep limited data for legal, security, or abuse-prevention reasons.

1212. Account deletion

You can delete your account at any time from your account page.

Deleting your account permanently removes your sign-in (email and identity), your saved plans (including any group memberships and chat messages attached to them), your avatar, your push tokens, your calendar links and calendar sharing, and your feedback requests. Festivals you published are unlinked from your account but may remain available as shared community content that other users may have planned against. Some data may persist briefly in backups or logs until those systems are automatically overwritten.

1313. Your rights

Depending on where you live, you may have the right to:

• access the personal data we hold about you;
• correct inaccurate data;
• delete your data;
• restrict or object to processing;
• receive a copy of your data;
• withdraw consent where processing is based on consent;
• lodge a complaint with your local data protection authority.

To exercise your rights, contact us at privacy@setgrid.app.

1414. Children

Setgrid is not intended for children under the age required by applicable law to use online services without parental consent, and we do not knowingly collect their personal data.

1515. Security

We use reasonable technical and organizational measures to protect your data, but no online service can guarantee complete security. Please keep access to your email and Google account secure, as they can be used to sign in to Setgrid.

1616. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. If we make material changes, we will update the “Last updated” date and, where appropriate, notify users through the app or website.

1717. Contact

For privacy questions or data requests, contact privacy@setgrid.app.