Privacy Policy

• Name, email address, and password (or your Google/Apple account identifier if you sign in with those providers).
• Profile details you choose to add: avatar, school/graduation year, and similar preferences.
• Group and plan activity: the plans, groups, and squads you create or join.

If you enable live radar, safe zones, or ride/carpool coordination, we collect your device's real-time or approximate location so it can be shown to the people you've explicitly shared it with (your squad for a specific plan, or your linked guardian). Location is collected only while these features are turned on, and only from the device you've signed in on.

• Contact details you provide to invite someone to a group, plan, or as a guardian link (e.g. an email, phone number, or invite code).
• The relationship itself — who invited whom, and whether an invite was accepted.

When a teen and a guardian link their accounts, we collect and store the link itself (which accounts are connected and in what role), plus the data that link is designed to share — see Minors, teens & guardians below for exactly what that includes.

Direct messages, plan chat, comments, private answers you submit to a plan (like budget or scheduling constraints), and any photos or files you upload (e.g. an avatar).

• Log data such as IP address, device/browser type, and timestamps of activity.
• Push notification tokens, if you enable notifications.
• Basic diagnostic and analytics data used to keep the Service reliable.

When you join a plan, other members of that plan can see the profile info you've shared, your live location if radar is on for that plan, and your ride details. Your private constraints (like an exact budget) are never shown to the group — only whether a proposed option is compatible with them.

If a teen's account is linked to a guardian, that guardian can see the data described in Minors, teens & guardians — this is a core, intentional part of the parent-safety features and is not "sharing with a third party" in the ordinary sense, since the guardian is acting as an account holder on the linked family unit.

We use a small number of vendors to run the Service, who process data on our behalf under their own confidentiality and security obligations:

• Supabase — database, authentication, and file storage.
• Mapbox — map rendering and location display.
• Geoapify — venue and place search results when you browse spots for a plan.
• Open-Meteo — weather forecasts for a plan's date and location (no account or API key; only coordinates are sent, never who they belong to).
• Google's Gemini API (or a fallback AI gateway) — generates plan summaries and suggested compromises from aggregate, non-identifying figures (like a group's tightest budget cap or an overall match score) — never an individual member's raw private answer.
• Google and Apple — if you choose to sign in with those providers.
• Push notification delivery providers (e.g. your browser or OS push service), if you enable notifications.

We may disclose information if required by law, subpoena, or other legal process, or if we believe in good faith it's necessary to protect the safety of a user or the public, investigate fraud, or enforce our Terms.

If Syncly is involved in a merger, acquisition, or asset sale, your information may be transferred as part of that transaction. We'll notify you before your data becomes subject to a different privacy policy.

You must be at least [minimum age — confirm the age you want to support, e.g. 13] years old to create your own account. If you are under 18, we encourage — and some features may require — a parent or legal guardian to link their account to yours. Syncly is not directed at children under [13], and we do not knowingly collect personal information from children under that age without guardian involvement through the linking flow described here.

Once a teen accepts a guardian link (or a guardian sends and the teen accepts an invite), the guardian's family hub can see:

• The teen's live location and location history while radar is active, and any safe zones configured for them.
• Plan details the teen is part of: who's going, cost, destination, and ride/return-time information.
• Check-in requests and responses.
• Plan approval requests, and the ability to approve, decline, or approve-with-conditions.
• Alerts related to safe-zone entry/exit or missed check-ins.

A guardian link does not give a guardian access to the teen's private messages, DMs, or the private constraints (like an individual friend's budget) that other group members have submitted to a plan.

Linking requires action from both sides — typically an invite code generated by one party and entered by the other — so neither a teen nor a guardian is linked without their participation. Either party can unlink the accounts unilaterally from their settings, at any time, without the other party's confirmation. Unlinking stops future data sharing between them going forward, but does not retroactively delete location, plan, or check-in data that was already shared with the other party while the link was active.

Laws governing children's and teens' data (such as COPPA in the U.S. and similar regimes elsewhere) vary by age and jurisdiction. [This section describes the product's intended data-sharing design, not a legal conclusion. Have counsel confirm the minimum age you support, whether COPPA or a state student-privacy law applies to your user base, and whether you need verifiable parental consent before a guardian link is treated as sufficient.]