Your request and your privacy.

WorldHinge is a physical-world request service operated by Ryan O’Shea, Future Grind, LLC. Contact ryan@futuregrind.org for support or deletion requests. Do not email access tokens or passwords.

What we store and why

We store the need and scope you submit, optional principal/contact details, consent choices, conversation, status, and private operator notes to evaluate and respond to your request. Contact details are optional. A submitted address does not subscribe you to marketing or automatic email notifications.

Request credentials are hashed in storage. Your browser stores your request credentials and pending submissions so you can return. Anyone using that browser profile or holding your access file can read and delete that request. Founder keys and unsent founder replies use tab session storage. Use a trusted device.

Processing and access

Cloudflare hosts the application and its persistent database. Ryan reviews requests and may reply in the saved conversation. This release makes no AI/model calls, performs no automatic research, and sends no automatic emails. Request text is never executed as instructions. We do not sell request details, publish raw submissions, or train models on them.

There are no third-party analytics, tracking pixels, or remote fonts. Cloudflare processes network information to provide hosting and security. Our application stores temporary keyed hashes of peer addresses for abuse limits, rather than raw IP addresses. It does not log request bodies, authorization headers, or transcripts. Cloudflare's own operational records are governed by its policies.

Retention and deletion

Requests expire 90 days after creation; returning does not extend retention. Expired records are inaccessible and purged by the daily storage alarm and when the service is used. Use the request's privacy controls or authenticated DELETE endpoint to remove active records sooner. Linked conversation, operator notes, and audit events are removed. Non-content creation fingerprints remain until the original expiry to prevent a deleted request being accidentally recreated by a retry. Temporary abuse counters expire within about a day.

Cloudflare's database recovery history may retain previous versions for up to 30 days, including deleted data. Deletion is immediate in the active database, not instant erasure from that recovery history. Recovery access is restricted to the operator; a restore requires reapplying newer deletions and token revocations, and purging expired records before reopening requester access. No raw request backups are downloaded automatically.

If you lose your credential, contact the operator. There is no automatic public recovery flow, and identity/ownership must be established before any disclosure or deletion performed on your behalf. Avoid sending confidential details in email.

Service statistics

Internal inbox totals help us manage requests and understand the types of inquiries received. We do not publish request text or contact details.

The API also offers a separate, optional setting for inclusion in private category-level statistics exports. It is off by default, and the website form does not opt you in. These exports contain counts only, exclude test requests and spam, and omit groups smaller than five. Any public release requires a separate privacy review.

What to leave out

Do not submit passwords, payment information, sensitive personal data, private recordings, confidential employer/client material, or anything you lack permission to disclose. No files are accepted. Questions or concerns: Ryan O’Shea, Future Grind, LLC. Contact ryan@futuregrind.org for support or deletion requests. Do not email access tokens or passwords.