Privacy Policy

Current status of scheduling and contact forms

Public online booking is not currently enabled. While booking is disabled, completing the displayed form does not transmit a booking to John, create a calendar event or send a booking email. The scheduling disclosures below describe the implemented workflow that will operate only after activation.

The contact form asks for a name, email address and message; please do not include sensitive case details. When the form is switched on, entries are checked on our server and sent as one email from John’s Gmail account to john@johncorbally.com, with your address set as the reply address. The website does not save your name, email or message. To prevent duplicate emails and abuse, it keeps a random request number, a one-way scrambled form of your internet address, the delivery status and the time. The form is not yet switched on.

Personal and case-related scheduling information

When online booking is enabled, a submitted request includes:

• The scheduling contact’s name, email address and telephone number
• The party responsible for payment; no payment card or bank account information is requested
• Case style and date of accident, plus the SBWC case number if supplied
• Names and email addresses of claimant’s counsel and defense counsel
• Selected date and time, expected duration, and format: in person, virtual or hybrid
• Preferred location for in-person or hybrid mediation
• Optional basic case information, limited to 1,500 characters
• A generated request identifier used to recognize retries of the same booking

Case style and optional case information may identify the claimant, employer, insurer or other people involved in a matter. Provide only the information needed to schedule mediation and only information you are authorized to share. Do not submit medical records, Social Security numbers, financial account details or other sensitive supporting documents. The form does not accept document uploads.

Submitted information is processed by the website’s server to validate the request, check availability, create the booking event and send the notifications described below. Form entries remain temporarily in browser memory while the form is open; the application does not save them to browser storage for later visits.

Google account identity and calendar selection

John authorizes Calendar and Gmail through Google’s consent screen. The application requests OpenID and email access to check the Google account’s email address and verified-email status against the permitted owner account. This is separate from John’s website sign-in.

Calendar list read-only permission (calendar.calendarlist.readonly) retrieves identifiers, names and primary-calendar status for calendars John can write to, so he can choose the booking calendar. The server checks his owner or writer access before saving that selection. These calendar names and identifiers are shown only on the owner’s connection page, not in public availability.

How Google Calendar free/busy information is used

Calendar free/busy permission (calendar.freebusy) lets the server ask Google for occupied start and end times on the selected calendar within the requested date range. The application uses these intervals to calculate open morning and afternoon slots in America/New_York time and to check again for conflicts before a booking event is written. Existing appointments and blocks on that calendar can make a slot unavailable.

Free/busy lookup does not retrieve appointment titles, descriptions, attendees or case details. The public availability response contains busy start and end times only; the calendar display converts them into availability statuses. Busy intervals are processed for the lookup and are not saved in a separate website availability database.

How booking calendar events are created and managed

Calendar events permission (calendar.events) is broader than free/busy access. The implemented workflow uses it to create and read booking events, update their private processing properties, and reuse a cancelled booking event for a later request for the same slot. The application does not use event access to publish existing calendar contents or browse unrelated appointments.

Each successful booking creates an event on John’s selected Google Calendar. Its title contains the case style; its description contains the scheduling and case information listed above. Its start and end times reserve the slot. The event is marked private and busy. A slot-based event identifier, the request identifier and notification-sent flags support conflict checks and retries.

The application adds no calendar guests and sends no Google Calendar invitations. Counsel email addresses are recorded in the private event description, not added as attendees. Event details are not returned to public visitors. The private setting is not an absolute confidentiality guarantee: access within Google remains subject to the calendar’s permissions and any applicable Workspace administration settings.

Once enabled, the system reports a booking as confirmed after the calendar event has been created; email delivery may still be delayed. Changes and cancellations are handled directly with John, not through a public self-service cancellation or deletion feature.

How Gmail sending permission is used

Gmail send permission (gmail.send) lets the server send booking-related email from John’s Google account. It does not grant the application permission to read, search or delete his inbox messages. The implemented notifications are:

• A confirmation to the scheduling contact’s supplied email address containing the mediation date, time and format, location or video-link follow-up wording, and instructions to reply for changes or cancellation. It does not include the case style or the other intake details.
• A notification to John containing the case style and the full scheduling information from the private event description.

The application does not automatically email claimant’s counsel, defense counsel or the payment party unless that person is the scheduling contact. It does not generate a video meeting link. Google processes outgoing messages; copies may remain in John’s mailbox and recipients’ email systems under those services’ own settings and retention practices.

What is stored and which providers process it

• Google Calendar: booking event titles, times, intake descriptions, private request identifiers and email-status flags. These booking records are not stored in a separate website booking database.
• Google Gmail and recipients’ email providers: the outgoing notifications and any copies retained in mailboxes. John’s notification includes intake details; the scheduler’s notification is limited as described above.
• Lovable Cloud: the owner’s website authentication record and sign-in/session processing; encrypted Google access and refresh tokens; Google email address, granted permissions, token-expiry and connection timestamps; and the chosen calendar identifier, name and settings update time.
• Temporary authorization records in Lovable Cloud: a one-time state value, service being connected, owner account identifier, encrypted authorization verifier, a hash of the browser nonce, return website origin and creation time.
• The owner’s browser: the website sign-in session and a temporary cookie binding the Google authorization attempt to that browser. Google API access and refresh tokens are not returned to the browser.

Lovable provides website hosting and Lovable Cloud processing. Google provides account authorization, Calendar and Gmail processing. The website has no implemented payment collection or separate booking email service. This description does not establish a geographic storage location or a complete list of these providers’ own subprocessors.

Hosting necessarily handles requests to the site, including network and browser information. The site’s error-handling code can report error messages, stack information and the affected page to Lovable’s diagnostic hooks when available; server failures can also be logged. The precise production logging, analytics, backup and provider-retention settings require confirmation below.

Google token security, refresh and disconnection

Google access and refresh tokens are encrypted with AES-256-GCM before storage in server-restricted connection records. The encryption key and OAuth client secret are held as server environment secrets, not included in public pages. Owner-only authenticated functions manage the connection; visitors cannot read the connection records.

Authorization uses PKCE, a one-time state value and a browser-bound nonce. The nonce cookie is Secure, HttpOnly and SameSite=Lax and has a ten-minute lifetime. The server rejects authorization attempts older than ten minutes. These measures reduce particular risks; they do not guarantee absolute security or constitute a security certification.

Offline access allows the server to exchange the stored refresh token with Google for a new access token when needed, without John being present. The refreshed access token is encrypted and its expiry updated. If Google reports an invalid grant, the corresponding stored connection is removed and authorization is needed again.

John can select Disconnect on the private connection page. The application sends a token-revocation request to Google and deletes the corresponding local connection record. The current implementation does not verify that Google completed revocation, so disconnection must not be understood as a guarantee of confirmed revocation. John can also remove the app’s access directly in Google account permissions. Disconnecting does not delete existing calendar events, sent emails, the owner’s website account or the saved calendar selection.

Sharing and access by other parties

Scheduling information is provided to John, Google and the hosting and processing services needed for the workflow. The scheduling contact’s email provider processes the confirmation sent to that contact. The application does not publicly display case information, send it to other counsel automatically, or implement sales of personal information, advertising transfers or data-broker integrations.

Sharing or access outside this website workflow, including John’s professional record handling and access by anyone administering his Workspace account or supporting the website, must be confirmed by the business. A private calendar event alone does not establish who has access under all provider or business arrangements.

Google API Services User Data Policy and Limited Use

John Corbally Mediation’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the applicable Limited Use requirements. The following commitments apply to Google data and data derived from it:

• Use is limited to providing or improving the visible scheduling, calendar-connection and booking-notification features described in this policy.
• Transfers are limited to providing or improving those appropriate user-facing features with the user’s consent, necessary security purposes, compliance with applicable law, or a merger, acquisition or asset sale after obtaining the user’s explicit prior consent.
• Human access is limited to the user’s affirmative agreement to view specific data, necessary security purposes, compliance with applicable law, or aggregated data used for internal operations in accordance with applicable privacy law.
• Google data is not sold or transferred to advertising platforms, data brokers or information resellers, used for advertising or retargeting, or used to determine creditworthiness or for lending.
• Google data is not used to train generalized artificial intelligence or machine-learning models.
• Employees, agents, contractors and successors with permitted access must comply with these requirements. Any additional use or access requires appropriate disclosure and consent before it begins.

These commitments are presented for business review and approval, not as a claim that Google has verified or certified this application.

Retention and deletion

The website implements no automatic age-based deletion of booking events or emails and no fixed business retention period. Those records remain in Google Calendar and mailboxes until removed under the relevant account’s practices. Deleting or cancelling a calendar event does not remove copies of notification emails. Removing data from John’s accounts cannot remove copies held independently by recipients.

Connection records remain until disconnection, replacement during reconnection or removal following an invalid-grant response. Authorization state is deleted when a callback consumes it; records older than fifteen minutes are cleaned up when a new authorization begins, not by a continuously scheduled deletion job. The nonce cookie expires after ten minutes and is cleared on callback. Owner authentication records and calendar settings are not deleted by Google disconnection.

The application has no visitor account or automated deletion-request portal. The business must confirm how it handles access, correction and deletion requests, verifies a requester’s identity, and identifies any records it must retain. Provider backups, logs and recovery copies may follow separate retention practices; no deletion deadline or immediate removal from all backups is promised here.

Resource Center and browser processing

Present-value calculations and Resource Desk searches operate in the browser using fixed resource content. The application does not transmit calculator inputs or search questions to an AI service, save question histories or create user profiles from them. Search and calculator state is temporary, not written to persistent browser storage. External government-source links lead to other websites whose own policies apply.

Privacy contact and items requiring confirmation

John Corbally Mediation is the business responsible for this notice. For privacy questions or requests to access, correct or delete information, the proposed contact is john@johncorbally.com, subject to John’s final approval. This Google Workspace mailbox is operational and has been tested. Do not send sensitive case documents with an initial privacy request. Do not use the website contact form until its message delivery has been connected and verified.

• To be confirmed: John’s final approval of john@johncorbally.com as the published privacy and deletion contact.
• To be confirmed: the business retention schedule for calendar events, emails and inquiries; deletion-request handling, identity checks and any recordkeeping exceptions.
• To be confirmed: any additional providers, personnel access or sharing outside the implemented workflow, and actual hosting analytics, cookies, logs and backup retention.
• To be confirmed: John’s approval of the policy’s factual disclosures and Limited Use commitments before this revised policy is published.

Changes to this policy

We will update this notice when the described practices change. The date above identifies the latest revision. Material changes to Google data access or use require updated disclosures and appropriate consent before that access or use begins. See also our Terms of Use.