Privacy Policy
This policy explains what ProjectPrint collects, why it is collected, how long it is kept, which service providers are involved, and the choices available to visitors and members.
Effective / last updated: August 12, 2026
1. Who is responsible for the data
test operates the ProjectPrint website and acts as the controller for data described in this policy.
Privacy contact: test.
2. Information we collect
Website analytics, only after consent
When analytics consent is granted, we create random first-party visitor and session identifiers and record:
- pages viewed, page titles, visit times, time engaged, scroll depth, landing page, and exit page;
- click events such as Discord, Premium, internal navigation, and external link clicks;
- referring domain and UTM campaign parameters;
- browser, operating system, device class, language, timezone, screen and viewport size;
- coarse country, region, and city information supplied by the hosting platform; and
- whether a session clicked through toward the Premium checkout. A checkout click is not treated as proof of purchase.
ProjectPrint does not store full IP addresses in its first-party analytics tables. Hosting and security providers may temporarily process IP addresses in ordinary network and security logs.
Authentication and membership
When a visitor signs in through Whop, Discord, Google, or another connected provider, we may process account identifiers, email address, display name, membership/access status, authentication tokens, and related security records needed to provide access.
Member portal, recap-video engagement, journals, and community activity
For authenticated recap-video playback, ProjectPrint may record which recap a member played, approximate active watch time, playback sessions, completion, repeat viewing, and playback progress. This first-party member engagement data is used to understand whether educational content is being used and where the member experience can be improved. It is not used as proof of trading performance and does not store full IP addresses.
Members may choose to create trading journals, goals, risk plans, trade-review requests, bookmarks, comments, and community chat messages. Journals are private by default. If a member explicitly shares a journal to the community, other members receive a pseudonymous version that does not expose the member's real name, email, Whop username, Discord username, billing details, IP address, or internal member identifier.
Pseudonymous community activity is not untraceably anonymous. ProjectPrint administrators may access the underlying account mapping when reasonably necessary for moderation, support, security, abuse prevention, or platform operation. Members can unshare or delete their own journal content through the portal, subject to limited security, audit, backup, and legal-retention needs.
Messages sent through Discord, support channels, feedback forms, or email may include the information the sender chooses to provide. Discord and other community platforms process this activity under their own policies.
AI-assisted member reviews
When a member actively requests an AI Review, ProjectPrint may send the relevant journal text, saved process and risk-plan context, summarized live-attendance information, recent process posts, and the selected trade screenshot when available to the configured AI service provider so the requested review can be generated. ProjectPrint is designed to minimize the information sent for this feature and does not intentionally include the member's email address, billing details, Discord username, or raw account balance in the AI review prompt.
AI-generated reviews can be inaccurate or incomplete. They are provided as educational process feedback and are not trading signals, personalized financial advice, or a substitute for the member's own risk rules and judgment.
Payment information
Payments are processed by Whop and its payment partners. ProjectPrint does not receive complete card numbers. We may receive transaction, product, subscription, invoice, trial, refund, failure-reason, billing-management-link, and access-status information needed to operate the service and send limited transactional payment reminders.
3. Why we use information
- Consent: optional audience analytics, conversion measurement, and marketing tracking.
- Contract and requested services: account access, membership verification, Premium delivery, member-portal features, support, journaling, trade reviews, and community participation.
- Legitimate interests: security, fraud prevention, service reliability, aggregated business reporting, and defending legal claims, where those interests do not override individual rights.
- Legal obligations: accounting, tax, consumer protection, lawful requests, and compliance duties where applicable.
4. Cookies and tracking choices
Optional analytics and marketing technologies remain off until a choice is given. Necessary cookies support authentication, security, and saved privacy choices. The banner uses a coarse country code to present EU/UK, US, or general privacy wording. A recognized Global Privacy Control signal disables marketing tracking. Choices can be changed or withdrawn at any time through the Cookie Settings link in the website footer.
Authenticated member recap-playback measurement is account-linked service engagement used to improve member delivery and is separate from optional anonymous/marketing website analytics consent. More detail is available in the Cookie Policy.
Transactional billing emails may use a signed ProjectPrint redirect and a one-pixel image to estimate link clicks and email opens. Open data is approximate because mailbox privacy tools, image proxies, and blocked images can create false or missing signals. ProjectPrint stores a one-way hash rather than the raw IP address for first-party email engagement events.
5. Service providers and recipients
Information may be processed by providers that help run ProjectPrint, including:
- Vercel for website hosting, delivery, security, and optional analytics;
- Supabase for database, authentication, server-side data storage, member-portal records, and protected media references;
- Whop for checkout, membership, access verification, billing status, and marketing measurement after consent;
- Resend for transactional billing-recovery email delivery, delivery, delay, open, click, bounce, failure, suppression, and complaint events;
- Discord for community communication and live-stage activity;
- Bunny.net for protected trade-recap video processing and delivery where enabled;
- OpenAI for member-requested AI Review generation where that feature is enabled;
- professional advisers, authorities, or counterparties where legally required or necessary to protect rights.
These providers may process data in countries outside the visitor's country. Where required, transfers rely on recognized safeguards such as adequacy decisions or contractual protections.
6. Retention
- First-party raw website analytics are configured for deletion after approximately 395 days.
- Cookie-consent logs are configured for deletion after approximately 730 days.
- Authentication, membership, payment, support, member-portal, moderation, and security records are kept only as long as needed for the stated purpose, contractual obligations, dispute handling, and legal requirements.
Backups may retain deleted information for a limited period before secure rotation.
7. Individual rights
Depending on location, individuals may have rights to access, correct, delete, restrict, object to processing, receive portable data, withdraw consent, and complain to a supervisory authority. Consent withdrawal does not affect processing that occurred before withdrawal.
Anonymous analytics linked to the current browser can be deleted directly through Cookie Settings. Other requests can be sent to test. Verification may be required before acting on a request.
8. Security and data minimization
ProjectPrint uses access controls, server-side secrets, Google-admin allowlisting, row-level database restrictions, encrypted transport, and limited data collection. No system is completely secure, and absolute security cannot be guaranteed.
9. Children
ProjectPrint is not designed to collect personal data from children who cannot legally consent to the relevant services in their country. A parent or guardian who believes a child supplied information should contact us.
10. Changes to this policy
This policy may be updated when services, providers, laws, or tracking practices change. The effective date at the top will be updated, and material changes may be highlighted on the website.
