PRIVACY

Minimal data by design.

Before launch: add the operator identity and privacy contact required for your business.

What BRIK stores

• A random first-party visitor token used to limit votes, reactions and Free BRIKs.
• HMAC-hashed IP address and user-agent values for abuse prevention and security logs. Raw IP addresses are not intentionally stored in the application database.
• Branding content you submit: name, URL, optional social profiles, chosen color and sanitized logo.
• Stripe identifiers needed to reconcile a payment, such as Checkout Session and PaymentIntent IDs. Card data is handled by Stripe and is not stored by BRIK.
• Private dislike/feedback messages submitted through the feedback modal.

Uploaded images

Accepted images are decoded, resized and re-encoded as AVIF. The original upload is discarded. This removes original image metadata such as EXIF from the stored copy.

Public information

Paid BRIK branding and game results are designed to be public. Private dislike text is visible only in the administration panel.

Analytics

The V1 contains no third-party analytics, advertising pixels, social tracking SDKs or external font services.

Retention

Historical tower and purchase records are part of the permanent project record unless removal is legally required. Short-lived security/rate-limit data can be cleaned automatically. Abandoned uploaded logos are deleted when reservations expire.

Your rights

Contact [PRIVACY EMAIL — REPLACE BEFORE LAUNCH] for privacy requests. Applicable legal rights depend on your jurisdiction.