Calendjke Privacy Policy

Last updated: 27 September 2026 · applies to the Calendjke website (calendjke.com) and the Calendjke app (app.calendjke.com)

Calendjke is a web application for scheduling paid meetings. A host signs in with Google, connects Google Calendar and a Stripe account, sets working hours and a price, and shares a booking page. Guests pick a free time and pay to confirm it; Calendjke then adds the meeting to the host's Google Calendar and invites the guest.

This policy explains what information Calendjke collects, how it is used, stored and shared, how long it is kept, and how you can have it deleted. Calendjke is operated by Andrey Posnov (aposnov.dev), who is the data controller. Contact: aposnovdev@gmail.com.

1. Information we collect

Hosts (people who sign in)

• Google account information: your name, email address and Google account ID, received when you sign in with Google.
• Google Calendar free/busy information: the start and end times of busy periods in your calendars. We do not receive event titles, descriptions, locations or attendees through this access.
• Google Calendar events created by Calendjke: the ID of each event Calendjke creates for a confirmed booking, so the same event can be removed if the booking is cancelled.
• Google OAuth tokens: a refresh token that lets Calendjke keep your calendar connection working. It is stored encrypted.
• Settings you enter: username, timezone, weekly availability, blocked dates, public-holiday country, buffer and notice rules, meeting types, durations and prices.
• Stripe connection: the ID of the Stripe account you connect and whether it can accept payments. Your bank and identity details are given directly to Stripe and are not stored by Calendjke.

Guests (people who book a meeting)

• Name, email address, optional note and timezone entered on the booking form.
• The booking time, the meeting type, the amount paid and the Stripe Checkout session ID. Card details are entered on Stripe's page and never reach Calendjke.

Technical data

• A session cookie after sign-in and a short-lived security cookie during sign-in, plus a cj_consent cookie that remembers your analytics choice. No advertising cookies are used.
• Standard server logs (IP address, time, requested URL) kept for security and troubleshooting.

Usage analytics (Microsoft Clarity)

• The website and the app use Microsoft Clarity to see how pages are used (clicks, scrolling, page views, session recordings, heatmaps) together with device and browser type, approximate location and referring page. We use it only to find usability problems and improve Calendjke.
• Text you type and the content of the host dashboard, booking forms and booking confirmations are masked before leaving your browser. Google user data (calendar free/busy times, events, your Google name and email) is never sent to Clarity.
• Clarity sets its cookies (_clck, _clsk) only after you click Accept in the analytics banner. Without consent Clarity runs without cookies and cannot link your visits together.
• You can change your choice at any time by clearing cookies for calendjke.com — the banner will appear again. Declining also asks Clarity to erase its cookies.

2. Google user data — what we access and why

Calendjke requests the following Google permissions and uses each only for the purpose listed:

• userinfo.email, userinfo.profile — to create your Calendjke account, sign you in and show your name and email in the dashboard.
• calendar.freebusy — to read when you are busy so guests are only offered times that are free in your Google Calendar.
• calendar.events — to create one event in your primary calendar for each paid booking (with the guest invited and a Google Meet link attached), and to delete that same event if the booking is cancelled. Calendjke does not read, change or delete any other events.

Google user data is used only to provide these user-facing features. We do not:

• sell Google user data or transfer it to data brokers or information resellers;
• use it for advertising, including personalised, retargeted or interest-based advertising;
• use it to determine credit-worthiness or for lending purposes;
• use it to develop, improve or train generalised or non-personalised AI or machine-learning models;
• allow any person to read it, except with your explicit consent, when needed for security (such as investigating abuse), to comply with law, or when the data has been aggregated and anonymised for internal operations.

Calendjke'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.

3. How we use information

• To show a host's booking page with only genuinely free times.
• To hold a time while a guest pays, and to confirm the booking once Stripe reports the payment.
• To create the Google Calendar event and invitation for a confirmed booking; Google sends the invitation email to the guest.
• To let hosts see and cancel their bookings in the dashboard.
• To keep the service secure, prevent abuse and fix problems.

4. How information is shared

We share information only as needed to run Calendjke:

• Between host and guest: a guest's name, email and note are placed in the host's calendar event; the host's name and the meeting details appear in the guest's invitation.
• Google: to read free/busy times and create or delete booking events via the Google Calendar API.
• Stripe: payments are processed by Stripe on the host's own Stripe account (Stripe Connect). Stripe receives the guest's email, the meeting title and price, and handles card and payout details under Stripe's Privacy Policy.
• Microsoft: masked usage analytics via Microsoft Clarity, handled under the Microsoft Privacy Statement. Microsoft never receives Google user data from Calendjke.
• Infrastructure providers: Hetzner Online (servers in Germany) hosts the app and database; Amazon Web Services (EU region) hosts the website and encrypted database backups.
• Legal: if required by law or to protect the rights and safety of users.

We do not sell personal information and do not share it for advertising.

5. Storage and security

• Data is stored in a PostgreSQL database on servers in the European Union (Hetzner, Germany).
• All traffic uses HTTPS (TLS). Google refresh tokens are encrypted at rest with AES-256-GCM.
• Database access is restricted to the application; daily backups are stored in a private Amazon S3 bucket in the EU.

6. Retention and deletion

• Host account data and bookings are kept while the account exists.
• Unpaid booking holds expire after about 30 minutes and are marked expired.
• Database backups are deleted automatically after 30 days.
• Revoke Google access at any time at myaccount.google.com/permissions; Calendjke stops reading your calendar immediately.
• Disconnect Stripe at any time from your Stripe dashboard.
• Withdraw analytics consent by clearing cookies for calendjke.com and choosing Decline. Clarity keeps recorded data for up to 13 months.
• Delete your account: email aposnovdev@gmail.com from the address you signed in with. We delete your account, settings, tokens and bookings within 30 days (backups roll off within a further 30 days). Guests can request deletion of their booking data the same way.

7. Your rights

You can ask to access, correct, export or delete your personal data, or object to its processing, by emailing aposnovdev@gmail.com. If you are in the EU/EEA or UK you also have the right to complain to your local data-protection authority.

8. Children

Calendjke is not intended for anyone under 16, and we do not knowingly collect their data.

9. Changes to this policy

If this policy changes, the new version will be posted on this page with an updated date. Significant changes will be announced to hosts by email.

10. Contact

Questions or requests: aposnovdev@gmail.com