Privacy
Privacy Policy
Effective 15 September 2026
This policy explains the information AppointFrame may process, why it is used, how connected-service data is protected, and how retention and deletion are handled.
Information AppointFrame may process
AppointFrame is appointment-scheduling software. Depending on how an organization configures and uses it, the system may process information such as names, email addresses, phone numbers, appointment details, staff and service information, locations and online-meeting details, session-package information, notification preferences, communication history, and records of appointment-related or administrative actions.
The organization operating an AppointFrame installation determines the participant and staff information it enters and the scheduling records it needs to maintain.
How information is used
Information is used to provide the scheduling functions requested by the organization and its participants, including appointment creation and changes, availability checks, reminders and notifications, session-package validation, reporting, audit history, secure access, external-calendar review and import, and support.
AppointFrame does not use appointment information or connected-calendar information for targeted advertising, personalized advertising, credit decisions, lending, sale to data brokers or information resellers, or the training of generalized artificial-intelligence or machine-learning models.
Public demo workspace and cookie
The public AppointFrame homepage does not create a demo sandbox cookie. When a visitor chooses a demo experience, AppointFrame first explains the temporary workspace. If the visitor continues, the demo uses one strictly necessary HTTP-only cookie, appointframe_demo_sandbox, containing a random identifier that connects that browser to its isolated temporary demo database.
The cookie is not used for advertising, analytics, profiling or cross-site tracking. The demo workspace uses a sliding 24-hour inactivity window and is automatically removed after it expires. Clearing the cookie breaks the browser-to-workspace association and a later demo visit starts fresh. The public demo uses fictional seed data, and visitors should not enter confidential or sensitive real information while experimenting.
Website enquiries are separate from the sandbox. If a visitor submits the AppointFrame contact form, the information they voluntarily provide is relayed through Formspree to the monitored AppointFrame contact mailbox.
Connected calendars and OAuth account data
Where the feature is enabled, an authorized AppointFrame administrator may connect an external calendar. The connection is optional and uses the authorization screen provided by the external provider.
Google Calendar
AppointFrame requests read-only access to the administrator's Google calendar list and calendar events. It does not request permission to create, edit or delete Google Calendar events. Depending on the event, information read for review may include calendar and event identifiers, calendar name, event title and description, date and time, time zone, location, online-meeting link, organizer details, attendee names or email addresses and response information, recurrence information, event status and Google attachment metadata. Google attachment contents remain with Google and are not imported into AppointFrame.
AppointFrame's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy and the Google Workspace User Data and Developer Policy, including the Limited Use requirements.
Microsoft Outlook / Microsoft 365
When Microsoft calendar connectivity is configured and enabled, AppointFrame uses Microsoft OAuth / Entra authorization to obtain basic connected-account information and read-only calendar access. The requested Microsoft permissions are limited to the account/profile information needed to identify the connected account, read calendar data, and maintain the authorized connection. AppointFrame does not request permission to create, edit or delete Microsoft calendar events.
How calendar information becomes AppointFrame data
Calendar events are read so an authorized administrator can review them. An external event does not automatically become an AppointFrame appointment. If the administrator explicitly imports an eligible event, AppointFrame creates an appointment through its normal scheduling rules and may retain limited source information such as the provider, calendar and event identifiers, event title, date/time, time zone, location or meeting link, recurrence identifiers, organizer email, event version information, and the administrator's mapping choices. This retained information is used for duplicate prevention, auditability, mapping assistance, and later change or cancellation review.
How connected-service and sensitive data is protected
AppointFrame uses technical and administrative safeguards appropriate to the information it processes. In particular:
- Production OAuth callbacks require an HTTPS AppointFrame public address, and communications with Google and Microsoft authorization and API endpoints use HTTPS/TLS.
- Google and Microsoft OAuth access and refresh tokens stored by AppointFrame are encrypted at rest using AES-256-GCM with a deployment-specific encryption key.
- OAuth authorization uses PKCE with S256. Temporary OAuth authorization verifiers are encrypted while stored, browser state is stored only as a cryptographic hash, and OAuth state is short-lived and one-time use.
- Calendar connection, reconnect, disconnect and related administrative controls are restricted to authenticated AppointFrame administrators, with state-changing administrator requests protected by the application's request-forgery controls.
- AppointFrame requests read-only calendar permissions and limits connected-calendar use to the calendar review, import and reconciliation features presented to the administrator.
- Application and hosting access is limited to the access necessary to operate, secure and support the service.
No internet-connected service can guarantee absolute security. AppointFrame therefore also limits the data and permissions requested to those needed for the configured functionality.
Sharing and transfer of information
AppointFrame is not designed to sell personal information or connected-service data. Information may be processed by hosting, email, messaging or other service providers only where needed to provide configured AppointFrame functionality, maintain security, or comply with applicable legal obligations.
Google user data is not transferred or disclosed to third parties for advertising, data-broker, information-resale, credit or lending purposes. Human access to connected-calendar data is limited to authorized use needed to operate the user-facing feature, provide support with appropriate authorization, investigate security or abuse, or comply with applicable law.
Email and WhatsApp
If an organization enables email or WhatsApp features, information needed to deliver those communications is sent to the relevant service provider. WhatsApp messaging is provided through the WhatsApp Business Platform operated by Meta. Those external services process information under their own terms and privacy policies.
Retention of connected-calendar and other data
AppointFrame retains information only for as long as reasonably necessary for the purposes described in this policy, the operational and record-keeping needs of the organization using AppointFrame, security and dispute resolution, or applicable legal obligations.
- OAuth connection credentials: stored while the calendar connection is active. When an administrator disconnects a calendar in AppointFrame, AppointFrame deletes its stored OAuth connection record and encrypted token bundle and stops using those credentials. The administrator can also revoke AppointFrame separately through the Google or Microsoft account's own connected-app controls.
- Temporary OAuth authorization data: short-lived, one-time authorization state is removed when used and is rejected after expiry.
- Calendar events reviewed but not imported: event data is retrieved from the connected provider for administrator review and is not converted into an AppointFrame appointment unless the administrator explicitly chooses to import it.
- Imported or linked calendar events: limited provider-derived source information may remain with the related AppointFrame appointment, import mapping or reconciliation history for as long as that operational record is retained. Disconnecting the external calendar stops future access but does not automatically delete appointments or historical records that were already created in AppointFrame.
- Appointments and operational records: may be retained to maintain scheduling history, reports, package accounting, auditability and other functions requested by the organization operating the AppointFrame installation.
When retained information is no longer needed for the purposes above, it should be deleted or anonymized where reasonably practicable, subject to information that must be retained for legal, security, fraud-prevention or dispute-resolution purposes.
Deletion and other privacy choices
You may ask what information is held about you, request correction, or request deletion where applicable. Because an organization using AppointFrame controls its participant and appointment records, AppointFrame may need to coordinate a request with that organization.
A deletion request can include identifiable information derived from a connected calendar. Where applicable, that information will be deleted or anonymized unless limited retention is reasonably necessary for legal, security, fraud-prevention or dispute-resolution purposes. Deleting or disconnecting information in AppointFrame does not automatically delete information independently retained by Google, Microsoft, Meta, an email provider, or another external service.
Changes to this policy
This page may be updated as AppointFrame functionality, connected-service integrations, security practices or deployment practices change. The effective date above identifies the current version.