Privacy policy

You use Portreeve directly — you browse this site, join the early-access list, or run a Portreeve account and dashboard. For that data, we decide how and why it is processed (we are the “data controller”), and this whole policy applies to you.

A service you used sent us your data — you signed up for, or paid, one of our customers, and their systems asked us to screen the event. For that data we are a service provider (a “data processor”): we act only on our customer’s instructions, and that customer is responsible for telling you about it and for handling your privacy requests. Sections 04–06 describe exactly what we do with it. If this is you, contact the service you used first; if you contact us instead, we will help route the request to them and assist with it.

• Account details — your name and email address, when you create a dashboard account. Sign-in (Google or email and password) is handled by our authentication provider, WorkOS; if you use a password, it is held by WorkOS and never stored by us.
• Billing details — if you buy a paid plan, payment is handled by Stripe. We receive your plan, invoice status, and card brand/last-four for display; full card numbers never touch our systems.
• Early-access list — the email address you submit on this site, used only to contact you about Portreeve. One-click removal any time.
• Support — whatever you send us by email, kept as correspondence.
• Operational logs — requests, errors, and timing data needed to run and debug the service.

This site uses three measurement tools: PostHog, for page views and clicks on the marketing site; Google Ads conversion measurement; and the ChatGPT Ads pixel from OpenAI. The two ad tags exist to tell us whether an ad click led to a signup, and set a first-party cookie for up to 30 days to do it. In the EEA, UK and Switzerland the Google tag runs without cookies unless you consent. The dashboard sets a session cookie so you stay signed in. There is no other tracking, and nothing is ever sold to advertisers.

When you choose “Sign in with Google”, we receive your name, email address, and profile picture from your Google account — nothing else. We use them solely to create your Portreeve account, sign you in, and identify you inside the dashboard. We do not use Google user data for advertising, do not sell it, and share it only with the subprocessors that operate sign-in and hosting for us (section 07).

Portreeve’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. You can revoke Portreeve’s access at any time at myaccount.google.com/permissions, and you can ask us to delete the associated account data (section 08).

To produce a verdict, a customer’s systems send us event metadata about an action on their service: email address, IP address, user agent, device signals, identity hints the customer chooses to send (a phone number, for example), and payment metadata from their payment processor — a card fingerprint and funding type, never card numbers, never CVV. We cannot charge cards and never see enough of one to try.

We process this data solely to produce abuse verdicts and the dashboard, analytics, and notifications around them, on the instructions of the customer who sent it. We never use it to contact anyone, never build advertising or marketing profiles from it, and never sell it.

Raw event payloads — the parts containing personal data like emails and IPs — are kept for 90 days, then irreversibly scrubbed: identifying values are replaced with one-way hashes. The identity keys used to link repeat abusers are stored in normalized, hashed form from day one. A hash lets us recognise “this same email again”; it cannot be reversed to recover the email itself.

Abusers hit many small products with the same devices, cards, and identities, so hashed identity keys and their abuse status may be used in aggregate to inform abuse signals across Portreeve customers — a device hash confirmed abusive on one service can raise the risk score of that same hash elsewhere. No readable data — no email addresses, no IPs, no names, and nothing about any customer’s business or traffic — is ever shared between customers; only one-way hashes and their abuse status. Customers can opt their traffic out of cross-customer signals at any time, with no change to their service.

We use a small set of service providers to run Portreeve. Each receives only what its job requires:

• Cloudflare — site & network edge; web traffic to our domains.
• Railway — application hosting & databases; the service data described above.
• WorkOS — dashboard sign-in; account name, email, sign-in method.
• Stripe — billing; billing details and payment method.
• Resend — transactional email; email addresses we send mail to.
• ProxyCheck.io — IP intelligence; event IP addresses only, for VPN/proxy lookups.
• Google — ads conversion measurement; ad-click identifiers and page visits on portreeve.com, plus the moment a workspace is created.
• PostHog — product analytics on the marketing site; page views and clicks.
• OpenAI — ChatGPT Ads conversion measurement; ad-click identifiers and the moment a workspace is created.

Beyond that: we disclose data only if the law genuinely requires it (and we tell the affected customer unless legally barred), or as part of a merger or acquisition, in which case this policy continues to apply to the data. There is no other list. No data brokers, no ad networks.

• Raw event payloads: 90 days, then irreversibly hashed (section 05).
• Hashed identity keys: kept while they are useful for abuse detection; deleted on the sending customer’s request, including from cross-customer aggregates.
• Your account data: kept while your account exists; deleted within 30 days of a deletion request.
• Early-access emails: kept until we’ve contacted you or you ask to be removed, whichever comes first.
• Invoices and billing records: kept as long as tax and accounting law requires.

All traffic is encrypted in transit (TLS). API keys are stored only as one-way hashes — a secret key is shown once at creation and cannot be retrieved afterwards, by you or by us. Access to production systems is limited to what operating the service requires. If you believe you’ve found a security issue, email admin@portreeve.com and it will be read the same day.

You can ask us for a copy of the personal data we hold about you, ask us to correct or delete it, or object to how it’s used — email admin@portreeve.com from the address in question and we’ll act on it within 30 days. If you’re an end user of one of our customers, we’ll route the request to them and assist (section 01). Depending on where you live, you may also have the right to complain to your local data-protection authority.

• Where data lives: our infrastructure runs primarily in the United States; using the service means your data is processed there.
• Children: Portreeve is a business tool and is not directed at children under 16; we don’t knowingly collect their data.
• Changes: updates are posted here with a new effective date; material changes are emailed to account holders before they take effect.
• Contact: admin@portreeve.com — you’re writing to the person who runs the service, not a queue.