Vestara

Privacy Policy

Effective September 9, 2026

Effective date: September 9, 2026

Short version

Vestara is an iPhone astrology app operated by an independent developer. The app does not require an account and does not collect your name, email address, or phone number. Your birth details stay on your device and are used there to calculate your chart. Some features send a request to a Vestara Cloudflare Worker: Ask sends your question, derived factors, today’s sky factors, an installation-level session ID, and, when applicable, a Plus receipt; paid readings send derived chart information, transit factors, report settings, locale, a purchase receipt, and product ID. These requests can be processed by DeepSeek, our AI provider. The service also uses an installation-level session identifier and, for Plus requests, a verified Apple purchase transaction identifier for rate limiting and deduplication.

Vestara does not run advertising or analytics features in the app code. Provider systems may have their own logging, security, and retention practices, described by their own policies.

What stays on device

Birth date, birth time, and birthplace are stored locally and used to calculate the chart on the device; these birth details stay on your device. Raw birth date, time, city, latitude, and longitude are not part of the production request contracts described below. App preferences, notification choices, and remaining Ask credits are also stored locally. iOS schedules daily notifications on the device.

What is sent and why

Ask. The request contains the question, derived chart placements, available transit factors, today’s sky factors, an installation-level session_id, and, when applicable, a plus_receipt used for Plus verification. The service uses these fields to answer the question, verify the applicable tier, and enforce rate limits. Ask rate-limit records use a date-bucketed key with a 48-hour KV TTL: free requests use the session ID as the rate-limit subject, while verified Plus requests use the Apple originalTransactionId. The Ask answer is not written to the report store, although the rate-limit record is stored for that TTL. Daily fair-use limits apply to Ask on every tier.

Reading. A paid reading request contains the derived chart, transit factors, report settings (such as the reading window, arcs, cadence, and any event identifier), locale, product_id, and an Apple receipt for verification. The receipt is used for Apple verification and is not sent to DeepSeek or stored in the report value. The generated report is stored under a report_id for one year (a 365-day TTL that restarts when you ask a follow-up). The verified Apple originalTransactionId is retained in server-side rate-limit or deduplication keys; the raw receipt is not stored in the report value.

Follow-up. A follow-up request contains a report_id and a new question. The service reads the stored report and sends the full stored report content plus the new question to DeepSeek for a single answer. A successful follow-up updates the stored report record and resets that report record’s one-year TTL from the update time.

The service does not receive raw payment-card or bank details. Deleting the app removes local app data; it does not immediately remove a server-side report. Server-side records expire under the retention periods above, and privacy requests can be made using the contact address below.

Providers

Apple provides App Store distribution, StoreKit purchases, and purchase verification inputs.

Cloudflare hosts the Worker that handles Ask, readings, and follow-ups. The application code does not establish the scope or retention of Cloudflare platform-level logs, so this policy does not make a broader claim about those logs.

DeepSeek is the upstream AI provider. Ask sends derived factors and the question. Reading sends the derived chart, report settings, and locale; the receipt and product ID are used by the Worker and are not included in the report prompt. Follow-up sends the full stored report and the new question. DeepSeek and other providers may process or retain request data according to their own policies; Vestara does not make a retention promise on a provider’s behalf.

Purchases

Subscriptions and in-app purchases are processed by Apple. Vestara receives purchase verification data needed to unlock the applicable feature and to support rate limiting or deduplication; this can include transaction identifiers even though Vestara does not receive raw payment-card or bank details. Refunds and subscription management are handled through Apple.

Notifications

Notification choices are stored locally and notifications are scheduled by iOS on the device. Vestara does not operate a push server for these local notifications and does not receive a read receipt.

Your rights

For privacy questions or rights requests under applicable law, contact support@joinvestara.com. A request may concern local data, a report identified by report_id, or service-side rate-limit and purchase-related records. We will review the request against the data and retention rules that apply to the relevant service record.

Changes

If Vestara changes how it handles data, this page will be updated with a new effective date before the change ships.

Contact

Vestara is operated by an independent developer. Contact: support@joinvestara.com.

Privacy · Support · Free vs Plus · Houses · Refunds · AI