Privacy Policy
Google user data
Google sign-in and Google Calendar authorization are separate choices with separate clients, permissions, and purposes.
Sign in with Google
ReachLynk receives your Google account identifier, email address, and basic profile information when you choose Google sign-in.
We use this identity data only to create or authenticate your ReachLynk account and maintain your application session.
Google sign-in does not authorize ReachLynk to access Google Calendar and its identity token is not used for Calendar API operations.
Google Calendar connection
Only after you separately choose to connect Google Calendar, ReachLynk requests permission to view free/busy availability and to view, create, update, and delete events needed for scheduling and meeting management.
ReachLynk uses Calendar data to avoid booking conflicts, create and manage meetings requested through the product, and show the resulting booking state to authorized workspace users.
ReachLynk stores the Google account identifier and email, the granted scope set, encrypted OAuth credentials, connection settings, and identifiers or booking details needed to operate and reconcile the scheduling features. Free/busy results are queried for scheduling and are not used to build advertising profiles.
ReachLynk does not sell Google user data, use it for advertising, or allow people to access it except as needed to provide the requested features. Current processors for this integration include Supabase for authentication and database infrastructure and Vercel for application hosting. ReachLynk also exchanges the user-directed event operations with Google Calendar. Other disclosure is limited to legal requirements or protecting rights and safety.
Connection credentials and related Google account metadata are retained while the Calendar connection is active. Disconnecting deletes the active Calendar connection and its stored OAuth credentials. Booking records created through ReachLynk may remain under the account and legal-retention terms described in the full Privacy Policy.
You can disconnect a Calendar in Settings to remove ReachLynk's active connection data. You can also revoke ReachLynk in your Google Account permissions; revocation stops future access but does not itself delete records already retained under the Privacy Policy.
ReachLynk's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Questions or deletion requests can be sent through the ReachLynk support contact identified in the Privacy Policy. Review the Terms of Service.