Your input stays local.
A model number or shared retailer link is normalized and matched on the device. The raw retailer link is not sent to Wasitever, Cloudflare, or the retailer.
Privacy
A record request without an app account.
This policy explains the Wasitever iPhone app first, then the separate website and account services. It is effective .
- App account
- Not required
- Advertising
- None
- Cross-app tracking
- None
- Reader cookies
- Not stored
iPhone app
What leaves the device
The app has no advertising SDK, analytics SDK, account identifier, advertising identifier, contacts access, location permission, photo access, or background tracker.
Static Wasitever data only.
When live data is enabled, the app makes foreground GET requests to wasitever.com for a current pointer and content-addressed Wasitever objects. It sends no request body, app account, advertising identifier, or retailer credential.
Cloudflare serves the files.
Cloudflare necessarily receives the source IP address, requested Wasitever path, and ordinary connection metadata to route, secure, and answer the request. The app uses an ephemeral session with cookies and the URL cache disabled.
Retention
Provider records and Wasitever controls.
Wasitever does not enable its customer-facing stored Worker request logs, traces, Tail Workers, Logpush, or R2 Data Access Logs for the Reader. Those settings do not disable Cloudflare's own platform and security processing.
- R2 operations
- 31 days
- Worker metrics
- Up to 3 months
- Zone analytics
- 30 days
- App cache
- Memory only
- Wasitever customer logs
- Off
R2 operational metrics include the operation, status, bucket, object name, response status, and time. An object name is a content-addressed Wasitever path and can indicate which published object was requested.
Aggregate Worker metrics include request counts, success or error status, invocation status, duration, and runtime resource measurements. Cloudflare may also derive coarse country-level traffic and security metrics from connection data.
Cloudflare separately processes End User IP addresses, traffic-routing data, system-configuration information, and other traffic metadata. It maintains limited-period network-event logs and collects or derives Network Data such as request volumes, error rates, availability, and IP threat scores. Cloudflare's public policy does not give one universal retention period for those records. See Cloudflare's Privacy Policy and GDPR FAQ.
The app keeps verified Reader data only in bounded memory. It does not write Reader history, input, cookies, or responses to app storage.
App Store disclosure
We disclose the retained service facts.
Wasitever treats the retained request, object, and network records as Usage Data (Product Interaction and Other Usage Data), Device ID, Diagnostics (Performance Data and Other Diagnostic Data), Coarse Location, and Other Data (Other Data Types).
Purpose and linkage
Conservative linkage, no tracking.
The App Store disclosure marks all seven data types as linked because Cloudflare receives an IP address and does not promise de-identification before collection. Their purposes are App Functionality and Analytics: delivering, securing, maintaining, measuring, and troubleshooting the Reader. Wasitever does not use them for advertising or tracking across apps or websites.
Website and account service
The website is a separate surface.
Opening this policy or another public Wasitever page does not use the app's Reader session.
- Cloudflare Web Analytics measures aggregate page views, paths, referrers, and performance without an analytics cookie. Google Analytics 4 runs through Cloudflare Zaraz from Cloudflare's edge; Google processes those site events for Wasitever.
- Cloudflare may set strictly necessary security cookies, including its bot-management cookie. Those cookies protect the website and do not enter Wasitever's verdict or ranking systems.
- Reading public records requires no account. If you choose to manage a watch, the account service uses a session cookie and the email address you provide or confirm through a sign-in provider. Watch and sign-in data are used to provide that service.
- Wasitever does not sell personal information. It runs no session recorder or heatmap, and alert emails carry no tracking pixel.
Your choices
The app creates no account or local history.
You can stop Reader requests by closing or removing the app. The app keeps verified Reader data in memory and does not create an app profile. Cloudflare still processes the network records described above; contact Wasitever for a verifiable rights request and we will respond or coordinate with the provider as required.
Watches and sign-in
Account controls stay with the account service.
You can manage active watches and the signed-in session at watch.wasitever.com/account/. Contact us if you need help with account data or a privacy request.
Contact
Questions or requests
Was It Ever, LLC operates Wasitever. Email alerts@wasitever.com with “Privacy” in the subject line. We may update this policy when the app, providers, or retention practices change; the effective date above will move with the change.