Effective Date: 11 May 2026 |
Last Updated: 11 May 2026
Important: FamSynch is a family logistics and intelligence application. It is NOT a medical record system, legal advice service, child-welfare authority, or licensed counselling service. Any health, medical, custody, or safety information you record in FamSynch is for your family's own coordination purposes only. FamSynch does not verify, endorse, or take responsibility for the accuracy of family-supplied information. For medical, legal, or child-safety concerns, consult a qualified professional or contact the relevant authority directly.
1. Who We Are
FamSynch ("we", "us", "our") is a mobile application based in Australia.
When we refer to "FamSynch", "the Services", or "the App", we mean the FamSynch mobile application available on Apple App Store and Google Play.
2. Our Commitment
We take your privacy seriously. We collect only the data you give us, and only what we need to provide the Services. We do not connect to your email, iMessages, or any account you have not explicitly opted in to. We do not sell your data to any third party. We store your data securely using industry-standard practices. You have the right to access, export, and delete your data at any time.
This Privacy Policy explains what information we collect, how we use it, what we share with whom, and the rights you have regarding your data.
3. Information We Collect
3.1 Information you provide directly
Account information — email address, first and last name (used for account creation, authentication, and personalization).
Family member profiles — for each member of your family that you add: name, alias, role (parent, child, teen, grandparent, etc.), age bracket or school year, school, workplace, mode of transport, and other details you choose to record. Optional fields include allergies, medical notes, dietary restrictions, custody schedule, and emergency contacts.
Home, school, and workplace addresses — used for travel-time calculations and location-aware reminders.
Screenshots — images you upload for AI extraction (e.g., school newsletters, work rosters, SMS confirmations, ticket emails). See §3.3 for retention.
Calendar events — events created manually, extracted from screenshots, or synced from connected services.
Family memory notes — unstructured notes you record (e.g., "Riya needs goggles Tuesday").
Chat messages — conversations with the FamSynch AI assistant.
Cultural and regional preferences — festivals, school terms, public holidays you choose to track.
3.2 Information from connected services (opt-in only)
If you choose to connect a third-party service to your FamSynch account, we receive only the data needed for the integration:
Google Calendar — when a family member opts in individually, we read their calendar events using the https://www.googleapis.com/auth/calendar.readonly scope. We never write to Google Calendar. The sync window is limited to events from -7 days to +90 days. See §10 for full details.
You can disconnect any integration at any time, after which we revoke our access tokens with the provider and delete the synced data from our systems.
3.3 Information collected automatically
Device information — device type, model, operating system version, app version, language, time zone.
Usage data — screens viewed, features used, app interaction events (for improving the app).
Crash reports — diagnostic information when the app encounters errors (no personal content).
Approximate location — country-level detection based on IP address (used for showing regional content). We do NOT collect precise GPS location.
3.4 What we do NOT collect
We do not read your email, iMessages, SMS, or any messaging app.
We do not access your device contacts.
We do not access your photo library beyond images you explicitly select to upload.
We do not collect precise GPS location.
We do not connect to your bank, payment, or financial accounts.
4. How We Use Your Information
We use your information for the following purposes:
Provide the Services — create your family, extract events from screenshots, generate reminders, run conflict detection, power the chat assistant.
Improve the app — understand how users interact with features, identify bugs, plan updates.
Communicate with you — send account verification, password reset, service updates, and respond to support requests.
Storing your account, family data, events, encrypted refresh tokens. Hosted on AWS.
Account data, family member data, events, screenshots (transient), refresh tokens (encrypted via Supabase Vault).
Google Calendar API
Read-only sync of a member's calendar events when they opt in individually.
OAuth refresh + access tokens (server-side only); event data flows from Google to our server.
Google AI (Gemini)
AI vision extraction from screenshots; primary AI provider for chat.
Screenshot image content and your text queries. Google's API terms prohibit using API inputs to train models.
OpenAI
Fallback AI provider for vision and chat; content moderation.
Screenshot content (when fallback is used) and text queries.
Anthropic (Claude)
Fallback AI provider for chat.
Text queries only when fallback is used.
Mistral
Fallback AI provider for vision.
Screenshot content only when fallback is used.
OpenWeather
Weather context for reminders ("rain expected — pack a jacket").
Approximate location coordinates derived from your saved addresses.
Google Distance Matrix
Travel-time intelligence between events.
Saved address coordinates (origin and destination) only.
Google Places
Address autocomplete during onboarding.
The text you type when adding an address.
Apple App Store
App distribution.
Managed under Apple's Privacy Policy.
Google Play
App distribution.
Managed under Google's Privacy Policy.
Sentry (crash reporting, if used)
Diagnostic information when the app crashes.
Device info, stack trace (no personal content).
Each service has its own privacy policy. We recommend reviewing them for further information.
6. Data Retention
We retain your personal data only as long as needed to provide the Services:
Account data (email, name, preferences) — retained while your account is active.
Family member profiles, events, memory notes, addresses — retained while your account is active; deleted on account deletion.
Screenshots — uploaded screenshot files are deleted from storage within 7 days of successful processing. Failed uploads are deleted within 3 days. Stuck uploads are deleted within 24 hours. The extracted event data remains until you delete it.
Synced calendar events from Google — retained while the integration is connected; deleted in full when the user disconnects Google Calendar.
Google OAuth refresh tokens — encrypted at rest using Supabase Vault. Deleted immediately on disconnect or account deletion. We also explicitly revoke the token at Google.
Chat history — retained for up to 2 years for service quality and chat-context continuity.
Audit log — security-relevant events (logins, OAuth grants, disconnects) retained for up to 2 years for security investigation.
Anonymized and aggregated usage data (no personal identifiers) may be retained longer for analytics and service improvement.
7. Your Rights
7.1 Under Australian Privacy Act, Indian DPDP Act, GDPR, and CCPA
You have the following rights regarding your personal data:
Right of access — request a copy of all personal data we hold about you.
Right of rectification — update or correct your personal data.
Right of erasure (right to be forgotten) — delete your account and all associated personal data.
Right of data portability — receive your data in machine-readable format.
Right to object — object to certain processing of your data.
Right to withdraw consent — withdraw consent for data processing at any time, including disconnecting Google Calendar.
7.2 How to exercise your rights
Delete your account: Settings → Privacy → Delete Account. Account and personal data are permanently removed from our active systems within 30 days.
Export your data: Settings → Privacy → Export My Data. Your data is provided in machine-readable format (JSON) within 14 days.
Disconnect Google Calendar: Settings → Integrations → Google Calendar → Disconnect. Tokens are revoked at Google and synced events are deleted from our systems immediately.
Access / correct data: Most data is editable directly in the app (member profiles, events, addresses). For specific requests, email support@famsynch.com.
Other requests: Email support@famsynch.com with your request. We will respond within 14 days.
7.3 If you are in the European Union (GDPR)
In addition to the above rights:
You have the right to lodge a complaint with a supervisory authority.
The legal basis for our processing is: (a) performance of a contract (to provide you the Services you have signed up for), (b) legitimate interest (to improve and secure the Services), and (c) your consent (where applicable, including for Google Calendar sync).
If you do not provide required data, we may not be able to provide the Services.
7.4 If you are in California, USA (CCPA + CPRA)
You have additional rights:
Right to know what personal information is collected, used, shared, or sold.
Right to opt out of sale of personal information — we do not sell your personal information.
Right to non-discrimination for exercising your rights.
Right to correct inaccurate personal information.
To submit a CCPA request, email support@famsynch.com with subject line "CCPA Request".
7.5 If you are in India (DPDP Act 2023)
You have the rights of access, correction, erasure, and grievance redressal. Our grievance officer contact:
We implement industry-standard security practices to protect your personal data, including:
Encryption in transit — all client–server communication uses HTTPS/TLS.
Encryption at rest — Supabase default encryption for the database; Supabase Vault encryption for Google OAuth refresh tokens specifically.
Server-side API key custody — third-party API credentials (AI providers, weather, maps) live only in Supabase Edge Functions, never on the client device.
Row-level security (RLS) — every table is partitioned by user / family identity, with database-level policies preventing cross-family or cross-user reads.
OAuth state CSRF protection — Google Calendar OAuth uses signed, single-use state tokens to prevent linking attacks.
Audit logging — security-relevant events (logins, OAuth grants, disconnects, RLS denials) are logged for investigation.
Regular security reviews — internal review of access controls and dependencies.
However, no method of electronic storage or transmission is 100% secure. In the event of a data breach that affects your personal data, we will notify you and the relevant authorities as required by law.
9. Data Transfers
FamSynch is operated from Australia. Some of our third-party service providers are based in the United States, European Union, or other countries. When your data is transferred outside your country of residence:
For European users: we rely on Standard Contractual Clauses or equivalent safeguards.
For Indian users: transfers are made under the Digital Personal Data Protection Act 2023.
For Australian users: transfers comply with the Privacy Act 1988.
10. Google Calendar Integration
FamSynch offers optional, per-member, read-only Google Calendar sync. This section explains what we do and don't do with your Google Calendar data.
10.1 Scope requested
When a family member connects their Google account, FamSynch requests only the following Google API scope:
https://www.googleapis.com/auth/calendar.readonly — read access to calendars and events. Read-only, no write capability.
FamSynch does not request scopes for Gmail, Drive, Contacts, Photos, Tasks, or any other Google service.
10.2 What we read
The list of calendars on the connected Google account.
For calendars the user has chosen to sync: events from -7 days to +90 days only — not historical events.
For each event: title, description, start/end time, location, attendee status (busy/free), and Google's visibility flag.
10.3 What we never do
We never write to Google Calendar.
We never share Google Calendar event content with third parties — including AI providers, advertising, or analytics.
We never read calendars the user has not explicitly chosen to sync.
We never read events outside the -7d to +90d window.
We never sync between family members' Google accounts — each member's connection is independent.
10.4 Visibility model
By default, synced events are visible to your family inside FamSynch (matching FamSynch's whole-family value proposition). However:
Events marked visibility=private in Google Calendar are filtered out at sync time and never shown to other family members.
Events marked visibility=busy are shown to other family members as a busy block with title, description, and location masked.
You can override visibility on any individual event inside FamSynch — even after sync — to hide or mask it from other family members.
10.5 Token storage
Google OAuth refresh tokens are stored only on the server, never on the client device.
Refresh tokens are encrypted at rest using Supabase Vault.
Access tokens are short-lived (1 hour) and held in memory by the server during sync; never persisted to the database.
10.6 Disconnect
You can disconnect Google Calendar at any time via Settings → Integrations → Google Calendar → Disconnect. On disconnect:
The refresh token is revoked at Google.
The encrypted token is deleted from our database.
All previously-synced events are deleted from our database.
Derivative data (reminders, conflict alerts) referencing those events is cascade-deleted.
An audit-log entry of the disconnect is retained for security purposes.
Account deletion performs the same disconnect flow for any active integrations.
10.7 Compliance with Google API Services User Data Policy
FamSynch's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use the data only to provide the user-facing features described above; we do not transfer the data to third parties for advertising; we do not allow humans to read the data unless required for security, compliance, or with the user's explicit consent for support; and we do not use the data to develop, improve, or train generalised AI models.
11. Family Members and Children
11.1 Family member roles
FamSynch supports the following member roles:
Parent / Guardian — full create/edit/delete access on family data.
Teen (16–17) — optional individual login; can manage their own events; can view family calendar based on visibility settings.
Child (under 16) — managed by parents. No individual login. The child does not have an account; they appear in FamSynch as a profile maintained by the parent.
11.2 Children's data
Information about children under 16 in your family is provided to FamSynch by the parent or guardian who created the family. We rely on the parent's authority to record this information for family-coordination purposes.
FamSynch does not create accounts for children under 16.
FamSynch does not directly collect data from children under 13 — any such data appears only because a parent has recorded it in their own account.
Parents can edit, export, or delete child profile data at any time.
If you are a child under 13 using a parent's account, please ask the parent to manage your data on your behalf.
If you believe a child's data has been recorded in FamSynch without parental authority, please contact support@famsynch.com and we will investigate.
11.3 Cross-member privacy
Within a family, FamSynch enforces a per-event visibility model: events can be marked private (only visible to the owner), busy (other members see "busy" without details), or shared (full visibility). This applies to manually-created events, screenshot-extracted events, and Google-synced events alike.
12. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect changes in our practices, technology, or legal requirements. The latest version is always available at famsynch.com/privacy and via the in-app Settings → Legal section. We will notify registered users of material changes via email or in-app notification at least 30 days before the changes take effect.
Continued use of the Services after the effective date of updates constitutes acceptance of the revised Privacy Policy.
13. Legal Compliance
This Privacy Policy is designed to comply with:
Australia — Privacy Act 1988 (Cth) and Australian Privacy Principles.
India — Information Technology Act 2000, IT Rules 2011, and Digital Personal Data Protection Act 2023.
European Union — General Data Protection Regulation (GDPR).
United States — California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA).
Other jurisdictions — applicable local privacy laws.
14. Contact Us
For questions about this Privacy Policy or our data practices: