Private Pilot Privacy Notice
How personal information is handled during the limited private pre-commercial pilot.
Version privacy-private-pilot-0.1
Operator and pilot scope
ChallengeTracker is operated by Stamatis Katsiberis as an individual developer based in Greece. No legal entity has yet been formed.
This is a limited, private, pre-commercial pilot for personally selected adults aged 18 or older. No payment or commercial service is currently offered.
External legal and privacy review is planned before any broader public or commercial launch.
Information we handle
Account and profile information includes email, display name, optional profile fields, preferences, adult-eligibility statements, policy acknowledgements, and account-security records.
Challenge information includes agreements, memberships, activities, shared and personal measurements, notes, comments, reactions, invitations, notifications, ownership transfers, completion results, and retrospectives.
Beta learning information can include a broad user-selected goal category, optional privacy-minimised first-party product interactions, aggregate counters, feedback, optional surveys, and separately consented interview contact. Optional linked analytics, surveys, and interview contact default off.
Do not enter passwords, payment-card details, government identifiers, medical diagnoses, crisis information, information about minors, confidential employer information, or unnecessary highly sensitive information.
Why information is used
Information is used to provide private challenges, authenticate accounts, maintain security, deliver configured transactional messages, support exports and deletion, review reports, protect the service, respond to support, and improve the pilot.
Optional first-party analytics is not used for advertising, sale, employment or eligibility decisions, session replay, heatmaps, fingerprinting, or cross-site tracking. It excludes challenge titles, descriptions, notes, measurements, comments, names, emails, tokens, IP addresses, and raw user-agent strings.
Privacy boundaries
Challenges are private by membership. Drafts are owner-only. PERSONAL measurements and personal retrospectives are author-only, including from challenge owners and peer confirmers. Shared notes are visible only to current challenge members.
The founder may access limited operational, support, report, security, and Beta-research information only through the implemented role-controlled paths. Platform roles remain technically separate even though the founder temporarily owns each responsibility.
Service providers and processing locations
The application is deployed using Vercel and stores data using MongoDB Atlas. Better Auth is used within the application for account handling. A transactional email provider is used only when separately configured and verified.
These providers may process data outside Greece or the European Economic Area depending on their configured regions and service arrangements. Provider, transfer, and regional details will be reviewed before broader release.
Your controls
The application provides recent-authenticated JSON and CSV export controls and a 30-day account-deletion recovery period. A shared-challenge owner must complete an accepted ownership transfer before deletion can proceed.
Final deletion removes credentials and direct identifiers. Solo content is deleted; minimum non-identifying shared progress may remain as Former participant. This is practical de-identification, not a promise of mathematical anonymity.
Optional linked analytics and interview-contact permission can be withdrawn independently. Analytics withdrawal stops future linked collection and schedules raw linked interactions for removal within 30 days; non-identifying aggregate totals can remain.
Retention, testing, and security
ChallengeTracker is still under testing. Functionality and test data may change, and availability is not guaranteed. Active challenge data remains while needed to provide the pilot; archived challenges receive a review point after approximately 24 months.
Working periods include approximately 30 days for unverified registrations, 90 days for terminal invitations, 12 months for in-app notifications, 90–365 days for security and administrative audit records, and approximately 35 days for encrypted rolling backups when configured.
We use role-based access, data minimisation, hashed one-time tokens, rate limits, session controls, and restricted moderation. No online service can promise absolute security.
Contact and changes
During this pilot, support, privacy, security, reports, and Beta feedback are reviewed by the founder at stamatis.katsiberis@gmail.com. This is not a 24/7 or emergency contact.
A material change creates a new policy version and requires active acceptance again. Acceptance boxes are not preselected.
ChallengeTracker is not an emergency, medical, therapy, financial-advice, gambling, employment-certification, or formal professional-certification service.