Help & Trust
Why is some detail limited?
What to check when part of an experience cannot be shown.
Missing information — Check that required details are present. If you do not know them, leave them unknown; do not guess.
Low confidence — Treat the result as limited context. Review any source or confidence detail shown, and add more precise information only when you genuinely know it.
Unsupported scope — Use another available part of Akashr. Repeating the same action will not add a detail this experience does not support.
Access not included — Review the access or plan message shown for that feature. This is different from missing evidence; changing your information will not unlock access.
Temporary service or provider failure — Wait and try again later. If the message keeps returning, contact support with the help topic or error code.
Birth details and missing layers
Why date, place, and exact time change what Akashr can show.
Why Akashr asks — Your birth date anchors date-based calculations. Your birth place resolves the historical timezone and coordinates. An exact time unlocks the Ascendant, Midheaven, houses, and time-dependent Human Design layers.
Unknown or approximate time — Keep an unknown time marked unknown; do not guess. Akashr omits unsupported houses, angles, Human Design, relationship, or timing layers instead of inventing them. Date- and place-supported calculations can still be available. A low-confidence result is different from missing evidence, plan access, an unsupported experience, or a temporary service error.
People and relationships — Your own profile, a managed person you control, a connected account controlled by someone else, and a name-only relationship thread have different permissions. You cannot correct another connected account’s birth details.
Corrections — Review the consequence shown in Birth chart configuration before saving. A saved correction recalculates the profile and invalidates derived caches that depend on the old details. Saved historical artifacts can retain the evidence context they were created with. Akashr shows any Credit consequence before confirmation.
How calculations and AI work together
Deterministic evidence, Google Gemini, validation, and current data-use limits.
Deterministic calculations — Akashr calculates chart, timing, and source evidence before an AI narrative layer. The model does not invent those calculations. Open source detail, confidence, or technical detail when available to inspect the evidence boundary.
AI narrative — Akashr sends relevant structured evidence and bounded context to Google Gemini to generate or classify content. Outputs are validated and can still be incomplete or wrong. Internal prompts and hidden instructions are never displayed.
Training and retention — The canonical Privacy Policy explains the terms that apply to Akashr’s Google service tier. Google Paid Services state that prompts and responses are not used to improve Google products, subject to logging, abuse-monitoring, legal, and service exceptions. Akashr’s launch checklist still requires production paid-project and retention verification, so do not treat no-training as unconditional until that evidence is recorded.
Use the result as reflective guidance, not medical, legal, financial, or crisis advice. The Privacy Policy and Terms are the current source of truth.
Export, clear, remove, or delete
Choose the operation that matches what you want removed.
Export — A signed-in export downloads a JSON bundle of account-owned data. It is limited to one request per 24 hours and excludes another connected person’s private birth data. Export does not delete anything.
Clear selected data — Profile settings can clear selected chats, readings, journals, intentions, practice logs, Memory, or Connection Link data. Your account, birth profile, Credits, and subscription remain unless the confirmation says otherwise.
Remove a managed person — This permanently removes the owner-controlled person and its owned relationship artifacts. It does not delete another registered account.
Remove a relationship thread — This removes the selected owner-held thread or history; it is not the same as blocking a connected account or deleting either account.
Delete account — This removes sign-in access and starts the full account-erasure cascade, including invitations, private pair access, notifications, and owned generated data. Active storefront obligations, billing records required by law, security holds, backups, caches, and processors follow the retention and propagation periods in the Privacy Policy. Clear selected data and delete account are never equivalent.
Billing, cancellations, and purchases
Find the right owner for Stripe, Apple, or Google Play purchases.
Check the owner first — Web purchases are managed through Stripe. Native storefront controls appear only when that storefront is enabled for the installed build; until then, web billing remains the active purchase path. When enabled, iPhone and iPad purchases are controlled by Apple and Android purchases by Google Play, with RevenueCat synchronizing the store entitlement to Akashr. Sign in to the same Akashr account and the same store account used for purchase. Store configuration and physical-device acceptance remain launch gates.
Cancellation — Cancel with the purchase owner. Access normally continues through the paid-through period shown by that owner. Deleting Akashr does not replace storefront cancellation.
Restore — On an enabled Apple or Google Play storefront, use the store restore or purchase-management path while signed in to the original store account and correct Akashr account. Web Stripe purchases reconcile through Billing.
Refunds — Request a native refund from Apple or Google Play. Stripe purchase refunds follow the web Terms and support path. Akashr cannot override a storefront decision.
Duplicate, pending, failed, or missing access — Do not purchase again immediately. Confirm both accounts, wait for a pending payment to settle, restore or refresh Billing, then contact support with the storefront, purchase date, and a redacted receipt identifier. Never send a full receipt, payment token, card, or bank details.
Sign-in and account recovery
Resolve verification, expired sessions, and account mismatches safely.
Sign in with the same provider and email you originally used. A different Google, Apple, or email identity can create or open a different Akashr account even on the same device.
If verification is pending, complete it in the original browser or provider flow, then return to Akashr. If a session expires, close duplicate sign-in tabs and sign in again; do not share the verification link or code.
If billing, History, or connections look missing, first compare the signed-in Akashr account with the account that owns them. Do not create another purchase while an account mismatch is unresolved. Contact support with the provider name, masked email, device or browser, and a safe error code only.
What Oracle reflections can and cannot do
How Akashr uses AI and symbolic language.
Akashr offers AI-generated symbolic reflection. It cannot contact spirits or deceased people, confirm signs, detect hidden agents or messages, or determine objective reality. Treat Oracle, ancestor, past-life, and mediumship experiences as metaphorical prompts for reflection, not verified contact or fact.
Retired Return Insights
Return Insights are no longer generated; existing saved copies remain in History.
Free keeps deterministic personal and daily value. Return Insights are no longer generated. If you already own a valid saved copy, you can reopen that exact narrative from History without another provider call. It is not regenerated, migrated, or charged again, and remains covered by export and deletion controls.
Notification delivery and fallback
Check permission, subscription, delivery health, and the in-app bell.
Akashr separates per-installation permission from server delivery health. One device becoming healthy does not repair another installation, and permission alone does not mean push is working.
Web and installed PWA — Open your browser’s site information or site settings for app.akashr.com, then review Notifications. On iPhone or iPad, web push requires an installed Home Screen app; after installation, review Settings > Notifications > Akashr. On Android, review the browser or installed app under Settings > Apps > Notifications. Menu names can vary; Akashr cannot change these settings for you.
Remediation — Check the current installation, subscription health, quiet hours, timezone, daily limits, and whether the message was deduplicated. A stale link can no longer open removed or unavailable content. Refresh delivery health after changing Settings.
If push is unsupported, denied, restricted, missing a subscription, stale, or temporarily suppressed, use the in-app bell in Circle. Never send support your notification token, screenshots with unrelated personal content, readings, prompts, birth data, or relationship messages.
Web
On the web — Open your browser's site settings for app.akashr.com and review Notifications. On iPhone or iPad, web push needs an installed Home Screen app (iOS 16.4+); add Akashr from the Safari share menu, then review Settings > Notifications > Akashr. Akashr cannot change these settings for you.
iOS
On iPhone or iPad — Open Settings > Notifications > Akashr to review permission and delivery style. If Akashr is a browser tab, install it to your Home Screen first (iOS 16.4+). Akashr cannot change these settings for you.
Android
On Android — Open Settings > Apps > Akashr > Notifications, or your browser's site settings, to review permission and channels. Akashr cannot change these settings for you.
Review a safe support summary
See exactly what a minimal diagnostic contains before sharing it.
Akashr builds a bounded summary from only the stable help-topic ID, a fixed originating product route, an allowlisted error ID, platform, and content version. Review the summary before you copy it; it is not sent automatically.
The summary excludes account identifiers, email, raw tokens, internal prompts, hidden instructions, complete generated narratives, birth data, relationship content, payment details, and unrelated personal information. Invalid route or error values are discarded. Another person’s private data is never attached.
If self-service does not resolve the problem, email contact@akashr.com with the reviewed summary and what you expected to happen. Support will reply through email with the next step. For immediate danger or crisis support, use the public Support safety resources instead of waiting for an account response.
Contact support safely
Get help without sharing more personal information than needed.
Email contact@akashr.com with only the help topic or error code, what you expected to happen, and your device or browser. Do not send raw access or authentication tokens, internal prompts or hidden instructions, payment card or bank details, passwords or sign-in codes, your birth data, another person’s birth data, complete readings, or unrelated personal information about you or anyone else. Review screenshots before sharing and remove anything unrelated to the problem.
