Privacy policy
Exactly what the hosted connector stores, where your application password sits, and what leaves for Polar.
The short version: we store what a connector needs and nothing else. Your application password is encrypted with a key that is not in the database. The audit log records that a change happened, never the content of the change. Page views are counted without cookies, and nothing here tracks you across the web.
What we store
Your identity. Sign-in is handled by Clerk: your account identifier, and the email address and name you signed in with. We read the identifier; the account record itself lives with Clerk.
Each site you register. The site URL, the WordPress username, and the application password for that user.
The application password, encrypted. Each site gets its own AES-256-GCM data key, and that key is wrapped by a key that lives only in the server's environment — never in the database, and never with the stored row. Encryption is bound to your account and that site, so a row lifted into another account's table will not decrypt. A database compromise yields ciphertext; an environment compromise yields a key with no data to use it on. The plaintext password exists only inside the function that is serving a request, and never enters an assistant's context.
An audit log of changes, without bodies. Every write an assistant makes is recorded: which site, which tool, when, and a handle to restore it. Not the post content, not the media, not the credential. It is kept for 90 days.
Page-view events, with no cookies. We count what is read here first-party: the page, the
referrer, the landing page, UTM parameters if a link carried any, a device class, and a country
derived from the request. The session identifier lives in your browser's sessionStorage and
is gone when the tab closes. There is no cookie, no third-party analytics, no ad pixel, and
nothing that follows you to another site.
Your plan. Which plan you are on, the billing status, the current period, the Polar customer and subscription identifiers, and how many of the free actions each site has used.
What we do not store
- No card numbers and no billing address — Polar holds those.
- No content from your WordPress site. Posts, media and comments are read, passed to your assistant and not retained.
- No tracking cookies and no cross-site identifiers.
- Nothing is sold or shared with anyone for their own purposes.
What goes to Polar
When you start a checkout we send Polar the plan and interval you chose, and an identifier for your wpreef account so the subscription can be matched back to it. You give Polar your email and payment details directly. Polar sends back the subscription status, the product, the period and the order identifier, which is what sets your plan here.
Who processes data for us
| Service | What it sees |
|---|---|
| Vercel | Hosting. Standard server logs — addresses and request paths — exist transiently at the infrastructure level. |
| Convex | The database: sites, the encrypted credentials, the audit log, events and plan records. |
| Clerk | Authentication, for this dashboard and for the connector's OAuth sign-in. |
| Polar | Merchant of record. Payment and billing details, under its own privacy policy. |
| Resend | Sends the few transactional emails we send, such as a plan becoming active. |
Your WordPress site is not a processor: it is yours, and wpreef is the thing talking to it.
We email you when a plan becomes active and when a plan is downgraded or revoked. Polar sends the receipts. We do not run a marketing list, and buying a plan does not put you on one.
How long we keep it
Sites and their credentials live until you remove the site or delete your account. The audit log is kept for 90 days. Event data is kept for product analytics and shrinks to aggregates over time. Billing records are kept as long as the law requires them.
Removing a site deletes its stored credential here. It does not revoke the application password on WordPress — only you can do that, at Users → Profile → Application Passwords.
Your rights
Ask us and we will tell you what we hold about you, correct it, or delete it. We answer within 30 days, usually much faster. If you are in the EU or UK these are your GDPR rights and they work exactly this way.
Account and data requests reach us by replying to the receipt Polar sent you, or through an issue on the project repository if you have no receipt yet.
Children
wpreef is developer tooling and is not directed at children under 16. We do not knowingly collect their data.
Changes
If what we store changes, this page changes first and the date at the top moves. See also the terms of service.