Privacy
Updated 15 November 2026
This page describes how Kledacta works. It was written by the people who build Kledacta and has not been reviewed by a lawyer.
Kledacta keeps registered results, the readings practitioners sign for them and the access people grant, for the people they belong to. This page covers this site, kledacta.com, and the application at app.kledacta.com.
In short
- Kledacta never receives the question or intention a client brings to a reading.
- There are no advertising or analytics trackers, and no data is sold.
- A client decides which practitioner can read a result, and can end that access at any time.
- You can delete a record or your whole account from inside the application.
What the application stores
When you use the application, Kledacta stores:
- Your account and sign-in identity. Clerk runs sign-in and holds your email address and sign-in details. Kledacta keeps an account identifier and the link to your Clerk identity.
- Invitations and admissions. An invitation is kept with its role, dates and status, and with a digest of the invited email address instead of the address itself. When you accept it, Kledacta checks that one of your verified addresses matches that digest and records your admission as a client or as a practitioner.
- A practitioner’s profile: the display name the practitioner chooses.
- Registered results. When Moiriom, the origin application, registers a result, Kledacta keeps the result’s code, the origin’s reference to it, the time Kledacta registered it, and the seal evidence: the origin’s signed receipt, its key, a digest of the result and the time the origin says it sealed the result. It also keeps the snapshot of the result’s facts and the text the origin supplies to describe it. For Moiriom, the snapshot holds the code, the creation time, the source of the number, the cards and moves drawn and the versions used. It never holds a question or the lens a person read through.
- Associations and consents. Which results belong to your record, when they were added and whether you archived them; and your standing consent for an origin application to add results to your record, with the version of the consent text and a digest of it.
- Practitioner sessions. The sessions a practitioner opens, the links and QR codes issued to start a kledon, kept only as digests, and the result a session is bound to.
- Access grants. Which practitioner you allowed to read a result for a session, what they may do, when you agreed, a digest of the text you agreed to, and when the access ended.
- Private drafts. A practitioner’s unsigned draft for a session. Only that practitioner can see it.
- Signed readings and corrections. The text a practitioner signed, the name shown with it, the time and the version. A correction is a new signed version; the earlier version stays.
- Deletion records. Which deletion was asked for and when, so that it is carried out and not undone.
- Operation receipts. For each change, a short receipt with identifiers, digests and times, so that a repeated request is not applied twice. Receipts hold no reading text and no question.
What the forms on this site collect
- Get started: your work email, which describes you, your practice or product name, your divination system or use case, the possible results and expected use, an optional implementation note, the page language and the time it arrived.
- Contact: the topic, an optional reply address, your message, the page language and the time it arrived.
We use these only to answer you and, for Get started, to decide on an invitation. They are not added to an account or to a mailing list. Each form also has a hidden field that people leave empty; it is checked and discarded.
To stop automated sending, this site counts recent submissions per IP address in memory and passes the server a keyed digest of the address, never the address itself. Neither is stored with your submission.
Do not send a question you brought to a reading, a reading, health information or other sensitive personal content through either form.
What Kledacta does not collect or do
- The question or intention a client brings to a reading. No field asks for it, and origin applications do not send it.
- Advertising or analytics trackers, or cookies from advertisers.
- Selling data, or sharing it for advertising.
- Writing, checking or rating readings. Practitioners write them.
- Writing what you type into the forms, or the text of readings, to its logs.
Cookies and browser storage
This site sets no cookies and stores nothing in your browser. Its fonts, scripts and images are served from this site.
The application uses the session cookies Clerk sets on the application’s domain to keep you signed in; it cannot work without them. If you choose a language in Settings, the application stores that one preference in your browser’s local storage.
Where it runs
Kledacta runs on these providers. Each handles data under its own terms:
- Cloudflare serves this site and the application, and passes the application’s requests to its server. Like any network, it handles technical data such as your IP address to deliver each request.
- Railway runs the application server.
- Supabase hosts the database, in the United States.
- Clerk runs sign-in and holds your email address and sign-in details.
Your data may be processed in the United States and in other countries where these providers operate.
Moiriom is a separate site with its own privacy page. It sends a result to Kledacta only when a practitioner’s session started the ritual, when you start it from your Kledacta record, or when you ask to keep the result.
How long data is kept
- Your record, meaning the results you keep, the readings signed for them and what is needed to show where they came from: until you delete the record or your account.
- A registered result that nobody adds to a record: removed 30 days after registration, together with the session and the readings made for it. A link to keep it stops working at the same time.
- A practitioner’s sessions: kept until the practitioner deletes their account, or until the result a session belongs to is deleted or removed. A session with a signed reading stays with its result even after the practitioner’s account is deleted.
- An unsigned draft: removed after 30 days without a change.
- An invitation: the digest of the invited address is removed within a day after the invitation is accepted, withdrawn or expired, and the rest of the invitation 90 days later.
- An admission that was removed, a consent you withdrew and an access grant that ended: removed 90 days later. A withdrawn consent stays for as long as you keep a result that was added under it.
- Operation receipts: removed after 90 days.
- A deletion you ask for: access ends at once, and the deletion is finished within 7 days.
- After a deletion: the deletion record, and the evidence that a deleted result was sealed (its code, the origin’s reference to it, the origin’s signed receipt and the digest, with no link to you), are removed 90 days after the deletion was accepted.
- Backups: deleted data can remain in the database provider’s backups for up to 30 days, until those backups expire. If a backup is ever restored, deletions are applied again before any data is used.
- Form submissions: deleted 180 days after they arrive, or sooner once handled.
Deleting and ending access
Inside the application you can delete a single record or your whole account. Deleting a record removes Kledacta’s copy of the result, its link to your account, the readings signed for it and the access you granted for it. Deleting your account removes all of your records, your profile and admissions, and your sign-in identity at Clerk.
Some things stay. The original result stays with the origin application, under that application’s own terms: Kledacta’s deletion does not delete it there. What a practitioner has already read or copied cannot be called back. The deletion record, the evidence that a deleted result was sealed and operation receipts stay for 90 days, and backups for up to 30 days, as above.
If a practitioner deletes their account, the readings they already signed stay in their clients’ records without the practitioner’s name.
To end a practitioner’s access, open the result in the application and revoke the access. From then on the practitioner cannot read the result. Readings they already signed stay in your record.
For anything else, such as a copy of your data or a correction, write to us through the contact form and choose Privacy. Do not include sensitive personal content in the message.
Changes to this page
When this page changes, the new version is posted here with its date.