Privacy Policy

DateRelay is operated by BuyFromUS LLC (United States). Contact: support@daterelay.com. BuyFromUS LLC is the data controller for the personal data described on this page.

DateRelay only receives what the sync you configure actually needs. Nothing else is requested and nothing else is stored.

• From your Google account: your name, email address and profile picture, used to identify your DateRelay account.
• From Google Calendar: the names and ids of the calendars you are subscribed to, so we can show you a list to choose from; and the event data — title, dates and times, and any fields you map, such as description or location — of the one calendar you select for a sync. We do not read events on calendars you have not selected.
• From Notion: the pages of the databases you explicitly share with DateRelay in Notion's own permission picker, and the properties you chose to map. Notion never gives us access to anything you have not shared.
• Your DateRelay settings: which database is paired with which calendar, the properties you mapped, and your plan.

We use it for one purpose: running the sync you configured. We read your Notion database and your selected Google Calendar, compare them, and write the changes across so the two match. We do not use your calendar or Notion content to train models, to profile you, to advertise to you, or for anything else you did not ask for. We do not sell it. Your email address is used to reach you about your account and about failures in your syncs.

DateRelay's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

DateRelay asks for the narrowest Google permissions that let it work: permission to view and edit calendar events, read-only permission to list the calendars you are subscribed to, and your basic profile and email address for sign-in. You can review or revoke DateRelay's access at any time in your Google Account permissions.

DateRelay runs on our own servers. Your Google and Notion access tokens, your sync settings and your sync state are stored in an access-controlled PostgreSQL database on that server, reachable only by the DateRelay service and the people who operate it. The access tokens are encrypted in that database.

Sync state is the record that lets us tell a real change from a duplicate: the Notion page id, the Google event id, and a hash of the content on each side. Event titles are also written to your sync log, which is what the activity list in your dashboard shows you. Event descriptions, locations, attendees and other body content pass through memory during a sync and are not stored.

Security procedures are in place to protect the confidentiality of the data you trust us with. Concretely, these are the measures that apply today.

• In transit. All traffic between you and DateRelay, and between DateRelay and Google and Notion, is encrypted in transit with TLS (HTTPS).
• On the server. The service runs on a private server we operate. The database is reachable only from the DateRelay application on that server and is never exposed to the internet, and access to the server itself requires SSH keys held by the operator only.
• Tokens and logs. Your Google and Notion OAuth tokens are encrypted at rest (AES-256-GCM) in that access-controlled database, with the key kept outside the database, and are never written to our logs — request logs record parameter names only, not their values. We never share your tokens or your calendar data with anyone beyond the sync you configured.
• Backups. Database backups are taken nightly and encrypted before they leave the server. They are kept in a private, access-restricted location and pruned automatically.
• Least access. We request the narrowest Google scopes that allow the sync to work — permission for calendar events and a read-only list of your calendars — and never full calendar access.
• Your control. You can revoke DateRelay's access at any time from Google or from Notion, and deleting your account from Settings removes every token and all sync state immediately.

If we became aware of a breach affecting your data, we would notify affected users by email without undue delay.

We never sell your data and we never share it for advertising. It reaches exactly three other companies, each acting as a processor for a part of the service you asked for: Google (Calendar and sign-in), Notion (your workspace), and Stripe (payments — Stripe handles card details directly and we never see them). We would disclose data otherwise only if the law required it.

Your account, your access tokens and your sync settings are kept for as long as your account exists. Sync state and sync logs are kept while the sync that produced them exists, and are deleted with it. We keep nothing after that: when you delete your account, your tokens, connections, syncs, sync state and sync logs are deleted from our database immediately.

To have your data deleted, open Settings and use "Delete account" in the Danger zone, or email support@daterelay.com and we will do it for you.

Payment records held by Stripe are kept for as long as tax and accounting law requires, independently of your DateRelay account.

Delete your account. Open Settings and use "Delete account" in the Danger zone. That immediately revokes DateRelay's Google and Notion tokens and deletes your account, your connections, your syncs, your sync state and your sync logs from our database. It cannot be undone. Your Notion pages and your calendar events are not touched — only DateRelay's own records are removed.

Disconnect one workspace. Disconnecting a Notion workspace in Settings revokes that workspace's token and deletes the syncs that depended on it.

Revoke from the provider. You can also remove DateRelay's access from your Google Account permissions or from Notion's connections settings. Your syncs stop; email support@daterelay.com if you also want the account itself removed.

You can ask for a copy of the data we hold about you, ask us to correct it, or ask us to delete it. Deletion is self-serve from Settings; for the other two, write to BuyFromUS LLC at support@daterelay.com and we will answer within 30 days. If you are in the EU or the UK these are your rights under the GDPR, and you may also complain to your local data protection authority.

New sign-ins keep their session in an HttpOnly dr_session cookie. Older sessions may also have a bearer token in your browser's local storage for compatibility; new sign-ins do not write one there. During Google sign-in, DateRelay uses a short-lived HttpOnly browser proof cookie to match Google's response to the browser that started it; that cookie expires shortly after the attempt. If you arrive from a link that ends in ?src= (for example from our Notion Marketplace listing), a first-party dr_src cookie keeps that one word for 30 days so we can tell where sign-ups come from; it is stored with your account only if you sign up, and is shared with no one. We use no tracking cookies, no advertising pixels and no third-party analytics.

If we change how we handle your data we will update this page and change the effective date above. For a change that materially affects you, we will email you before it takes effect.