Choosing a preset city differs from searching for a place through the location endpoint.
How Avenyora works
Make deliberate choices about your birth data
A date, time and birthplace can feel ordinary on their own but become personal when combined. The practical questions are which details are needed, whether they leave your device, when the application saves them, and how saved material is used later. Signed-in birth-chart generation attempts an automatic account save, so review that behavior before entering details.
Clear method Reflection, not prediction
Quick guide
What to know first
A temporary browser result is not the same as an account record.
Signed-in birth-chart generation automatically attempts to save a reading and birth profile and refresh the Blueprint.
AI requests can involve server-side processing; this is not an end-to-end encrypted private notebook.
Account removal does not imply that required financial records or independent payment-provider records disappear.
Provide enough location context, not a full address
The chart needs geographic coordinates and a time-zone identifier. It does not need the street address of a hospital, a birth certificate image or an identification number. Select the intended city carefully: similarly named places can have different coordinates and clock rules.
Choosing a preset can avoid a search request. Typing into the location search sends the search query to the application's location endpoint, which may use its configured location service. A local chart calculation should therefore not be described as a promise that no network request of any kind occurs while using the page. Keep the query limited to a city or region rather than a private address.
Distinguish this device from your account
For a guest, the birth-chart flow can retain a temporary result in this browser while preparing a handoff. The server-side journey identifier initially carries navigation metadata, not raw birth details. Continuing the authenticated save process submits the input so the service can calculate and store an account result. When already signed in, generating a birth chart automatically attempts to save a Reading and BirthProfile and refresh the Blueprint. Signed-in tarot draws also attempt an automatic reading-history save; numerology and basic compatibility use an explicit Save action.
Browser storage is separate from server storage. MDN's Web Storage documentation describes persistence and the effects of browser settings. On a shared device, consider whether leaving a local result is appropriate. Clearing site data can remove a local handoff, but does not erase a record already saved in your account.
Understand the purpose of each saved item
A birth profile supports chart-based context. A journal entry records something you wrote. A memory item is a reusable piece of personal context; removing one record does not automatically remove related records. An export is a copy, not a deletion request.
Companion requests include your Blueprint, up to four recent readings and up to eight recent chat messages by default. Successful user and assistant messages are saved and can provide later conversation context. Extra long-term memory and recent journal context require Premium access and active account consent; the request's memory switch can exclude them. Disabling that memory does not disable ordinary chat history or Blueprint context. These inputs may be processed on the server and by the configured AI provider. Consider that processing before sharing sensitive information.
A deletion request has more than one boundary
The Avenyora Privacy Policy is the current notice for the service's data practices. Consult it for the account process and contact route. The application supports account removal and retains financial records needed for its billing history. A payment provider also has its own records and obligations; an application cannot promise to erase those by deleting its own profile.
Before deleting an account, review any subscription and the records you still need. Keep your own receipt or permitted export somewhere appropriate. Do not send passwords, payment credentials or a full birth certificate when asking for help with a data issue. A page address and a minimal description of the affected control are usually more useful for an initial support request.
Common questions
Frequently asked questions
Does clearing my browser delete a saved account profile?
No. Browser data and server-side account records are different. Use the applicable account controls for saved records; clearing site data mainly affects this device.
Can I calculate a chart without sharing a street address?
Yes. A city selection supplies the geographic and time-zone context. A street address or identity document is not required for the chart input.
Which records have application-layer encryption?
New chat message content and private journal and memory payloads use application-layer encryption. Birth charts and reading inputs/results are application-readable JSON fields, not protected by that same payload encryption. Older records may use legacy storage; this is not a claim that a migration is complete. Application encryption is not end-to-end encryption: authorized processing and AI requests can need readable context.