Rowsmith: Data Notice (free phase)
Version 2026-10-18 (v0.2).

Who: meiorz runs this service. Contact for questions or deletion requests: business@meiorz.tech.

What the service keeps, per request: the time, the endpoint, a caller key, the number of rows, the response
status, whether a limit applied, the request's cost units, and the response time. The caller key is a keyed hash
of your network address (for IPv6, of its /64 prefix); the service never stores or logs the address itself.
The key that makes the hash is destroyed at the end of this free phase, and in any case no later than 90 days
after launch; after that, stored caller keys cannot be linked to anyone. If the phase runs past 90 days, a new
key is created and the old one destroyed, and repeat counts restart.
The operator sees aggregate counts per caller key; those keys fall under the same rule, so once the key that makes
the hash is destroyed they cannot be linked to anyone.
Daily counters per caller key are deleted on the first request of the following day (UTC).
Usage totals: per day, the number of calls, of refused calls and of distinct caller keys, and the calls per
endpoint and per tool. They hold no caller key and no address, and are deleted after 90 days. To limit requests to
the operator's statistics page, a per-minute request count per caller key is kept for at most one minute.

Payment sandbox: when you use it, the service stores the fake payment objects you create, so that later calls
in the same test session can read and refund them. For each charge: its id, amount, amount refunded, currency,
status, whether it was paid and whether it was fully refunded, the failure code, decline code and failure message
(fixed texts set by the service), the card brand and the last four digits of the test card number, its refund ids,
a logical creation time, the markers livemode, sandbox and test_data, and two optional fields you send: a reference
and up to 10 metadata entries. For each refund: its id, amount, currency, status, the charge it belongs to, the
optional reference, a logical creation time and the same markers. For the sandbox: its seed, version, expiry time
and two counters. The reference and the metadata keys and values may only hold 1 to 40 letters, digits, _ or -,
never 8 or more digits in a row; the sandbox accepts no other text from you. The card field accepts only
card numbers from Stripe's published testing list, of which it keeps the brand and last four digits. These are stored in
Cloudflare Durable Objects under a random sandbox id, and hold no caller key and no address. Everything in a
sandbox is deleted 1 hour after the sandbox was created (a reset deletes it earlier); nothing from it is kept after
that. Card-like numbers that are not on the published testing list are never stored or logged; requests
containing them are refused where the service detects them.

What it does not keep: the schema you send is used to answer the request and is not stored. Apart from the
sandbox objects above, nothing you send is stored.

Messages to the contact address are handled through the operator's mail provider under that provider's policy.

Processors: the service runs on Cloudflare Workers. Cloudflare processes network-level data, including your
address, under its own privacy policy (cloudflare.com/privacypolicy), outside the operator's control. The
service's own logs are kept for 3 days.

No sale, no advertising, no tracking cookies.