Terms, privacy, and content notice

What Algura Taro is

Algura Taro is an experimental reflective-tarot experience. It is not a source of factual prediction, diagnosis, treatment, legal, financial, emergency, or crisis advice. You remain responsible for your choices. Use qualified local support for matters that need it.

Terms and conditions (version 2026-10-28)

Experimental service. Algura Taro is a public alpha provided for experimentation. It may change, pause, or end at any time, and any feature may be unavailable. Nothing here is guaranteed to be available, correct, or uninterrupted, and no such guarantee is offered.

Accounts and eligibility. You access Algura Taro by signing in with a verified account through Clerk, our sign-in provider. You must follow Clerk's own terms, keep your credentials and one-time codes safe, and use only an identity that belongs to you. Do not share an account or attempt to access another person's account. Algura Taro stores no password and offers no homegrown sign-up; account and identity management happen at Clerk.

Your responsibilities. You are responsible for the questions you write and for how you use any reflection text. Do not submit sensitive, confidential, health, financial, or identifying information in questions or feedback. Reflections are reflective writing, not professional advice of any kind.

Acceptable use. Do not attempt to break, overload, or probe the service, exceed fair reading limits, or use automated tooling against it beyond what the operator invites. Abuse may result in access being refused.

Updates to these terms. Material changes are posted on this page with a new version and date. When the version changes, the app asks you to review the new version and accept it again through an explicit checkbox before you can keep requesting readings; merely staying signed in is not consent. Reading access pauses at a version change until you accept the current version. The update list is separate from marketing email, which is optional and off by default.

Alpha limits

The service may change, pause, or end. Do not submit sensitive, confidential, health, financial, or identifying information in feedback.

Privacy and updates

Readings. A reading requires three deliberate steps: a verified Clerk sign-in, an explicit acceptance of the current Terms and Conditions, and your own reading request — signing in alone never starts or implies a reading. When you request a reading, your question, the drawn cards, and the generated position roles are sent once, over HTTPS, to the AI service that writes the reflection text; the text is returned to you and is not stored by the app, which keeps no reading history. The question and a reference to the prepared draw survive only in your own browser tab, and are cleared after the reading or when you clear them.

Account data, draws, and limits. For accounts, the app keeps only a pseudonymous account key (a one-way hash of the Clerk issuer and your provider subject), account timestamps, your versioned terms-acceptance record, and short-lived hashed logout revocation records — never your provider password, raw subject, or account email, and never your question or the generated reading text. Clerk processes the email address and identity details you provide for authentication, including sending sign-in verification codes. A prepared card draw is bound to your browser and stays openable for a bounded window of about one hour; the app retains only its card identifiers and orientations during that window, and clearing the draw cookie does not reset your limits. AI usage limits apply per verified account, together with global attempt and concurrency caps that protect the service; they are not browser-only limits, and clearing cookies does not lift the account or global caps. No absolute anonymity, unlimited deletion, or account-level spending cap is promised.

Sign-in and consent records. Signing in is provided by Clerk, which processes your login under its own terms. The app verifies a fresh, short-lived signed session token on each protected request; it stores no provider tokens and runs no homegrown password or opaque-cookie session store. The app retains only: a pseudonymous account key (a one-way hash of the issuer and your provider subject — never the raw subject, email, profile, or password), account timestamps (created, last sign-in), your terms-acceptance evidence (the terms version and the server-recorded acceptance time for each version you accepted), and short-lived hashed session-revocation records used to honor logouts. Logging out revokes the session and clears local sign-in state; it does not delete your account or terms-acceptance record, and it does not by itself prove that every other active provider session ended. Questions, reflection texts, provider tokens, IP addresses, and user-agent strings are not retained for accounts.

If the update form is available and you opt in, Algura Taro stores your email address, consent time, and consent version solely to manage alpha updates. Feedback stores the message and its selected area. We do not ask for reading questions in either form. You can remove an email through the form on the home page. No marketing or update email is sent until a delivery service is deliberately configured; any future email will include a direct unsubscribe method. This is separate from sign-in: when you create an account or sign in, Clerk may send you verification or security codes for its own authentication flow.

For this alpha, personal data is processed to operate sign-in and sessions (technical identifiers that keep you signed in and support reading limits), to keep the terms-acceptance record described above, to carry your question and drawn cards transiently, over HTTPS, to the AI service for the reflection you request — no reading history is kept: your question and the reflection text are not stored on our server, and the drawn card identifiers and orientations of a prepared draw are held only while that draw is accessible (about one hour), after which it can no longer be opened; stored rows are later removed through bounded traffic-based cleanup and operator review, and no automatic physical-deletion scheduler is claimed — and, when you choose, to maintain the update list or review feedback. Marketing consent is optional and separate from readings; no marketing or update email is configured, so none is sent automatically — sign-in verification codes from Clerk are the exception, sent only to authenticate you. The collection forms stay unavailable until the operator verifies the removal contact and the retention operation. Planned retention: feedback is removed after about 30 days; update signups whose consent is not renewed are removed after about 90 days. A successful unsubscribe request deletes the address from the live update list. If the form is unavailable, use the operator contact shown when one is available; operator requests are handled by a person, so allow time for a response. These removals are performed by the operator on a reviewed schedule; no automated scheduler is claimed to run today. Deletion does not rewrite provider recovery history, which the operator handles separately. A final production privacy program, data-residency decision, and retention schedule are not part of this alpha.

Content and rights

This alpha uses the Algura Taro 78-card deck — card texts and card images used with permission. The images are served from this site's own origin. The reflection prompts are bounded reflective instructions; they do not produce factual predictions. The preview is not an endorsement of any third-party deck, publisher, or reader.

Contact and changes

Material changes to these terms or this privacy notice will be posted here with an updated date. Do not rely on this alpha for urgent help.