Dixie Desk Privacy Notice

This notice applies to dixiedesk.com and the related Dixie Desk services. In this draft, “Dixie Desk,” “we,” and “us” refer to the operator of the service. Counsel must insert the operator's complete legal name and mailing address before launch. Dixie Desk is currently designed for people in the United States.

Acknowledging this notice confirms that you received and read it; it does not waive any privacy right or replace a separate consent when the law requires one.

• Account information: name, email address, account role, authentication records, policy acceptance versions and timestamps, and support communications.
• Learner and booking information: requested subject, session time and mode, booking status, dispute records, and the student's full name supplied by an authorized adult for conflict screening.
• Session-verification information: short-lived challenge hashes, code-generation and claim attempts, which authenticated booking participant claimed the other participant's code, check-in and completion timestamps, verification method, session outcome, and payout-release state. QR and manual secrets are not stored in readable form, and Dixie Desk does not collect GPS for session check-in.
• Booking chat: plain-text messages, sender, booking thread, retry identifier, and timestamps exchanged between the educator and adult learner, parent, or guardian account holder. The first version does not accept chat attachments, HTML, or precise location.
• Educator information: public profile content, subjects, grade levels, rates, availability, service areas, credentials, license information, identity-verification status, payout status, and referral records. Public profile fields are visible to visitors after publication.
• Payment information: Stripe customer or connected-account identifiers, checkout and subscription status, amounts, discounts, commissions, payouts, refunds, and tax/accounting records. Stripe collects card, bank, tax, and identity evidence directly; Dixie Desk is not designed to store full card numbers, bank credentials, or identity-document images.
• Calendar information: the Google account identifier, granted scopes, encrypted refresh token, connection and sync status, busy windows, and identifiers for private events Dixie Desk creates.
• Approximate location: a city or ZIP you enter, or coordinates rounded to two decimal places after you choose “Use my location.” Coordinates are used for that search and are not added to the learner profile, though the search request and ordinary security logs may temporarily contain them.
• Technical information: IP address, browser/device details, timestamps, request and error logs, cookies needed for authentication and security, and records used to detect fraud or misuse. This draft does not authorize third-party behavioral advertising trackers.

We collect information from you, other booking participants, educators, service providers such as Stripe and Google, and automatically from the service when needed to operate and secure it.

We use information to:

• create and secure accounts, confirm eligibility, and provide support;
• publish approved educator profiles and power tutor search;
• request, accept, schedule, verify attendance for, pay for, document, and support sessions;
• deliver booking chat and preserve relevant attendance, completion, payout, refund, safety, and dispute evidence;
• screen current-student and other professional conflicts;
• verify educator identity and credentials and administer subscriptions, commissions, payouts, promotions, and referrals;
• sync availability and private session events with connected calendars;
• prevent fraud, enforce policies, investigate safety concerns, resolve disputes, and comply with law; and
• measure and improve service reliability using aggregated or de-identified information where practical.

Dixie Desk accounts are for adults age 18 or older. The service is not directed to children, and a child may not create an account or submit information directly. An adult learner, parent, guardian, or other legally authorized adult may book for a minor and provide only the student information reasonably needed for the session.

Booking chat and session-code controls belong to the signed-in adult account holder and educator. A parent or guardian may coordinate while a minor receives tutoring, but this feature does not create a child account or authorize unsupervised direct child messaging. Adults should not place unnecessary school, disability, health, financial, or other sensitive records in chat.

The student name is used to let the requested educator identify a current student or other professional conflict. It is not published, used for advertising, or written into Google Calendar event text. It is available only to the adult learner account, the requested educator during the active booking window, and authorized personnel handling support, safety, security, or legal obligations. Educator history views hide it after active use.

Dixie Desk is not a school and does not ordinarily receive education records from a school. Families and educators should not upload report cards, disability records, disciplinary files, health information, or other school records unless a feature specifically requests them and an appropriate legal basis exists. A school or district may not use Dixie Desk as its FERPA contractor or disclose education records under the “school official” exception without a separate written agreement and privacy review.

If you believe a child created an account or submitted information directly, email us promptly. After reasonable verification, a parent or guardian may ask to review, correct, or delete information associated with their child, subject to legal, safety, fraud-prevention, and dispute-record exceptions.

Calendar connection is optional for learners and required before an educator publishes calendar-based availability. Dixie Desk requests an OpenID account identifier plus Google Calendar event and free/busy permissions. We use those permissions only to identify the connected account, check for overlapping busy time, and create, update, or delete private availability and tutoring-session events on the connected primary calendar.

Dixie Desk retrieves only busy time windows for conflict checks and does not retain the titles, attendees, descriptions, or locations of the user's existing Google events. Events created by Dixie Desk contain generic text and internal booking or slot identifiers—not student names. The reusable token is encrypted on the server and is not exposed in the browser.

Use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy, including its Limited Use requirements. We do not sell Google user data, use it for advertising, use it to determine creditworthiness, or allow human access except with the user's affirmative permission for a specific support request, when necessary for security, or when required by law. Service providers may process it only to operate or secure the feature.

Disconnecting removes Dixie Desk's local connection and triggers a best-effort request to revoke the Google token. Google may retain events already created until the calendar owner deletes them or the sync workflow removes them.

We may disclose the minimum relevant information to:

• booking participants, such as sharing a student name and subject with the requested educator for conflict screening and session delivery, plus the booking chat and participant-visible check-in/completion status;
• service providers, including Supabase, hosting and email providers, Google, and Stripe, under their agreements and privacy terms;
• professional advisers and authorities when reasonably necessary for legal advice, a valid legal request, child safety, fraud prevention, security, or protection of rights; and
• a successor organization in a merger, financing, reorganization, or sale, subject to appropriate confidentiality and any consent required for Google user data.

Dixie Desk does not sell personal information, share it for cross-context behavioral advertising, or use it for targeted advertising. If that practice changes, we will update this notice and provide any legally required choice before the change applies.

We retain information only while reasonably needed for the purposes described here, including account operation, bookings, session verification, booking chat, safety, fraud prevention, disputes, accounting, legal compliance, and defense of claims. Account and profile records generally remain while the account is active. Payment, payout, tax, and transaction records may be kept for the legally required accounting period. Student names, chat, code-attempt logs, and attendance evidence should be deleted, restricted, or de-identified after related booking, chargeback, dispute, safety, and legal-retention needs end. Readable QR/manual secrets expire within minutes; only hashes and bounded audit records remain. Provider backups and security logs may persist for a limited recovery or security period. Counsel and engineering must approve a precise production deletion schedule before launch.

We use role-based access, server-only provider credentials, encryption for sensitive tokens and educator credentials, private calendar events, and other administrative and technical safeguards. No system is completely secure. If a security incident requires notice, we will notify affected people and authorities as required by applicable law, including Mississippi's breach-notification law.

You can decline browser location, enter a city or ZIP instead, disconnect Google Calendar, edit profile information, cancel an educator subscription through the available billing portal, or request account assistance. Subject to verification and applicable exceptions, you may ask to access, correct, delete, or receive a copy of personal information, or object to a use you believe is improper. We will not discriminate against you for making a privacy request.

Send requests to coen.mooney@dixiedesk.com. We may ask for information needed to verify the requester and the account. An authorized agent must provide proof of authority. If we deny a request, you may reply and ask us to reconsider.

We will post updates here and change the version date. If a change materially expands how previously collected information is used, we will provide additional notice and obtain renewed acknowledgment or consent when required before the new use begins.

Privacy questions and requests: coen.mooney@dixiedesk.com. Before launch, this section must also list the operator's legal name and mailing address.