What data may be stored
Question, selected method, cards or symbols, result, payment status, delivery email, technical identifiers, error logs, support notes, and minimal accounting records.
OmenHall
Answer
☰
Navigation
Menu level
OmenHall sections
Get an answerStart with your questionHallsChoose a traditionFormats & pricingFrom a short sign to a deep readingMembershipFor those who return regularlyGift OmenHallgift a private question without sharing someone else's dataAccountanswers, worlds, purchases, and settingsHow it worksprocess, trust, and librarySearch OmenHallfind a method, card, or reference
Reviewed 2026-08-17
private questions
Privacy policy
How OmenHall handles questions, readings, emails, archive records, payments, and deletion requests.
plain summary
Reading links and personal questions are private. We store what is needed for service operation, payment, delivery, support, safety, and accounting history.
important notice
Questions, readings, and personal archive links may contain sensitive context. Do not enter data you are unwilling to store in a digital service, and use the available privacy controls.
Private links
A reading access link may reveal a personal question and answer. Do not publish it. After first open, the service may use a cookie to remove the secret key from the URL.
Gift and invitation attribution
If you open an ordinary share link or hall invitation, OmenHall may keep first-party technical attribution for up to 30 days: source, campaign, and click time, then associate it with the account and first purchase after registration. This attribution does not contain private question or scroll text, is available only as an administrative marketing summary, and does not by itself promise the sender a reward.
Payment data
Payments are processed by Stripe. OmenHall should not store full card numbers. We may store Stripe ids, amount, status, product, date, and data needed for support and refunds.
Emails
Resend may be used for magic links, paid receipts, reading-ready messages, lost links, refunds, privacy confirmations, and service updates. Emails should contain minimal private detail.
Deletion and retention
A user may request deletion of personal content. Some payment, accounting, security, and dispute records may be retained in minimal form when needed for legitimate interests, reporting, or disputes.