Legal & Trust Center

We collect information you provide directly (name, email, profile data) and data generated through your investigation activity on the platform.

Your data is used to personalize your learning experience, track investigation progress, award XP and badges, and improve our platform.

Only the authorized CaseNest administrator connects a Google account to the waitlist reader. Learner authentication and invitations are managed through Clerk. Learners do not grant the CaseNest waitlist reader access to their Google accounts.

Google Form and its linked response sheet remain the source of waitlist submissions. Using read-only Google Sheets authorization, the CaseNest server reads only the approved email-address column from the administrator-authorized response sheet. The reader does not fetch names, phone numbers, countries, free-text answers, timestamps, demographics, or other form columns. It does not access Gmail messages or unrelated files, and it does not modify the Google Form or sheet.

Waitlist emails are used only for the administrator's waitlist review, invitation eligibility checks, and approved invitation management. The authorized administrator can view these emails in Founder Workstation. When the Founder approves an invitation, the selected recipient's email is provided to Clerk to deliver and manage that invitation. Waitlist emails are not sent to website analytics, sold, used for advertising, or used to train AI models.

Original waitlist responses remain in the Google Form and linked sheet until removed by the administrator. The reader temporarily caches email-only results in server memory with a 60-second refresh interval; it does not create a separate persistent waitlist database or copy other form answers into CaseNest. Invitation and account records are stored separately by Clerk and CaseNest for access management. Deactivating an account does not automatically erase original form responses, invitation records, payment records, or audit and integrity history.

CaseNest uses authenticated access controls and server-authoritative records. Waitlist reads require Founder authorization and a server-side Google credential. OAuth credentials remain on the server and are not exposed to learners. The reader does not log raw waitlist emails or provider payloads. If authorization, the provider response, or the approved column mapping cannot be verified, the waitlist read fails closed.

Contact CaseNest support to request access, correction, or removal of your personal data, subject to identity verification and applicable record-retention requirements. The connected Google account owner can withdraw CaseNest's authorization through their Google Account third-party connections. Revoking Google authorization does not delete original form responses or separate Clerk and CaseNest records. Contact: support@casenest.app.

Google provides the waitlist Form, response sheet, and OAuth authorization. Clerk manages learner authentication and invitations. Vercel provides hosting and cookie-free aggregate website analytics; Supabase hosts the application database; Paystack provides hosted checkout. These services support their stated functions. Private waitlist emails and investigation evidence are excluded from CaseNest website analytics.

CaseNest's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. Google-derived waitlist data is used only for the disclosed waitlist and invitation functions, with administrator access limited to those functions.