Your information. Handled with care.

1. Information we collect and why

Inquiries and consultations. We collect the name, email address, service selection, message, appointment time, meeting format, address, and notes you submit. We use these details to respond, arrange consultations, provide services, prevent duplicate bookings, and communicate about your request. Appointment invitations may be sent through Google Calendar. Submitting an inquiry or booking does not automatically enroll you in marketing emails.

Support requests. We store request subjects, descriptions, categories, priority, replies, and status so clients and Raines can work through questions and changes. Requests and replies are visible only to the submitting client and authorized administrators. Replies are displayed inside the client portal; email notifications for support updates are not currently configured.

Accounts and private reflections. We use your account identifier, email address, and available display name to sign you in and provide account features. Email/password authentication is handled by Supabase; ChatGPT is an additional sign-in option. Passwords are not stored in our website content database. Vision answers and Vision Quest responses saved to an account remain private to that account and authorized administration, and are not published in the community. Questionnaire drafts may stay in your browser tab; course notes and completion may stay in your browser.

Community information. Profiles, profile photos, posts, replies, and events you choose to share are displayed to people who have access to the relevant community features. Your account email and private reflections are not displayed in the community feed. Avoid posting confidential information or information about others without permission.

Billing, client records, and referrals. We keep invoice and purchase references, amounts, payment status, and membership access information to provide services and your client portal. Card information is entered with Stripe, rather than stored in our content database. Administrator-created invoices include the recipient’s billing details and line items, which are sent to Stripe to create the invoice and deliver its email. The restricted Stripe API key used for invoicing is encrypted on our server and is never displayed back to users. Client goals and tutorial progress are associated with your account. Referral inquiries include the visitor’s name, email, and message; referring clients see the referral date and status, not those personal details.

Technical information. Hosting, authentication, and security services may process IP addresses, request details, cookies, and technical logs needed to operate and protect the site. Booking abuse prevention uses a hashed identifier derived from an IP address. Browser storage and authentication cookies support drafts, progress, sign-in, and booking security.

2. Google Calendar access and use

The Google Calendar integration helps visitors book consultations with Dylan Raines. A Raines administrator explicitly authorizes the connection through Google. Visitors can book a consultation without granting access to their own Google account or calendar.

Permissions and information accessed

• Calendar list read access: retrieve calendar identifiers, names, and access roles so the administrator can choose calendars for availability and the calendar where bookings are created.
• Free/busy access: check occupied times on the selected calendars to avoid conflicts.
• Calendar event access: read events on selected calendars to determine event times and meeting locations for travel buffers, and create, check, update, or delete consultation events as needed to administer bookings.

Google’s event responses can include titles, descriptions, attendee information, and other event fields. Our scheduling logic uses event times, status, availability, and location or booking-location metadata. Existing calendar event titles, descriptions, and attendee lists are not shown to website visitors. Availability responses expose bookable time slots, not the connected calendar’s private events.

Booking invitations and stored information

When you confirm a booking, we send its name, email, time, format, address when applicable, and notes to the selected Google Calendar. Google can send an invitation to the submitted email. Online bookings may include a Google Meet link. Booking details are visible to the calendar owner and people with access to that calendar or invitation under Google’s settings. We do not share unrelated calendar events with appointment attendees.

We store consultation records, Google event and calendar identifiers, selected calendar metadata, scheduling preferences, and authorization tokens needed to keep the connection working. Google access and refresh tokens and OAuth client credentials are encrypted on our server. Existing calendar events read for availability are processed for scheduling rather than copied into a separate calendar-event archive.

Limited Use

We handle information obtained through Google APIs in accordance with the Google API Services User Data Policy and its Limited Use requirements, together with the Google Workspace API user data and developer policy. Google Calendar information is used only to provide and support the scheduling features described here.

We do not sell Google user data, use it for advertising or audience targeting, or use it to train generalized artificial intelligence or machine-learning models. Human access to Google API data is restricted to circumstances permitted by those policies, such as your explicit authorization for a specific support purpose, necessary security investigations, or legal requirements. Transfers are limited to providing the authorized scheduling features, necessary security purposes, or legal requirements, consistent with those policies.

Disconnecting and requesting deletion

The administrator can disconnect Google Calendar in consultation settings. This removes the stored authorization tokens and disables new online bookings through the connection. It does not automatically delete existing Google events, consultation history, or saved calendar settings. You can also remove the app’s authorization through Google Account connections.

To request removal of stored Google Calendar information or booking information, email raineshq@gmail.com. We verify the requester’s identity and authority before removing relevant data. Existing events in a Google calendar can be removed by its owner or through the consultation’s cancellation process while the connection is available. Revoking Google access alone does not delete records previously stored by Raines.

3. Sharing and service providers

We share information as needed to operate the features you use: Google for calendar booking and invitations; Stripe for payments, invoices, and billing; Supabase for email/password accounts; ChatGPT/OpenAI Sites and its hosting infrastructure for site operation and optional sign-in; and FormSubmit for delivering service inquiries to Raines. These providers process relevant information under their own terms and privacy policies. Authorized Raines administrators can review information needed to respond to requests and manage services.

We do not sell your personal information. Information may be disclosed when necessary to comply with law, protect people and systems, or investigate misuse. Google API data remains subject to the more specific restrictions in Section 2.

4. Storage, security, and retention

We use encrypted network connections, account-based access controls, and restricted administration. Google authorization secrets are encrypted before storage. No online system can guarantee complete security; protect your account and private consultation management links.

We retain account information, inquiries, consultations, and client records while needed for the service, ongoing follow-up, recordkeeping, dispute resolution, or legal obligations. There is no automatic deletion schedule for all of these records. Calendar tokens are removed when the connection is disconnected. Calendar metadata and past consultation records remain until deleted or no longer needed. Browser drafts and course notes can be removed by clearing the relevant browser storage. Deleted data may remain temporarily in service-provider backups or required records.

5. Your choices and requests

You can edit your profile and delete your own community posts and replies. Use your private consultation management link to cancel an appointment, or contact us for help. Email raineshq@gmail.com to request access, correction, export, or deletion of information associated with your account or booking. Include the relevant email and a description of your request, but do not send passwords or payment-card details. We may request verification and retain information required for legal obligations or legitimate service records.

Service providers may process information in the United States and other locations. Privacy rights depend on where you live; this policy does not limit rights available under applicable law.

6. Children and policy changes

Account, community, and booking services are intended for adults. We do not knowingly collect information from children under 13 through these services. Contact us if you believe a child has submitted information that should be removed.

We may update this policy as services or requirements change. The current policy and update date will appear here. Material changes affecting Google API data use will be disclosed and any required additional consent obtained before that new use.