Draft — legal approval required

Program privacy notice — DRAFT / NOT OPEN

Controller: ThackTree LLC [confirm legal name, address, privacy contact].
Giveaway information: name, normalized email, state, adult/residency attestation,
entry time, rules version, optional marketing choice, documented manual review
and drawing/award records. Names/emails are not included in drawing snapshots.
One email record is allowed; separate manual identity review addresses multiple
emails belonging to the same person. No technical system guarantees one human
per entry without that review. No identity-document upload is requested.

Opportunity information: name, email, preferred path, WHY/WHAT/HOW responses,
optional proposed payment schedule, review status, exact agreement, acceptance
and manual access decision. Do not provide bank numbers, Social Security numbers,
credit-card information, tax returns, medical records or financial documents.
Brian uses this information to review requests, prepare agreements and administer
access. Assistance does not require referrals, marketing or publicity. Requests
are assessed respectfully for course fit, intended use, workable schedule and
available assistance capacity; no automatic scoring or approval.

Only Brian’s designated admin account can review program submissions. Student
accounts see only their own offered agreement and winner permissions. Data is
stored in the existing protected SQLite database; never serve the repository or
database directory statically. Local form submissions stay in this backend;
there is no email delivery, payment integration, analytics upload or automatic
third-party submission. Hosting/backups and processor disclosures must be
confirmed before launch. The existing interest-list link leads to Airtable;
its separate privacy/consent process must be verified before real use.

Marketing: separately optional and unchecked for the giveaway. Saying no has
no effect on eligibility or odds. No marketing email is sent by this system.
[Before launch: identify sender, unsubscribe mechanism, contact and processor,
and establish revocation/suppression handling. Brian can record withdrawal in
admin controls; preserve a minimal suppression record as counsel approves.]

Winner publicity: first name, state, selected path and statement are individually
optional. Permission starts absent; winners can revoke any field immediately
via their authenticated account. Winning alone does not authorize publication.
Changes are audited without copying the statement into the audit payload.

[Set and approve specific retention periods before opening: unsuccessful
applications, entries, winner/audit records, accepted agreements, consent records,
security rate-limit data and backups. Define deletion and backup expiry process.
Audit/financial records may need restricted retention rather than immediate
removal; communicate reasons and applicable rights.]

Contact [privacy email] to request correction, access, deletion, marketing
withdrawal, or manual publicity withdrawal. [Confirm response times, identity
verification and rights applicable in each jurisdiction.] Avoid requesting
sensitive financial proof. Do not send application stories in ordinary email
threads or put them in support tickets, logs or analytics. Restrict database and
backup permissions; encrypt disks/backups and use HTTPS in production.

Analytics and search-engine tools remain disconnected. Any future activation
requires Brian’s approval, consent/notice review and verification that no names,
emails, form text, account IDs, tokens, URLs containing personal information or
private page activity are transmitted.