Privacy

Who we are

OUTCHOKE.LOL is an independent internet experiment, made in the spirit of the satirical software wave begun by outbit.lol and similar projects. We are not affiliated with those projects. This policy explains, at the level we consider appropriate to publish, what information this experiment involves. Operational specifics are internal security matters and are deliberately described only by category.

The principle

We process only the minimum information required to operate a public, credit-based leaderboard experiment — nothing more, retained no longer than useful. We never sell data, run advertising trackers, or profile you across other sites. Analytics, where enabled, are aggregate visitor counts supplied cookieless by our hosting provider.

What is involved in using the site

• Account access. Interactive features require signing in through a third-party identity provider chosen by us (currently X). Only the public profile details needed to recognise your account reach us; authentication secrets held by that provider stay there, and we do not retain them beyond completing sign-in.
• Your choices. What you voluntarily tell the experiment — which submissions to support or challenge, any short text or rating attached to such support, whether your public identity should appear alongside it, and any listing you may submit yourself.
• Service integrity. To keep the board fair against automated abuse, the site processes limited technical signals from your connection and device, pseudonymised and kept only briefly. Proof-of-interaction challenges exist solely to distinguish humans from scripts.
• Payments. Acquiring credit runs entirely through our payment processor as merchant of record. Card and bank data go only to that processor under its own policies. From payment completion we record the reference, the receiving account, the amount, and the resulting allocation of credit.
• Diagnostics. Short-lived technical records may be kept to resolve faults or evidencing consent; these relate to service operation, are retained on measured schedules, and are never used for marketing.

What is public — and what remains private

The very nature of this experiment is a visible public arena. By design:

• Records of actions (supporting, challenging, or submitting a project) are public by nature and form part of the permanent fabric of the board. The identity shown on such a record appears only if you elect to show it for that action; otherwise it stands without personal attribution.
• Your balance, purchases, grants and transaction history remain private — visible exclusively within your authenticated account area and excluded from all public surfaces, listings, and search engines. Other visitors, signed in or not, gain no knowledge of their existence.
• Aggregate figures the product displays (totals, order positions) are sums of the public records above, not extracts of anyone's private data.

Handling of auxiliary records

Where auxiliary records must link an action to its source for narrow purposes — abuse handling, fulfilling lawful requests, and protecting the platform — they exist solely for those purposes, are restricted to operators, are never published, sold, shared, or used commercially, and are detached from records promptly upon request (see below). Where a request intersects an active payment dispute, we pause erasure steps until that matter concludes, because partial alteration would harm both parties equally.

Your controls

• Display of identity is always per-action and off unless you switch it on; leaving it off keeps records unattributed.
• You may ask at any time for the linkage between your account and past records to be detached — dm @_trou3 on x. Records themselves become fully anonymous in the process.
• Your purchase and usage history can be reviewed or exported privately through the documents available in your account area.
• Preference data (such as theme selection) lives only in your own browser storage.

Security posture

Proportionate technical and organisational measures protect this service. We describe our protections by purpose rather than mechanism — publishing their engineering detail would assist attackers more than users — and they evolve as abuse patterns evolve. Report suspected vulnerabilities or impersonation through the contact channel before posting publicly, so misuse cannot spread while we address it.

Changes and contact

Material updates to this policy appear here. Questions, requests, or reports: dm @_trou3 on x.