FOCL ("we", "our", or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard your information when you use FOCL — the wedding-day planning app, and FOCL Galleries, where photographers deliver photographs to their clients.
When a couple or a wedding guest opens a gallery shared with them, we may collect:
Photographers can switch on selfie search for a gallery. Where it is on, we use Amazon Rekognition to create a mathematical representation of each face appearing in that gallery's photographs — a "face template". A face template is a biometric identifier. It is not a photograph and cannot be turned back into one.
We do not use face data to identify anyone outside the gallery it came from, do not build a profile across galleries or weddings, and do not sell, licence or disclose it to anyone other than Amazon Web Services, the processor that performs the matching.
Connecting Google Calendar in FOCL Studio is optional and requires a separate authorization from signing in with Google. When you connect, FOCL accesses your Google account identifier and email address, your calendar list and permissions, and busy periods from the calendars you select.
We use this information to offer available call times and create, update, or cancel FOCL appointments on your chosen owned calendar, including Google Meet links and calendar invitations. When checking that calendar during booking or rescheduling, we request event identifiers, times, availability status, and your attendance status to exclude the appointment being moved. We do not request unrelated event titles or descriptions for these checks. Your unrelated events are not displayed to clients.
We store your connection identity, selected calendar identifiers, scheduling settings, encrypted authorization credentials, and FOCL appointment records. Appointment records include participant names and email addresses, answers provided when booking, times, timezones, event identifiers, and meeting links. Busy-time results and unrelated event details are not retained as a calendar history.
Scheduling information is shared with the photographer and appointment participants as needed to arrange the call. Google processes calendar events, invitations, and Meet conferences. Supabase provides hosting and storage, and Resend delivers verification, confirmation, and reminder emails containing the relevant appointment details. We do not access Gmail messages or record calls through this integration.
FOCL's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Google-derived data is used for the scheduling features described here, not for advertising, sale to data brokers, lending decisions, or training generalized AI models. Human access is limited to your affirmative permission for specific support needs, necessary security investigations, or legal obligations. These limits also apply to our service providers and override broader uses described elsewhere in this policy.
You can disconnect in Studio's Scheduling calendar settings or revoke access through your Google Account connections. Disconnecting through FOCL revokes the connection, deletes its stored refresh credential, and pauses new bookings. Existing Google events and FOCL appointment history remain; disconnecting does not cancel appointments. If you revoke access in Google, FOCL stops calendar operations when the revoked authorization is detected. Use FOCL's disconnect control to remove the stored connection as well.
Appointment records remain while your FOCL account is active, subject to the retention policy below. You may request deletion of Google-derived scheduling data at privacy@getfocl.app or request account deletion in Settings. Deleting FOCL data does not delete copies already delivered to participants or events retained in their Google accounts.
| Purpose | Legal Basis |
|---|---|
| Provide and maintain the Service | Contract performance |
| Send account-related emails | Contract performance |
| Improve and optimize the Service | Legitimate interest |
| Respond to support requests | Contract performance |
| Detect and prevent fraud | Legitimate interest |
Your data is stored securely using Supabase, a trusted cloud infrastructure provider. We implement the following security measures:
We do not sell your personal data. We only share data in the following circumstances:
| Provider | What they handle |
|---|---|
| Supabase | Database, accounts and application hosting |
| Cloudflare | Photograph and video storage, delivery and streaming |
| Amazon Web Services | Face matching for photo search (Rekognition), where a photographer has switched it on |
| Stripe | Subscription and print-order payments, and photographer payouts. Card details go to Stripe directly. |
| WHCC | Printing and shipping. Receives the photographs ordered and the shipping address. |
| Resend | Email delivery |
| Sentry | Error reporting, with gallery links and personal details removed before sending |
| Google (Gemini) | Reading uploaded documents into shot lists and timelines, in the planning app |
You have the right to:
We retain your data for as long as your account is active. When you delete your account:
Some things follow their own schedule:
Most people who appear in a FOCL gallery never signed up for FOCL. You were photographed at a wedding, and the photographer delivered those photographs through us. This section is for you.
The photographer decides what is in their gallery and who can see it. We host it on their behalf. That makes them the controller of those photographs and us the processor, so the quickest route to having a photograph taken down is to ask the photographer directly.
You can also come to us at privacy@getfocl.app to:
We will act on a face-data request without asking you to prove a subscription or an account, because you will not have one. Where we need the photographer's involvement — deleting a photograph they own, for instance — we will tell you so rather than leave the request unanswered.
Face templates are biometric identifiers under the Illinois Biometric Information Privacy Act, the Texas Capture or Use of Biometric Identifier Act and Washington's biometric privacy law. Where those laws apply:
FOCL uses minimal cookies and local storage:
We do not use third-party tracking cookies or advertising cookies.
FOCL is not intended for users under 18 years of age. We do not knowingly collect information from children. If you believe a child has provided us with personal data, please contact us.
Your data may be processed in countries other than your own. We ensure appropriate safeguards are in place for international transfers, including standard contractual clauses where required.
We may update this Privacy Policy from time to time. We will notify you of significant changes via email or through the app. The "Last updated" date at the top indicates when the policy was last revised.
If you have questions about this Privacy Policy or your data, please contact us:
California residents have additional rights under the CCPA, including the right to know what personal information is collected, request deletion, and opt-out of the sale of personal information. We do not sell personal information.
If you are in the EU or UK, you have additional rights under GDPR including the right to lodge a complaint with a supervisory authority. Our legal basis for processing is contract performance and legitimate interest as described above.