Privacy Policy

1. What we collect at the corporate layer

The corporate layer is the data Weird Network holds about provider accounts (the venue operators using our service), billing, and aggregate metrics. We hold this because we need it to run the service — not because we want to.

Provider accounts

If you sign up as a provider (venue operator), we collect:

• Email address — used for login, important service notifications, and the magic-link / password-reset flow.
• Password — stored as a scrypt hash. We do not store plain-text passwords. We cannot recover your password — only reset it.
• Business name and location — displayed in your venue's captive portal branding.
• PayPal or bank payout information — stored only as needed to pay you out for revenue you've earned; never used for any other purpose.
• Email verification and password-reset tokens — single-use, short-lived, hashed in storage.

Billing

For paid subscriptions:

• We store your Stripe customer ID and subscription ID (so we know what plan you're on and when it renews).
• Your payment instrument (card, etc.) is held entirely by Stripe. We do not see, store, or transmit your card number. Stripe's privacy practices apply to that data.
• We keep a log of webhook events from Stripe so we can reconcile subscription state idempotently.

Anonymized aggregate metrics

To understand how the service is being used (and where to invest next), we collect page-view metadata on our public and provider-facing pages:

• Page path (e.g. /, /pricing).
• Referrer header.
• User-Agent string.
• The visitor's IP address, hashed with SHA-256 before storage. The hash is one-way; we cannot recover the original IP from it. We do this so the same visitor across requests can be aggregated without storing identifying information.

We do not set cookies for page-view tracking. We do not use third-party advertising cookies or any cross-site identifiers.

2. What end-user (guest) data looks like — the forward-only architecture

This is the part that makes Weird Network's privacy posture unusual. Most guest-WiFi vendors ask the venue to send guest data to their cloud, where they hold it indefinitely and use it however they like. We're built the opposite way: guest data captured at your captive portal is forwarded to you (the venue) — typically by email — and we don't retain it beyond the time it takes to route it.

What we hold about a guest session

For each WiFi session at a venue, we hold only the minimum telemetry needed to operate the service and to bill / report usage to the venue:

• MAC address of the connecting device.
• Session start and end timestamps.
• Byte counts (in / out).
• Authentication method (form capture, social gate, voucher code).
• Session status (active / ended / terminated).

We do not typically hold guest name, email, phone number, or sign-in form content — those fields, if the venue chooses to capture them, are captured by the venue and forwarded to the venue by email. The venue is the data controller for that data; we act only as a transient routing processor.

Why this matters

Because we do not retain end-user personal information at scale, there is no large guest database sitting in our infrastructure waiting to be breached, subpoenaed, or repurposed. The venue owns the relationship with its guests; we provide the software that makes the relationship work.

If you (a guest) want your data changed or deleted, you should contact the venue directly — they hold it. We're happy to help you figure out which venue to contact if it's not obvious.

3. Cookies, sessions, and analytics

Cookies

We use two categories of cookies, and no third-party advertising cookies:

• Provider session cookie — if you're logged into the provider dashboard, we set an httpOnly session cookie (stored hashed server-side in the provider_sessions table; the cookie itself is opaque and unreadable to JavaScript). This is necessary for you to stay signed in.
• Functionally required load-balancer / CSRF cookies — set automatically by our hosting environment for request routing and CSRF protection. They carry no personal information.

We do not use Google Analytics, Facebook Pixel, Hotjar, Mixpanel, Segment, or any other third-party tracking or advertising script.

Sessions

Provider sessions are time-limited (rolling expiration) and tied to a single device fingerprint. You can end your session at any time via the “Sign out” link in the provider dashboard.

Analytics

Our analytics is the page-view log described in Section 1 — hashed IP, no cookies, no cross-site identifiers. We use it to count unique visitors per page and to spot traffic anomalies. We do not use it to build advertising profiles. We do not sell or share it.

4. Third-party processors

We use a small number of third-party processors to run the service. Each one receives only the minimum data it needs to perform its function:

• Stripe — payment processing for subscriptions. Receives your payment instrument directly; receives your email and plan from us to reconcile the subscription.
• Transactional email vendor (Postmark, via Polsia email proxy) — delivers notification emails you ask us to send (magic links, password resets, alerts, digests). Receives your email address and the message contents.
• Neon — hosts our PostgreSQL database. Receives encrypted-at-rest database contents; this is infrastructure-level access, not application-level data sharing.
• Render — hosts the application process. Infrastructure-level access only.
• Cloudflare R2 — optional file storage (e.g. beta-test screenshots). Receives only the files you or a provider explicitly choose to upload.

None of these processors are used for advertising. We do not pass guest end-user data to any third party.

5. Your rights

You have different rights depending on whose data you're asking about.

If you're a guest whose data was captured at a venue's WiFi

Two layers of data are involved. First, the venue is the data controller for whatever you signed up with (your name, email, phone, etc.) — send your access, correction, or deletion request to the venue directly and they will handle it. Second, for what we hold — WiFi session metadata like device fingerprint, duration, byte counts — use our data-deletion form and we'll delete it immediately. That page also routes you back to the venue whose WiFi you used so you can ask them about the rest.

If you're a provider (venue operator)

• Access: Your provider account data is visible at any time in the provider dashboard — profile, billing status, venues, sessions.
• Export: You can export your venues, members, session records, and earnings history via the dashboard. The data is yours.
• Deletion: You can request closure and deletion of your provider account via the contact channel below. We will confirm and execute within a reasonable window. A formal self-serve deletion endpoint is on the roadmap; until it ships, please email us and we will action it manually.

Aggregated metrics we hold

Because our metrics are anonymized (SHA-256 hashed IP, no user identifier), they cannot be linked back to you as an individual. They are not subject to access or deletion requests in the same way account data is.

6. Contact

Questions about this policy, requests about your data, or concerns about how a venue has handled your information:

• Email: weird-network@polsia.app

We read every message. For provider-account data requests, please include the email address on the account so we can verify identity before acting.