Privacy Policy

This policy describes what information the trialtwo platform actually collects today, why, and what happens to it. It is written from the application’s real data model — if the platform changes, this document must change with it.

Waitlist. Before launch, the home page offers a waitlist. If you join, we store your email address, the interest you selected (backing, launching, or both, if any), where the signup came from, and the time. We use it to send you one invitation when trialtwo opens. It is not shared, not used for marketing, and is deleted on request (email the address in section 8) or when the waitlist is retired.

Account information. Your email address and a password (stored only as a secure hash by our authentication provider), and the date you accepted the Terms of Service and which version.

Profile information. Your username, display name, and any bio or avatar image you add. These are public.

Project information. Everything a founder enters about a project — title, story, budget, milestones, funding settings, offers, updates, and uploaded images. Published projects are public.

Support records. When you support a project (all support is currently simulated), we record what you committed to, the amount, when, and the offer version you accepted, together with a history of status changes (who changed what, when). If a reward requires delivery, the delivery name and address you enter — and any answers you give to a founder’s fulfilment survey (sizes, variants) — are stored in separate, restricted tables visible only to you and that project’s founder. You can choose to hide your name from the public on a commitment.

Social activity. Follows, saved projects, likes, comments, replies, questions you ask founders, and reports you submit. Saved projects, your collections and private notes, and the people you block or mute are private to you; questions you ask are private to you and the founder unless you choose public Q&A and the founder publishes the exchange; reports are visible only to you and the moderation team.

Moderation and audit records. Reports about content, moderation decisions, suspensions, and appeals are kept in an audit trail for platform integrity.

Product usage events. To understand whether the platform works for people, we record a small, fixed set of usage events in our own database: the home page being viewed, a project card being seen or opened, a project page being opened, a sign-up or sign-in being started and completed, a project being shared, a project being followed or unfollowed, and — for founders — the steps of creating a project (the start screen opened, a draft created or resumed, a stage completed, a media upload succeeding or failing, a validation message shown, and a publish attempted or succeeded). Each event stores only the event name, the time, the project involved (if any), the position of a card in the feed, which action you were trying to take when you were asked to sign in, and for creation events the stage name plus a short code (a field name, an error code, or a media type and size bracket — never the text you typed or the files you uploaded). If you are signed in, the event is linked to your account. Events from a visit also carry a random identifier kept in your browser tab only (it is not a cookie, is not sent to anyone else, and disappears when the tab closes), so that an impression can be linked to a click within that visit. We do not record IP addresses, device or browser details, or page addresses beyond the route itself. These events are kept for 90 days and then deleted automatically; deleting your account deletes the events linked to it. They are used only in aggregate (for example, “what share of card views lead to a click”) by platform administrators.

Technical information. Server logs for errors and security events (written to avoid including personal content — records are referenced by ID), and short-lived, in-memory request counts per network address for rate limiting (not persisted to the database).

The platform uses cookies only to keep you signed in (authentication session cookies set by our authentication provider). Product usage is measured with the first-party events described in section 2, stored in our own database. There is no third-party analytics, no advertising, no cross-site tracking, no tracking cookies, and no browser fingerprinting on the platform, and no third-party marketing scripts.

If you are signed in, the searches you submit are kept in your own search history (the most recent 30, for up to 90 days) so you can repeat them, and the interest categories you choose are stored with your account. Both are private to you, both power the recommendations shown to you on the website and in the app, and you can clear or change them at any time from the Discover page and your account settings. Trending searches are computed only from terms that at least three different people searched.

• to operate the product: accounts, projects, support, feeds, notifications;
• to show founders who supported their project and what fulfilment requires (for example, delivery details for a physical reward);
• to keep the platform safe: moderation, rate limiting, audit trails, security logging;
• to understand, in aggregate, how discovery, sign-up, sign-in, sharing and following are used, so we can improve them (section 2, product usage events); and
• to send the emails the product needs (account confirmation and password reset). There is currently no marketing email.

We do not sell personal information.

The platform’s database, file storage, and authentication are hosted on Supabase infrastructure located in Tokyo, Japan (AWS ap-northeast-1). That means your information is stored and processed outside Australia. Access to the database is controlled with per-row security rules enforced in the database itself: for example, your saved projects are readable only by you, and delivery addresses are readable only by you and the relevant founder.

• Public: your profile (username, display name, bio, avatar), published projects, comments, likes, follows, and — unless you mark a commitment anonymous — your support of a project.
• You and the founder: your commitments on their project and any delivery details you provided.
• Only you: saved projects, notifications, your commitment history across projects.
• Moderation/administration: reports, moderation records, suspension state — visible to platform staff roles only.
• Service providers: Supabase (hosting, database, authentication, file storage) processes data on our behalf. No payment provider is connected yet.

You can deactivate your account from your account page; this hides your profile but is reversible. Permanent deletion is currently a manual process handled on request. When an account is deleted, content needed for the integrity of other people’s campaigns (for example, the record that a published offer version existed, or aggregate support totals) may be retained without your identity attached — supporter identity on retained records is removed rather than kept.

To be decided: Concrete retention periods (for logs, moderation records, and deleted-account data) and a self-service deletion flow have not been defined. (Tracked in docs/legal/open-decisions.md.)

• You can edit your profile and most content you created.
• You can support projects without your name shown publicly.
• You can cancel pending commitments and unfollow/unsave at any time.
• You can request access to or correction or deletion of your personal information using the contact below.

Australian users may have rights under the Privacy Act 1988 (Cth), including making a complaint to the OAIC. This platform has not yet been assessed for Privacy Act compliance — that assessment is part of the required pre-launch legal review.

Access control is enforced in the database with row-level security on every table, privileged operations run through audited server-side functions, secrets are kept out of the codebase, and passwords are handled solely by the authentication provider. No system is perfectly secure; if a data breach occurs that is likely to result in serious harm, we will notify affected users and, where required, the relevant regulator.

This policy is versioned and dated; material changes will be announced in-product before they take effect.

To be decided: A privacy contact (email address and responsible person/entity) has not been established yet and is required before launch. (Tracked in docs/legal/open-decisions.md.)