Skip to content

Security & privacy

Tarot questions can be intimate. The infrastructure must treat them accordingly.

The product uses account ownership, role permissions, private file delivery and controlled reader access so spreads never appear on public pages or in openly accessible resources.

Authenticated accessPrivate filesRole separationAccount deletion

Core safeguards

Security is a system of boundaries.

No single checkbox makes a private product. The important part is how ownership, files and roles interact.

🔒

Ownership checks

Users access their own profiles, spreads and orders.

Reader isolation

A tarot reader sees only eligible orders assigned to their active persona.

Private media

Spread images use private storage and authenticated delivery rather than public gallery URLs.

Input controls

REST nonces, validation, file type checks and size limits reduce obvious abuse.

Audit trail

Important order, consent and delivery events can be recorded.

×

No public indexing

The application layer is intended to remain outside search indexing.

Data minimisation

Do not put a biography into a field that needs one date.

The strongest privacy control is not collecting unnecessary information in the first place.

  • Use only the birth and relationship data needed for the selected spread.
  • Do not include document numbers, passwords or unrelated medical detail in a tarot question.
  • A reader receives data required for the assigned service, not unrestricted account access.
  • Retention periods must be defined in the final privacy policy and implemented in operations.

External processors

Services that may receive necessary data.

Payment providers and WooCommerce process transaction and billing data according to the configured checkout.

An AI API may receive the selected context, cards, meanings and working text required for generation or recognition.

A geocoding provider may receive the place search text used to resolve location details.

E-mail infrastructure processes messages and service notifications.

Contract and configuration matter

The operator must maintain current processor terms, access control and retention settings.

Marketing copy is not a privacy policy

The final legal documents must accurately name the operator, purposes, legal bases, recipients and retention.

FAQ

Security questions

Are spread photos public media files?+

They are designed for a private authenticated flow, not ordinary public media-library exposure.

Can support read every question by default?+

Administrative access should be limited to what is necessary for service, security and dispute handling.

Does deleting the account erase every transaction record immediately?+

Not necessarily. Legal, tax, fraud-prevention or dispute records may need to be retained or anonymised for defined periods.

Is two-factor authentication available?+

The final production environment should enable strong authentication, especially for tarot-reader and administrator accounts.