Last updated: November 14, 2026 SingleCalendar is operated by Debuggex Inc., 222 Finch Ave W #213, Toronto, ON M2R 1M6, Canada. We are responsible for the personal information described in this policy. Contact hello@singlecalendar.com with privacy questions or requests. This policy covers SingleCalendar's website, app, calendar synchronization and related support. It explains what we collect, why we use it, who receives it and how you can exercise your choices. ## 1. Information we collect **Account information.** When you sign in or connect a Google account, we receive its Google account identifier, verified email address and available profile information, such as your name. We store your account and session records, connected accounts and configuration. **Calendar information.** We read the calendar list for connected accounts so you can choose calendars. This includes calendar identifiers, names, colors, time zones, access permissions and reminder defaults, including metadata for calendars you have not selected. For selected calendars, we read and store event information needed for synchronization. Depending on the event and what Google permits, this can include titles, descriptions, locations, dates and times, recurrence rules, reminders, availability, visibility, organizer and attendee information, responses, meeting links, and information about birthdays or other Google event types. Calendar entries may contain information about other people. We also store event snapshots, mappings between originals and copies, synchronization requests and results, changes, deletion records, and failed-edit details. These records let us detect changes, resolve conflicts, retry work and prevent deleted copies from being recreated. **Google authorization.** We store access and refresh tokens that let the service work while you are away. Tokens are encrypted when stored. We do not receive your Google password. SingleCalendar's current Google permissions cover identity, calendar lists and calendar events. They do not grant access to your Gmail messages or Drive files. **Billing information.** We store your balance, calendar charges, deposits, automatic top-up choices, payment status, Stripe identifiers and a saved-card summary such as its brand and last four digits. Card details are entered on Stripe's pages. We do not collect or store full card numbers or card security codes in SingleCalendar. **Support and technical information.** We receive messages and attachments you send us. Our infrastructure and service providers may process IP addresses, browser information, request times and diagnostic information when delivering and securing the service. The signed-in app also uses Pavior as described below. ## 2. How we use information We use this information to: - Sign you in and manage your connected Google accounts. - Show available calendars and apply your selections and settings. - Copy events and Busy blocks, synchronize supported changes, remove generated events and resolve synchronization problems. - Calculate charges, process payments and manage automatic top-up. - Answer support requests, diagnose faults and protect the service against misuse. - Meet legal obligations and resolve billing or other disputes. Where a law requires a legal basis, we rely on providing the service you request, our legitimate interests in operating and securing it, legal obligations, or consent where required. Google authorization allows us to access the accounts you connect. You remain responsible for having authority to connect calendars and copy information about others. ## 3. Google data and calendar sharing SingleCalendar copies information between the Google calendars you select. A full copy on the master can include the source event's details and reminders. Busy blocks contain the time and a title identifying the master calendar, without the source event's description, location or reminders. People who can access a destination calendar may see copied information according to Google's sharing rules. The Hide details setting uses Google's Private visibility. It does not prevent access by everyone, including people with sufficient editing permissions. Review destination sharing settings before synchronizing sensitive calendars. We use Google user data to provide and maintain the calendar features you request. We do not sell it, use it for advertising or credit decisions, or use it to develop or train generalized AI or machine-learning models. Human access is limited to specific data you authorize us to review, necessary security investigations, or legal requirements. Service providers handling Google data for us are subject to the same use restrictions. SingleCalendar follows the Google API Services User Data Policy, including its Limited Use requirements, when using or transferring information received from Google APIs: https://developers.google.com/terms/api-services-user-data-policy ## 4. Pavior feedback and session playback The signed-in SingleCalendar app uses Pavior for feedback and session playback. Playback records activity within the app, including page layout, navigation, clicks, scrolling and other interactions, so we can investigate problems and improve the service. It does not record activity in unrelated apps or on Google's or Stripe's separate pages. We send Pavior your original account email and a signed identity proof to associate feedback and recordings with your account. Before capture, the app masks account and calendar names, event details shown in sync warnings, payment-method identifiers and sensitive admin fields. Non-identifying sync status, controls and billing totals may remain visible. Information you deliberately include in feedback or support messages is sent with that request. Playback is enabled for signed-in users. SingleCalendar does not provide a playback settings switch. Contact hello@singlecalendar.com with a recording-related privacy request. ## 5. Who receives information We do not sell personal information or share it for cross-site targeted advertising. Information is disclosed where needed for the purposes above: - **Google** provides sign-in and Calendar APIs and receives synchronization changes. Destination calendar users may receive copied information through your sharing settings. - **Stripe** processes payments and saved cards. It receives the payment and account information necessary for those services and handles its own payment records under its privacy policy: https://stripe.com/privacy - **Pavior** handles support, feedback and app playback as described above. - **Hosting and infrastructure providers**, including Cloudflare for website delivery and DNS, process information needed to host, deliver and protect the service. - **Authorities or professional advisers** may receive information when required by law or necessary to address a legal or security matter. Google data remains subject to its Limited Use restrictions. Providers acting on our behalf receive only the access needed for their work. A business transfer involving Google user data must also satisfy Google's restrictions, including prior consent where required. ## 6. Storage and security We use HTTPS, encrypted storage for Google tokens, access controls and account-specific authorization to protect information. Our synchronization servers need access to event contents to perform the service. Application error reporting is designed to exclude tokens, credentials and event contents. We operate from Canada. Our hosting and service providers may process information in other countries, where privacy laws and government-access rules may differ. We apply safeguards required by applicable law for international transfers. Contact us for information about the arrangements relevant to your data. No system can guarantee complete security. Protect your Google account and report suspected unauthorized access to hello@singlecalendar.com. ## 7. Retention and deletion We keep account, connection and synchronization information while needed to provide your configured service. Event snapshots and operation history can include past or deleted events. Removing an event or calendar does not immediately erase every stored record: mappings, deletion records and related history help finish cleanup, reconcile interrupted work and prevent unwanted recreation. Removing a calendar from sync schedules deletion of SingleCalendar's associated copies and Busy blocks in Google Calendar while preserving your originals. If access has been revoked, generated events can remain until access is restored or you remove them in Google Calendar. Pausing sync or running out of balance leaves the last copies in place. You can request account closure and deletion of stored personal information at hello@singlecalendar.com. We may verify your identity and clarify the scope first. We will stop the relevant processing and delete information that is no longer needed, subject to legal obligations and applicable rights. Account closure and deletion requests are handled through support, rather than an automatic in-app control. Billing records may need to remain for accounting, tax and dispute obligations. Support, diagnostic and playback records are kept as needed to handle the issue, protect the service or meet legal obligations. Retained information is restricted to those purposes and removed when no longer needed. We do not apply one fixed retention period to every category of data. Deleting data from SingleCalendar does not erase originals or copies held independently by Google, other calendar users or payment providers under their own responsibilities. ## 8. Your choices and rights You can change calendar selections and settings in the app and revoke Google access at https://myaccount.google.com/connections Revoking access stops further authorized Google API access, but does not itself delete stored SingleCalendar data, close the account or remove generated calendar events. You can ask us for access to your personal information, a copy, corrections or deletion. Depending on applicable law, you may also have rights to restrict or object to processing, withdraw consent, or complain to a privacy regulator. We may need to confirm your identity and explain any legal limits on a request. Withdrawing access or requesting deletion may prevent us from continuing synchronization. Send requests to hello@singlecalendar.com. You may also contact the Office of the Privacy Commissioner of Canada at https://www.priv.gc.ca/ or your local privacy authority. ## 9. Cookies and children We use cookies and browser storage for sign-in, security and app state. The Pavior integration may use browser storage for feedback and playback. Blocking storage can affect these features. We do not use advertising cookies in SingleCalendar. SingleCalendar is intended for adults aged 18 and over. If you believe a child has provided personal information through their own account, contact us so we can investigate and address it. An adult's selected calendar may contain information about family members, including birthday events, as part of the calendar service they request. ## 10. Changes and contact We will update the date above when this policy changes. Material changes will be communicated through the service or another appropriate channel, and we will obtain additional consent where the law requires it. Email: hello@singlecalendar.com Debuggex Inc. 222 Finch Ave W #213 Toronto, ON M2R 1M6 Canada