YOUR INFORMATION
Privacy in the Academy.
What the workspace stores
Academy stores your verified account email and name, application context, learning plan, submissions, feedback, support history and account preferences to deliver the program. A résumé file is parsed in your browser; the original file is not uploaded. Extracted text you confirm and submit becomes part of your application.
AI and service providers
Context you submit for planning or coaching is processed through OpenAI. Sign-in emails, essential application, admission, payment and enrollment notices, and opted-in learning updates use NeoAistriq’s managed Lovable sender. Essential service notices are delivered regardless of the optional learning-email preference. Email verification codes are currently the only sign-in option. Payments use Stripe’s hosted checkout. Operator-supplied restricted Stripe keys are verified and encrypted server-side, never copied into learner records or returned to the browser. Payment/setup records are distinct from learning records. Do not submit passwords, API keys, customer records or confidential employer information.
Access to your work
Program operators and your assigned reviewer can access relevant learning records for admission, delivery and review. Referrers see attribution status, not another learner’s résumé, diagnostic or submissions. Project examples and practice data should be synthetic.
Professional directory and opportunity interests
Your role, country and timezone support personalization and delivery planning. Business-owner operating context, course drafts and concept checks, content issue reports, pilot observation notes and confirmed workflow context, concept diagnostics, saved practice drafts, engineering bridge evidence, scoped capability assessments and introduction consent/status records are also stored. Foundation answers, generated adaptive lessons, submitted practice responses, formative feedback, human skill reviews and tool-access/budget declarations are stored with your learning records. Adaptive generation uses relevant professional context and evidence gaps; it does not need your full résumé. Deleting learning records also removes these adaptive records. Teaching-library review records are retained as program audit records. Private generated lessons are cached for their original context. Shared reuse uses separately reviewed generic fictional templates; résumés, private workflow details and submissions are not automatically promoted into shared teaching. Directory participation requires assessed completion, separate consent and operator moderation. The profile fields you submit and any current scoped capability label, assessment date, scope and supervision limitations are shown to enrolled members and graduates. Private submissions, résumé text and account email are not copied into the directory. Editing a profile returns it to moderation; withdrawing consent removes its visibility. Opportunity and support interests remain private to you and program operators. External introductions require a separate decision and consent to the specific recipient and proposed disclosure. The application records this permission and progress; it does not send an introduction automatically.
Your controls
You can export learning evidence, change learning-email preferences and delete learning records from the workspace. Deleting learning records also removes queued learning-update payloads. Account identity, payment records, operator audit records and short-lived security counters are separate; deletion does not erase legally retained financial records. You can raise other data requests through the support workspace or NeoAistriq’s website contact channel.
Sign-in and security
Academy uses secure session cookies. If you follow a referral link, its code may be retained in your browser session to preserve attribution while you explore the public pages. Email verification codes are short lived and stored as hashes. Google handoffs use browser-bound state and one-time codes. Account access does not itself grant paid enrollment or reviewer permission.
This page explains the current program handling. Any additional seller-specific notices are provided with your enrollment offer.
Operational monitoring
We count aggregate public page requests by path and day, without retaining IP addresses, query strings, tracking cookies or device fingerprints. Do Not Track and Global Privacy Control requests are excluded. Counts can include repeat requests and bots. Operational alerts go to the Academy leadership inbox. Application alerts include submitted professional details, written responses, diagnostic selections, screening recommendations and any submitted resume text for admissions review. Payment and enrollment alerts include learner identity, relevant states and record references. Network action alerts include member identity, profile-review status and reasons, submitted opportunity or support interest, and introduction progress. Member action receipts are essential account messages and are separate from optional learning emails. Exact introduction recipient and proposed disclosure remain in the authenticated workspace; they are not copied into email alerts. Opportunity listings are not automatically emailed as marketing broadcasts. Private support conversations, card information and credentials are not included. Pending checkouts may be flagged for review after one hour; this is not proof of abandonment. Monitoring email logs and aggregate page counts are retained for up to 90 days.