Privacy policy
The short version: this website has no accounts, no login and no advertising trackers, and subscriptions are handled by npayload rather than by us. The longest section below is about the public figures we observe, because that is the one place where our work touches information about identifiable people.
1. The short version
This site does not ask you to create an account, does not set advertising or cross site tracking cookies, and does not sell data about you to anyone.
Your subscription, key and billing live with npayload. We see which subscription consumed how much, not your payment details.
One preference is stored in your own browser: your choice of dark or light theme. It never leaves your device.
2. What this website stores on your device
A single entry in local storage, wf-theme, holding dark or light when you pick a theme explicitly. It is not an identifier, it is not sent anywhere, and if you never touch the theme control nothing is written at all.
No advertising cookies, no cross site trackers, no session identifiers, no fingerprinting.
3. Server logs
This site is served from Cloudflare’s edge. Standard request logs, which can include IP address, user agent, requested path and timestamp, are processed to deliver the site, keep it available, and defend it against abuse. That is a legitimate interest in operating a public website securely.
We do not build profiles from these logs and do not use them for advertising.
4. Subscriber data
Access to the feed is issued and metered by npayload. Account creation, authentication, payment and invoicing happen there, under npayload’s privacy policy, and we do not receive or store your card details.
We do process operational records tied to a subscription: which subscription consumed which events, volumes, rate limit events, and support correspondence if you contact us. We use these to run the service, enforce tier limits, bill correctly and answer you.
5. Public figures in the analysis, and why this section is the important one
Our product observes public statements about event contracts. Where a statement came from a named public account, our events can reference that account handle, a public URL, a timestamp, and our own scores for relevance, novelty and stance. In some jurisdictions that constitutes processing personal data about the person behind the account.
We keep this deliberately narrow:
- We watch a curated list of accounts speaking publicly in their capacity as candidates, office holders, agencies or commentators. We do not monitor private individuals.
- We store what we observed and our scores. We do not redistribute post text at scale as a product.
- We do not attempt to identify anyone behind a pseudonymous account, and we do not enrich, combine or resolve identities.
- We publish a stance relative to a contract’s resolution criteria. We deliberately do not compute or publish any sentiment, personality or behavioural score about a person.
- Our lawful basis is legitimate interest in producing financial and event analysis from public statements, balanced against the narrow scope above.
6. Retention
Our archive is append only by design, because a data vendor whose history can be quietly rewritten is worthless. Observations and emitted events are retained indefinitely as the historical record, with corrections stored as new versions rather than overwrites.
Support correspondence is kept while it is useful and then deleted. Operational subscription records are kept for as long as needed to run and account for the service.
7. Sharing
We use a small number of processors to run the service: Cloudflare for hosting and edge delivery, npayload for subscription, metering and delivery, and the source APIs we read from.
We do not sell personal data, and we do not share it for advertising.
8. Your rights
Depending on where you live you may have rights to access, correct, delete, restrict or object to processing of your personal data, and to data portability.
For anything held about a subscription, contact us and we will help; where the data lives with npayload we will point you to the right place. For a request concerning a public account referenced in our analysis, write to us and we will assess it against the archive integrity interest described in the retention section, and respond either way.
Requests go to privacy@wickfeed.com.
9. International transfers
Our infrastructure runs on a global edge network, so data may be processed outside your country. Where transfers are restricted we rely on the appropriate safeguards offered by our processors.
10. Children
This is a service for developers and institutions. It is not directed at children and we do not knowingly collect data from them.
11. Changes and contact
If we change this policy materially we will update the date above and give notice before the change takes effect.
Questions can be sent to privacy@wickfeed.com.