1. Public website
This public information site does not provide access to Relay’s working application. It does not collect form submissions, create user accounts, or use advertising trackers. Standard hosting infrastructure may process basic request data such as an IP address, browser type, requested page, and request time for security and reliable delivery.
2. Google data Relay accesses
With explicit consent, Relay requests read-only Google Calendar access. It may read calendar and event information including:
- calendar identifiers and names;
- event titles, dates, start and end times, and recurrence details;
- locations, descriptions, conference links, and event status;
- organizer and attendee names, email addresses, and response status; and
- synchronization cursors needed to identify later Calendar changes.
Relay does not request permission to create, modify, or delete Google Calendar events. It does not request Gmail access through this integration.
3. How Google data is used
Relay uses Calendar information only to:
- synchronize upcoming and historical meetings;
- associate meetings with private relationship context;
- prepare concise, just-in-time meeting briefings; and
- operate, secure, troubleshoot, and improve those owner-requested functions.
Relay does not sell Google user data, use it for advertising, use it to determine creditworthiness, or allow humans to read it except when necessary to provide or secure the application, comply with law, or act with the user’s affirmative permission.
Relay’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
4. Storage, security, and sharing
Synchronized Calendar records are stored in a database connected to Relay’s protected Vercel application. Provider authorization is managed through Vercel Connect. Access to the working application is restricted, and Relay avoids placing provider credentials in client-side code or public pages.
Data may be processed by infrastructure providers solely to host the application, manage the authorized connection, store synchronized records, and maintain service security. Relay does not sell or rent Google user data and does not share it with advertisers or data brokers.
5. Retention and deletion
Calendar records are retained only while they are needed to operate Relay and its relationship-history features, or as required for security and legal obligations. Revoking Google access prevents future synchronization but may not by itself delete records already synchronized into Relay.
To request deletion of synchronized Google Calendar data, email mbeck04@gmail.com. A verified deletion request will be completed within 30 days unless retention is legally required. Backup copies may persist temporarily until normal backup rotation completes.
6. Your controls
Google Calendar access can be reviewed or revoked at any time from the Google Account connections page. You may also contact Relay to ask what Calendar information is stored, request a correction, or request deletion.
7. Policy changes
This policy may be updated when Relay’s data practices or applicable requirements change. Material changes will be reflected on this page with a revised effective date before the changed practice takes effect where reasonably possible.
8. Contact
Questions, access requests, and deletion requests can be sent to mbeck04@gmail.com.