Your atlas, your information.
Who is responsible
ASPECTORY is provided by P and A LLC, trading as Panda LLC, registered in the Republic of Kazakhstan. Contact support@pandallc.dev for privacy requests. This policy describes the ASPECTORY mobile app and its service. Updated 7 November 2026.
Information you choose to provide
We process your sign-in email and account identifiers; travel projects, dates, preferences, entered budget estimates, notes and decisions; support messages and safety reports; and store purchase and allowance records. Supabase Auth manages passwords. Passwords are not included in business data, account exports or analytics. Birth date, time and selected birthplace coordinates are optional for practical planning. We do not request device GPS access.
Optional astrological calculations
When you explicitly request a calculation, the server sends the birth date, time when available, selected location coordinates and calculation settings to astrology-api.io. This is required to calculate the requested chart and city perspective. Birth profiles and temporary raw calculation responses are encrypted on our server. You can plan without providing birth details. Astrology is a symbolic perspective, not a prediction of events.
Service providers
Supabase provides authentication, database and private file storage. Render hosts the API and background jobs. Resend delivers sign-in and verification email. RevenueCat verifies Apple or Google transactions using an account identifier and purchase information. Apple or Google handles payment credentials; ASPECTORY does not receive your payment card details. Mapbox supplies map resources and processes network/device information needed for delivery; app map telemetry is disabled. Place search uses imported GeoNames data in our database. Providers may process network and security logs under their own terms and retention schedules, and may process information outside your country.
Manual profiles without an account
A creator may enter one project-specific companion birth profile after stating that they have permission. They must share a notice and attest that they delivered it before requesting the companion calculation. This is the creator’s statement, not an independently verified action or identity of the other person. The notice includes a public support reference and a separate private deletion code. The code authorizes deletion of that manual profile only; the server stores its hash. The person can request deletion without creating an account. The creator can also delete the profile. This does not close the creator’s account, cancel a subscription or return a consumed allowance.
Sharing with your companion
Together shares a limited trip view and the priorities you explicitly publish with one invited companion. Each person separately controls publication of their regional chart geometry and interpretations. A new private calculation is not published automatically. Revoking a publication removes its common section and dependent online files. While membership and the project remain active, a guest may still read and export their own private result; leaving, removal, blocking or project deletion closes access to project snapshots while their global self profile and other projects remain their data. A previous manual profile is not identified with a person who accepts an invitation; its old data remains private to its creator. Your raw birth details, private journal and written personal choice reason are excluded from shared travel briefs. Saving a private draft does not publish it. A recipient controls a PDF or other copy you choose to save or send.
Why we use information
We use information to authenticate you, save and compare trips, run requested calculations, verify purchases, deliver exports, respond to requests and protect the service. We do not sell personal information or use it for advertising or cross-app tracking. Product analytics and crash-reporting service sinks are currently disabled. Hosting and provider security logs are separate from product analytics.
Retention and deletion
Account content remains while the account is active, until you remove it or request account deletion. Server export files expire within 24 hours; download links expire within five minutes and require the signed-in account. Account deletion closes access when accepted; background processing removes account content and provider profiles and retries outages. Backups and processor logs follow their configured retention and are not all erased instantly. Separate signed account and manual-profile erasure journals are reapplied before a restored service becomes readable. An accepted manual-profile deletion closes access first; background cleanup then removes its stored birth versions, calculation cache, raw responses, publications and dependent exports. Signed proofs and opaque consumed-allowance records remain to prevent restoration or quota resets. Minimal de-linked purchase/consumed-allowance records and signed erasure proofs have no automatic expiry; they are kept for reconciliation, prevention of replay and keeping erased accounts erased. They exclude your email, birth details and trip content. Files you previously saved or sent are outside our control.
Your controls
In Profile → My data & privacy you can request your own account-data JSON without a purchase and delete your account after recent authentication. The JSON can include private birth data, journals and manual profiles you control: protect any saved copy. It excludes other participants’ private birth profiles and never includes a private deletion code. You can edit your details, stop requesting calculations, unpublish shared priorities, leave a shared trip and use the in-app block/report controls. Signing out removes the local account cache. Depending on your location, you may have additional access, correction, objection or deletion rights; contact support@pandallc.dev. We verify identity before acting on private data.
Children and changes
ASPECTORY is intended for adults and is not directed to children. Contact us if a child has supplied personal information. We will update this page when service practices change; the date above identifies this version.