Privacy policy
Faro exists to hold you to your own calendar. To do that it needs to read your calendar and remember what you answer. This page says exactly what it collects, where it is kept, who else sees it, and how to make it go away.
Who runs Faro
Faro is built and operated by its developer in Toronto, Ontario, Canada. For anything in this policy, write to bestcanadianrealtors@gmail.com.
What Faro collects
| Data | Why |
|---|---|
| Your Google account name and email | To sign you in and to know whose data is whose. |
| Google Calendar events: title, start and end time, location, description, colour, and whether they repeat | To schedule reminders, ask whether you finished, and work out when you need to leave. Read-only: Faro never creates, changes, or deletes an event. |
| Your plan settings, including your home and office addresses if you enter them | Your Day 1, alarms, and the starting point for drive-time checks. |
| Goals, and the name and phone number of an accountability person if you enter one | Streaks per goal, and the one-tap text or call when you hit a milestone or reset. |
| Your answers to "Did you finish?", streak counts, and bedtime and wake-up taps | The streak engine. |
| Thoughts you capture in the inbox | The daily Clarify ritual. |
| Transactions from bank statement files you choose to upload: date, description, amount | The Money Mirror. Statements are read on your device and only the transactions are stored. Faro never connects to your bank. |
| A push notification token for your phone | So reminders reach you when the app is closed. |
| Drive-time checks: origin, destination, and minutes | To tell you when to leave. |
Faro has no advertising, no analytics trackers, and does not collect your location from the phone. Where you are comes only from the addresses on your calendar and the ones you type in.
Where it is stored
Your data is stored in your own account with Supabase, which hosts Faro's database and server functions and encrypts data at rest. Each person's data is walled off from every other person's by database access rules. The long-lived key that lets Faro read your calendar while the app is closed is kept on the server in a store the app itself cannot read.
Who else sees it
Faro shares data only with the services it needs to work, and only the piece each one needs:
- Google Calendar — Faro reads your events with the read-only permission you grant when you sign in.
- Google Maps (Routes) — the origin and destination addresses of a trip, to get a live drive time.
- Expo and Apple push services — your push token and the text of each reminder, to deliver it to your phone.
- Waze — a destination address, only when you tap "Open in Waze".
Faro does not sell your data, share it with advertisers, or use it to train anything.
Google user data
Faro's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Calendar data is used only to provide the reminders, confirmations, and travel checks you see in the app. It is never used for advertising, never sold, and never read by a person except with your permission to fix a problem you report.
Your choices
- Stop calendar access at any time from your Google account permissions. Faro's reminders stop with it.
- Turn off reminders from your phone's notification settings, or use Silent mode in Faro's settings.
- Remove a statement and every transaction from it, from the Money tab.
- Delete your account and all of its data by emailing bestcanadianrealtors@gmail.com from the address you signed in with. Everything is deleted within 30 days, including the stored calendar key.
How long it is kept
For as long as you have an account. Reminders that have already been sent are cleared from the server after 14 days. Everything else is deleted when your account is.
Children
Faro is not directed at children under 13 and does not knowingly collect their data.
Changes
If this policy changes in a way that matters, the date at the top changes and the change is described here.