From date input to a displayed reading
- The browser validates the date and calculates the number and matrix.
- Submitting with consent sends the date and language to this server in a POST request.
- The server validates the date again and sends the calculated number and digit counts to OpenAI.
- The generated text is returned to the browser for display.
What the application keeps
| Information | Purpose | Application storage |
|---|---|---|
| Birth date | Validation and calculation | Not saved to a result file or database |
| Generated reading | Display for this request | No stored result or result cache |
| Hashed IP identifier and counters | Limit excessive requests | Used in short-lived quota records |
| Access and page-performance records | Delivery and Cloudflare Web Analytics | Handled by the server and CDN services |
The request identifier is a hash derived from an IP address. It is treated as an access-control record, not as a guarantee of complete anonymity.
URLs and reading history
- The date is not placed in a URL query string.
- No individual result page or sharing URL is created.
- There is no reading-history retrieval feature.
- Browser autofill and device-side storage follow your own settings.
Ordinary access records may include an IP address, time and requested path. Cloudflare Web Analytics collects page-view and loading-performance information.
OpenAI’s handling of the request
The API receives the calculated number and digit frequencies rather than the date itself. Requests use store=false, which does not eliminate all provider-side retention, including possible abuse-monitoring records. Consult OpenAI’s official data controls for the applicable conditions.