Privacy Policy

Esotool is the data controller for account, security, service usage, and support data. For personal data entered by a practitioner about their clients, the practitioner determines the purposes and means of processing and is the controller; Esotool acts as processor under the Data Processing Agreement.

Removing names and direct identifiers from a workflow does not necessarily anonymise the remaining information. Birth date, time, and place may still identify a person indirectly when combined with other information.

• account identity, email, authentication ID, practice membership, and role;
• contract evidence, including the accepted wording, version, date, and account ID;
• practice details, contact information, preferences, logo, and language;
• client records, optional contact details, birth details, sessions, intentions, notes, calculations, readings, interpretations, and reports;
• technical requests, audit and error events, credit usage, AI-provider attempts, token volumes, and cost estimates;
• support messages and the information needed to handle them.

Data comes from the account holder, authorised practice users, actions in the application, and service providers such as the authentication service. Practitioners enter client data under their own responsibility and must provide their clients with their own privacy information.

• providing accounts, calculations, reports, exports, and requested features: performance of the contract;
• recording contractual acceptance and defending rights: performance of the contract and legitimate interest in retaining evidence;
• securing the service, preventing abuse, diagnosing errors, and measuring technical costs: legitimate interests in security and reliable operation;
• handling support and rights requests: contract, legal obligation, or legitimate interest depending on the request.

Practitioners determine the purposes and legal bases for their clients’ data. Esotool processes that data only on documented instructions.

Data is sent to a specialised provider only when a user actively starts an assisted generation. Structured names and account or client identifiers are excluded from prompts. Depending on the module, calculation results, astrological positions, birth details, drawn cards, and request text may be sent. Practitioners must not add direct identifiers or excessive data to that content.

Provider processing and retention are governed by service settings, contracts, and applicable safeguards. Generated results remain in the practitioner’s workspace for review and report preparation; they are not automatically sent to a client and are not used for solely automated decisions producing legal effects.

Data is available only to authorised practice users, authorised publisher staff when support or security requires it, and providers strictly needed for hosting, authentication, place search, and AI-assisted features. Providers handling client data are described in the Data Processing Agreement.

Application data is primarily hosted in the European Union. Where a provider or its staff processes data outside the EEA, the transfer relies as applicable on an adequacy decision, European Commission Standard Contractual Clauses, and suitable supplementary measures. Relevant contractual safeguards can be requested from the privacy contact.

• account and practice data is kept for the contractual relationship and as needed for closure and legal claims;
• client business data remains until the practitioner deletes or exports it, requests its return, or closes the account;
• after account deletion, a limited recovery receipt containing an email hash, quota period and usage, end of access, and necessary technical references is retained for 400 days by default, then automatically deleted;
• technical logs and metrics are retained only as proportionate for security, diagnosis, deduplication, and cost monitoring, then deleted or aggregated;
• backup copies are isolated from normal use and expire with their rotation cycle unless retention is legally required.

Astrology interpretations and notes may also be cached locally in the practitioner’s browser until site data is cleared. See the cookie and local-storage policy.

Measures include logical separation between practices, authentication and access control, encrypted communications, private storage, encryption at rest, security headers, useful event logging, and limiting data exposed in errors. No service can promise zero risk. Esotool follows GDPR incident procedures and assists the practitioner when an incident concerns data processed for them.

Practitioners can export a structured JSON record containing a client profile, sessions, calculations, reports, and related results, and can permanently delete a record and its linked active-storage items with reinforced confirmation. Practice owners can also delete the full account from settings; this removes business data, files, and active individual metrics, closes the authentication account, and clears local browser storage. A new registration never restores deleted clients, sessions, reports, prompts, or results.

Subject to applicable law, account users may request access, correction, deletion, restriction, objection, or portability, and may withdraw consent where processing relies on it. A client of a practitioner should first contact that practitioner, as controller.

For account privacy questions or rights requests, contact info@esotool.com. Proportionate identity verification may be required. You may also complain to the Belgian Data Protection Authority.

This policy may change with the service or applicable law. Its date and version appear at the top. Material changes will be announced by an appropriate method and may require renewed contractual acceptance.