Privacy Policy — LinkLatch

LinkLatch is a scheduling application that lets hosts share booking links so guests can reserve meeting times. This policy explains what data LinkLatch collects, why it is collected, how it is stored, and how you can remove it.

This policy applies to the LinkLatch web application at linklatch.atlasium788.ca.

1. Data we collect

Google account information

When you sign in with Google, we receive your name, email address, profile picture, and Google account identifier. We use this to create and identify your LinkLatch account and to display your name and photo on your booking page.

Google Calendar data (optional)

Connecting Google Calendar is optional and separate from signing in. If you choose to connect it, LinkLatch writes your confirmed bookings to your calendar:

Events we create. When a guest books a slot, we create a calendar event containing the meeting time, the guest's name and email, and any note the guest provided. If you enable it, we also generate a Google Meet link for the event.
Events we update or remove. If a booking is rescheduled or cancelled, we update or delete the corresponding event we created.

LinkLatch does not read your existing calendar events. Your availability is calculated entirely from the working hours you configure in LinkLatch and the bookings stored in our own database — we never query your Google Calendar to determine when you are busy. This means events created outside LinkLatch will not block slots on your booking page.

If you do not connect a calendar, LinkLatch still works; bookings are simply kept in LinkLatch rather than mirrored to Google.

Booking information

When someone books a meeting through your link, we store the name, email address, selected time, and any message they submit, so both parties have a record of the booking and can receive confirmations.

Technical data

We record basic operational logs — IP address, browser type, and timestamps of requests — to keep the service secure and diagnose faults.

2. Google API scopes and why we request them

LinkLatch uses two separate authorisation steps. Signing in requests only basic identity scopes. Calendar access is requested later, and only if you choose to connect a calendar.

Signing in

Scope	What it lets us do
`openid`	Establish your identity so we can create and recognise your account.
`userinfo.email` / `email`	Identify your account and send booking confirmations to you.
`userinfo.profile` / `profile`	Display your name and profile photo on your booking page.

Connecting a calendar (optional)

Scope	What it lets us do
`calendar.events` (not the full `calendar` scope)	Create, update, and delete booking events LinkLatch writes, and attach a Google Meet link where enabled. We do not request permission to share or delete your calendars, and we do not list or read events you created outside LinkLatch.

We request the narrowest scopes the service needs. We do not request read access to your calendar, and we do not read events that LinkLatch did not create.

3. Limited Use disclosure

LinkLatch's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

In practical terms, this means Google user data obtained through these scopes is used only to provide and improve the scheduling features described above. We do not transfer it to third parties except as needed to provide the service, to comply with applicable law, or as part of a merger or acquisition. We do not use it for advertising, and we do not allow humans to read it except with your explicit consent, for security purposes, to comply with applicable law, or where the data has been aggregated and anonymised. We do not use Google user data to develop, improve, or train generalised artificial intelligence or machine learning models.

4. How we share data

We do not sell your data. We share it only in these circumstances:

With your meeting counterpart. A guest booking a meeting sees the host's name and the confirmed time; the host sees the guest's submitted details.
With service providers. Our hosting and email delivery providers process data strictly on our instructions in order to run the service.
Where legally required. If compelled by valid legal process.

5. Storage, retention, and deletion

Data is stored on servers operated by our hosting provider and protected in transit with TLS. If you connect a calendar, the resulting Google access and refresh tokens are stored encrypted at rest and used only to write the booking events described above. Disconnecting your calendar in LinkLatch deletes those tokens immediately; bookings already in LinkLatch are unaffected and simply stop syncing.

We keep your account data and booking records for as long as your account remains active, so both parties can reference past meetings. We do not currently run an automatic timed purge of booking history while an account is active.

Deleting your data

You can remove your data at any time:

Revoke LinkLatch's Google access at myaccount.google.com/permissions. This immediately stops all calendar access.
Delete your account from Settings → Danger Zone. The account is deactivated immediately (booking links go offline). After a 30-day grace period — during which you can sign in again to cancel deletion — we permanently erase your profile, connected calendar references, stored tokens, and booking history.
Email us at info@atlasium788.ca to request deletion or a copy of your data. We respond within 30 days.

Calendar events that LinkLatch created remain in your Google Calendar after deletion; you control those directly in Google Calendar.

6. Your rights

Depending on where you live, you may have the right to access, correct, export, or delete your personal information, and to withdraw consent for processing. Contact us at the address below to exercise any of these rights.

7. Children

LinkLatch is not directed at children under 13, and we do not knowingly collect their personal information. If you believe a child has provided us data, contact us and we will delete it.

8. Changes to this policy

If we change how we handle your data, we will update this page and revise the date above. Material changes affecting Google user data will be communicated by email before taking effect.

9. Contact

Questions about this policy or your data: info@atlasium788.ca