Last updated: October 15, 2026
Degree to License is an independent educational resource for Florida therapists. This policy explains how the website and the Calendar Sync application collect, use, store, and share information, including Google account and calendar data, and the choices available to you.
Information we collect
If you join the updates list, you provide your email address through the embedded signup form. The site and its service providers may also receive routine technical information needed to operate, secure, and measure the site, such as your IP address, browser and device information, referring page, and basic interaction data.
Email updates and Brevo
The updates form is hosted and processed by Brevo (formerly Sendinblue). Brevo processes the email address and related subscription records you submit so Degree to License can manage the mailing list, send confirmation messages, and deliver occasional new guides and practice-tool updates. The list uses confirmation before subscription. Every marketing email includes an unsubscribe option.
Brevo handles this information under its own privacy policy. Degree to License does not sell your email address or use it for unrelated advertising.
Spam protection and Cloudflare Turnstile
The signup form uses Cloudflare Turnstile to help distinguish legitimate submissions from automated abuse. When Turnstile loads or checks a submission, Cloudflare may process technical and interaction data, including your IP address, browser and device characteristics, and signals related to the challenge, to provide security and fraud-prevention services. Turnstile is governed by Cloudflare’s privacy policy and terms.
How information is used and shared
Information is used to operate and protect the site, confirm and manage subscriptions, send the updates you requested, understand basic site performance, and respond when you contact Degree to License. Information is shared only with service providers that support those purposes, when required by law, or when necessary to protect the site and its visitors.
Purchases and product delivery
Stripe processes payments for paid Degree to License resources. Degree to License receives the buyer’s email address, order identifier, product and payment amounts so it can verify a purchase, deliver access and help with an order. Card details are entered through Stripe and are not stored by the Degree to License delivery plugins.
Managed Payments orders are marked Sold through Link at checkout. Stripe handles payment-related support for those orders. Degree to License provides access to the resource and helps with its use.
The WordPress delivery system stores purchase records and private access information. Buyer email addresses and access tokens are encrypted in that system. Purchase records are used for delivery, access control and support. Buying a resource does not add the buyer to the marketing list.
Product emails and private links
Brevo sends the site’s transactional emails, including purchase delivery messages. Brevo processes the recipient’s email address and the message content. Its current tracking settings can record email opens and link clicks. When you open a tracked delivery button, the private access link passes through Brevo. Keep purchase emails and access links private.
Notes in browser tools
The paid browser kits and planners save your entries in the browser you use. The tools do not send those entries to Degree to License or sync them between devices. Export a backup to move your work or keep a separate copy. Backup and readable files contain the entries you export, so keep those files private.
The tools use a secure cookie to maintain access after you open your purchase email. Clearing site data can remove access cookies and saved entries. You can reopen the purchase email to regain access while it remains available, but you need your backup to restore notes that were removed. Keep client information and private clinical records out of these tools.
Keeping purchase records
Purchase records are kept to provide access, resolve order questions and meet applicable recordkeeping requirements. There is no automatic deletion period configured in the delivery system. Requests to remove purchase information are reviewed, including whether a record still needs to be retained.
Copies of purchase records may remain in website backups until those backups are replaced or deleted. The Calendar Sync backup periods elsewhere in this policy apply to that separate application, not to WordPress purchase records.
Questions about purchase records
Use the Contact page to ask about your purchase information or request a correction or deletion. Include the email address used for the purchase. Do not send your saved planner, client information or card details.
Calendar Sync and Google account data
Calendar Sync is an invitation-only early-access service. When you connect a Google account, the service uses your Google account identifier and email address to create and identify your Calendar Sync account. It lists the identifiers and names of calendars available to your account so you can select between 1 and 20 source calendars.
For selected source calendars, Calendar Sync accesses event titles, start and end times, status, availability settings, and application markers within a rolling window of seven days in the past through 60 days in the future. Titles are read so the service can apply any exact-title exclusions you configure. Matching ignores capitalization and surrounding spaces. No titles are excluded unless you add them.
Event titles may contain sensitive information even though Calendar Sync does not copy those titles to Busy Mirror. Do not enter patient names or other sensitive information as exclusion rules.
Google permissions
Calendar Sync requests permission to:
- Identify your Google account and obtain its email address.
- View the list of calendars available to your account.
- Read events from the source calendars you select.
- Create and manage calendars and events created by Calendar Sync.
Calendar Sync does not request permission to modify your existing source calendars. Its calendar-writing permission is used for the dedicated Busy Mirror calendar that the application creates.
How calendar data is used
Calendar Sync combines eligible unavailable periods and creates or updates a separate Busy Mirror calendar in your Google account. Mirrored events contain a generic “Busy” title, start and end times, and an internal application marker.
Calendar Sync does not copy source event titles, descriptions, locations, attendees, conferencing information, attachments, or notes into Busy Mirror. Unavailable times may still reveal patterns about a person’s schedule.
The service reads its own Busy Mirror events to reconcile updates, moved events, deletions, exclusions, and errors. If you configure another scheduling platform to consult Busy Mirror, that platform may see the generic events through its own connection to your Google account. That platform controls its own access, processing, and refresh timing, so you should review its privacy practices.
Information the application stores
The Calendar Sync database stores information needed to operate the service, including:
- Your Google account identifier and email address.
- Selected source-calendar identifiers.
- The Busy Mirror calendar identifier and name.
- User-entered exact-title exclusion rules.
- An encrypted Google refresh token.
- Account sessions, service status, and synchronization timestamps.
Source calendar events and their titles, descriptions, locations, or attendees are processed temporarily during synchronization and are not stored in the Calendar Sync database. Raw Google access tokens are not stored in the application database.
Calendar Sync does not use Google calendar content for advertising, sell it, or add it to the Degree to License marketing list. The Calendar Sync application does not include the main website’s Google Tag Manager or Meta tracking scripts.
Calendar Sync does not create, use, share, or sell aggregated or anonymized datasets derived from Google user data. Google user data is not used to develop, improve, or train generalized artificial intelligence or machine-learning models and is not transferred to third-party artificial intelligence or machine-learning services.
Service providers and operational data
Google processes account and calendar data through its APIs and stores Busy Mirror in your Google account.
The application and its PostgreSQL database run on infrastructure operated by Degree to License. Encrypted database-backup files are created for disaster recovery. Backup files are encrypted before storage, retained locally for up to 30 days, and copied to a private Google Drive folder where they are retained for up to 180 days. Google Drive therefore processes only encrypted backup files; it does not receive readable source-event data from those backups. A deleted account may remain temporarily within an encrypted backup until that backup expires and is deleted under those schedules. Backups are used only for system recovery, not advertising, profiling, or product analytics.
Brevo may receive the account holder’s email address and a generic service-status message when Calendar Sync sends a reconnect, account-attention, or persistent-delay notification. These messages do not contain source event titles, appointment details, calendar contents, or patient information.
UptimeRobot checks a public service-health endpoint to detect outages. The endpoint returns operational status only and does not expose user identities, account records, or calendar information. Like other internet services, monitoring and network providers may process routine technical request information needed to deliver and secure their services.
Degree to License does not transfer Google calendar data to advertising platforms or data brokers.
Security, disconnection, and user choices
Google refresh tokens are encrypted at rest. Production account sessions use secure, HTTP-only cookies, and public application traffic is encrypted in transit using HTTPS. These safeguards reduce risk but cannot guarantee absolute security.
You can disconnect through Calendar Sync or revoke access through your Google Account permissions. Disconnecting removes the active Calendar Sync account, encrypted Google token, calendar selections, exclusion rules, and sessions from the application database and attempts to revoke the Google authorization.
Disconnecting does not delete the existing Busy Mirror calendar or its events from Google. You can review or delete that calendar in Google Calendar. Once disconnected, Calendar Sync will no longer update it.
If an account-access or deletion request cannot be completed within the application, use the Degree to License Contact page.
Calendar Sync is not an EHR, clinical record, or representation that a practice or workflow is HIPAA compliant. Clinicians are responsible for evaluating their own systems, vendor agreements, settings, workflows, and legal or contractual obligations before connecting calendars containing regulated or sensitive information.
Calendar Sync is also governed by the Terms of Service. Use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Retention and your choices
Subscription records are kept while you remain subscribed and as needed for legal, security, or suppression-list purposes. You may unsubscribe at any time using the link in an email. To ask about, correct, or request deletion of information associated with your subscription, use the Contact page.
External links and policy updates
This site links to government agencies, platforms, and other third-party resources. Their privacy practices are governed by their own policies. This policy may be updated as the site or its services change; the date above will reflect the latest revision.
Questions about this policy can be sent through the Contact page.