How Ezospace handles your data
Ezospace asks for personal information like birth details, saved-reading data, and sometimes compatibility inputs. This page explains what we collect, why we use it, and the boundaries we are trying to keep clear.
Information we may use
Ezospace may collect the information you provide directly in order to generate readings, save them to your space, and let you come back later.
- first name and, where relevant, birth name
- birth date, birth time if provided, and birth place
- email address for claim/save and account access
- compatibility inputs about another person, if you use that feature
- question text for Oracle-style features, if those are used and saved
- generated readings, saved artifacts, and related timestamps/state records
- basic technical/session/security information needed to operate the site
What the data is for
- to generate your Ezospace reading or symbolic output
- to save your result if you choose to claim or keep it
- to connect future unlocks to the same account or saved space
- to support compatibility features and handle partial-data states honestly
- to secure, debug, and maintain the service
- to confirm fulfillment and paid access if purchases are introduced
Important boundary
Ezospace is a symbolic self-discovery product, not a medical, legal, financial, or therapeutic service. We try to keep the product useful without pretending to know more than the input and method can honestly support.
Using another person's details
If you use compatibility features, you may enter limited information about another person. Please only use information you are comfortable providing and allowed to use.
- Compatibility outputs are reflective and symbolic.
- They are not factual proof of another person's hidden motives or private inner state.
- Ezospace should ask for the minimum information needed for the feature rather than turning relationship curiosity into surveillance theatre.
How long we keep things and who may help run the service
We do not want Ezospace to operate on the logic of “keep everything forever just in case.” Temporary unclaimed artifacts should expire, while claimed results may stay available as part of your saved reading history unless you request deletion or a legal retention reason applies.
- temporary unclaimed reading objects should expire automatically
- saved claimed results may remain in your account history
- security and service logs may be retained for a limited operational period
- payment/order metadata may be retained where needed for accounting, disputes, or fulfillment
Ezospace may also rely on third-party providers for hosting, storage, auth, payments, email delivery, analytics, or AI-generation infrastructure. Final provider details will be published once the live stack is locked.
Access, correction, and deletion
Depending on where you live, you may have rights such as asking for access to your data, asking for correction, requesting deletion, or objecting to certain processing.
Before paid public launch, Ezospace will publish a dedicated privacy contact route and finalize the exact process for handling these requests.
Current practical note
If a result is saved to an account, we may need to verify that the request really comes from the account owner before changing or deleting account-linked data.