QuickBite Privacy Policy

1. Information We Collect

1.1 Information You Provide

• Account details (organizers): name and email from your sign-in provider (Google, Apple, or a code sent to your email); phone only if you choose text invites; your contact list (names and phone numbers you add), your session history, and your voting preferences. You can also start a vote without an account.
• Participants: the name you enter and your votes. Phone only if you choose to get texts about the session, together with your opt-in/opt-out status and consent records (timestamp, IP address, method). No account is needed to join or vote.
• Where to search: every vote searches from one point, however it was set (typed, carried in a link or an unfinished draft, or suggested by us), and that point can be your device's exact position (when you tap to use your location; it may fill in by itself if you have already allowed this site to use your location). Google turns a typed place into coordinates. Whichever point the vote uses is stored with the vote. Rounded to about a kilometer, it is sent to Google to find restaurants near it; the unrounded point may also be sent to Google to show a place name for it.
• Communications: messages you send to us (e.g., support requests).

1.2 Automatically Collected

• Technical data: IP address, device/browser type, operating system, and interaction logs for security, debugging, and analytics.
• Cookies: essential session cookies (including CSRF protection). Optional analytics cookies as described below.

1.3 Information from Third Parties

• Restaurant data from Google Places when you search or view options.
• An approximate city from GeoJS (geojs.io): when you open the session-creation page we may send your IP address to GeoJS so we can suggest a default city and you do not have to type one. What comes back is a city-level guess, shown on screen labelled as a guess for you to correct. We do not store the guess on its own; if you start a vote from it, its city-level point is stored with that vote like any other search point. It is never precise GPS location.
• SMS delivery metadata from our provider (e.g., delivery status, error codes) to operate the messaging program.

1.4 Information We Do Not Collect

We do not collect payment card data (Stripe collects it directly when you pay), government IDs, biometric data, health data, or financial account data.

2. How We Use Information

We use information to:

• Provide, secure, and maintain the Service;
• Send transactional SMS about sessions you join (invites, reminders, results);
• Record and honor consent, opt-outs, and requests;
• Diagnose and fix bugs, enforce Terms, and prevent abuse;
• Analyze usage in aggregate to improve the Service;
• Comply with legal obligations and carrier requirements.

Where required, we rely on your consent (e.g., to receive SMS), our legitimate interests in operating and improving the Service, and performance of a contract with you.

3. SMS Privacy & Choices

4. Cookies & Analytics

• Essential cookies keep you signed in and protect against CSRF.
• Analytics (optional): We use Amplitude to measure product usage. We do not attach names or phone numbers to analytics, but it records the address of each page you visit, which can include what a link carries (such as a place name). You can limit analytics by enabling browser Do Not Track, using content blockers, or disabling cookies in your browser. We honor Do Not Track by not loading analytics when it is enabled.
• Error reports: We use Sentry to find bugs. Errors the app records, including crashes, are sent to Sentry as error reports, along with performance timings. Since November 7, 2026, before a report or timing is sent, we remove the query string (the part of a web address after the "?") from each web address in it, which is where coordinates and typed places travel, and the code in each QuickBite invite link. Since the same day, Sentry no longer records replays of how the page was used. Reports, timings and replays sent before then can still hold those details for as long as Sentry keeps them.

5. How We Share Information

We do not sell or rent your personal information. We share information only with:

• Twilio (SMS) — phone numbers and message content necessary to deliver SMS; we also receive delivery metadata.
• Google Maps Platform (Places and Geocoding) — the place you typed or your device's exact position, to turn it into coordinates or a place name; and the search point with a radius and your restaurant filters (such as cuisine and dietary choices), to find restaurants near it.
• GeoJS (approximate city) — your IP address, to suggest a default city on the session-creation page. Nothing else is sent, and the result is stored only if you start a vote from it.
• Render (hosting/database) — stores application data and logs.
• Supabase (sign-in) — your email, or the identity your Google or Apple sign-in shares (which can include your name and photo), plus sign-in codes and session records, to run your account.
• Stripe (payments) — when you start a paid plan, your email, your name if we have it, and an account ID that links the payment to your QuickBite account. Stripe's own checkout page collects your card details.
• Sentry (error reports) — error reports and performance timings, with sign-in cookies removed and with query strings and invite codes removed from web addresses, as described in Section 4. After this browser recognizes a test or team account, later reports and timings from it may carry that account's email.
• Amplitude (analytics) — event-level usage data and the addresses of pages you visit; we do not attach names or phone numbers.

If you share an invite or a result through WhatsApp, your phone's share menu or another app, that app receives the shared text and link from your device. We require service providers to use information only to perform services for us and to protect it appropriately. We do not share data with advertisers, data brokers, or social networks for advertising.

6. Data Retention

• Active accounts: We retain account and session data while your account remains active.
• Deleted accounts: When you use Delete my account on your Account page, we delete your sign-in, profile, contacts, saved groups, and the votes you started that nobody else joined right away. Votes other people took part in stay for them, without your name as host. Copies in encrypted backups are purged within an additional 30 days.
• Consent records: Retained for at least 3 years.
• Logs: Server/application logs are retained as needed for security and operations.

7. Data Security

We use technical and organizational measures such as TLS encryption in transit, encryption at rest, access controls, password hashing, input validation, rate limiting, monitoring, and audit logs. No method of transmission or storage is 100% secure.

Incident response. If we discover a breach of security that affects your information, we will take steps to contain it, assess impact, and notify affected users and/or authorities as required. Where applicable, we aim to notify within 72 hours of confirmation of a qualifying incident.

8. Your Rights and Choices

Depending on your location, you may have rights to:

• Access a copy of your information;
• Correct inaccurate information;
• Delete your information;
• Request portability of certain information;
• Object to or restrict processing in certain circumstances;
• Opt out of analytics cookies and SMS as described above.

To delete your account, use Delete my account on your Account page — it takes effect immediately. If you have a paid plan that is still billing, cancel it first; the page sends you to billing to do that. To exercise any other right, or if you cannot sign in, email hello@skylarkcreations.com. We will respond within the timeframe required by law (typically 45 days) and may need to verify your identity.

State Privacy Disclosures (U.S.)

For residents of states with comprehensive privacy laws (e.g., California, Colorado, Connecticut, Utah, Virginia): we disclose the categories of personal information described in Section 1; we use and share them for the purposes described in Sections 2 and 5. We do not "sell" or "share" personal information as defined under state laws. Some state laws treat precise location as sensitive personal information. A vote's search point, which can be your device's exact position, is stored with that vote. Rounded to about a kilometer, it is sent to Google to find restaurants and used to work out the local time for opening hours. Unrounded, it may be sent to Google to show a place name, and it is kept in your history so you can start the same vote again. It is shown to the vote's pages for anyone who has its link, rounded to about a kilometer. The restaurant distances on those pages are measured from that rounded point, and a restaurant list first built after this change on November 6, 2026 is also searched for and ranked from it. Anyone with the link also sees the host's display name, when the host's account has one, on the vote's pages and in the link's preview. We will not discriminate against you for exercising your privacy rights.

Authorized agents may submit requests by emailing us with proof of authorization. We may require you to verify your identity directly.

9. Children's Privacy

QuickBite is not directed to children under 13. We do not knowingly collect personal information from children under 13. If we learn that a child under 13 has provided information, we will delete it. Parents or guardians who believe their child has used the Service may contact us to request deletion.

10. International Users

The Service is operated in the United States and intended primarily for U.S. users. If you access the Service from outside the U.S., you understand and consent to the transfer, storage, and processing of your information in the U.S., where laws may differ from those in your country.

11. Changes to This Policy

We may update this Policy from time to time. For material changes, we will provide at least 30 days' notice via email, SMS, or in-product notice. Your continued use of the Service after the effective date constitutes acceptance of the changes.

12. Contact Us

Appendix: Subprocessors and Links to Their Policies

• Twilio (SMS): https://www.twilio.com/legal/privacy
• Google (Maps Platform: Places, Geocoding):https://policies.google.com/privacy
• GeoJS (approximate city from IP): https://www.geojs.io/
• Render (hosting): https://render.com/privacy
• Supabase (sign-in): https://supabase.com/privacy
• Stripe (payments): https://stripe.com/privacy
• Sentry (error reports): https://sentry.io/privacy/
• Amplitude (analytics): https://amplitude.com/privacy