Privacy policy
Privacy
Last revised 6 September 2026
Site visits
We measure public page views and estimate daily visitors using our own server and database. Analytics does not use cookies, local storage, third-party trackers, buyer details, query strings, or referrer URLs. A network address and browser identifier are briefly processed to make a protected daily identifier; the raw values are not saved in analytics. Daily identifiers are deleted within two days, and aggregate daily counts are retained for up to 400 days. These counts are visible only to our signed-in administrator. We respect Do Not Track and Global Privacy Control signals. Admin sign-in uses a separate essential session cookie lasting up to eight hours.
Data minimization
We collect only the information required to process a purchase, deliver the selected project access, produce the project purchase record, communicate about delivery, and protect the checkout from abuse.
Buyer and purchase information
Before payment, the service collects the buyer's name, email, university, programme, academic year, optional registration details, and delivery choice. A GitHub username is collected only when repository access is requested. These fields are used for delivery, the private project purchase record, and purchase support. They are never displayed on public project pages, including after a project is sold.
Project downloads
Project packages are stored privately. Temporary download links are created only for a completed purchase and may expire. Download records contain the order, project package, time, and a protected network identifier used for security and support.
Public project records
Public pages may show the project ID, domain, status, catalogue date, completion date, technical verification date, demo evidence, deliverables, and sold status. Public records will not identify the buyer or their institution.
Project information
Private repository references, access events, purchase records, and communication records will be limited to the buyer and personnel responsible for the handover.
Payments and service providers
Payment information is handled by Dodo Payments. GeniusProject stores the transaction reference, amount, currency, and payment status, not full card details. Purchase records are sent through the GeniusProject Hostinger mailbox, and GitHub manages repository invitations.
Retention and deletion
We retain request, purchase, delivery, and security records only while they are needed for fulfilment, support, fraud prevention, accounting, or legal obligations. Unverified requests do not reserve a project and are not acted on. You can email us to request access, correction, or deletion of your information. A deletion request may be limited where a record must be retained by law or to resolve a payment or delivery dispute.
Contact
Questions can be sent to admin@geniusproject.store.