Privacy, safety, terms, and refunds
Understand sensitive birth data, generated-guidance limits, consent, sharing, account and payment terms, refund expectations, and the policy pages that govern them.
Questions this guide answers
- How should I protect birth and relationship data?
- What are the limits of generated guidance?
- Where are refund rules explained?
Before you begin
- Read the live policy pages for the controlling legal text. This guide is a practical orientation, not a substitute for those policies.
Step by step
- 1
Collect the minimum
Store only the birth, relationship, and personalization data needed for the agreed task.
Expected result: The prepared record contains only the fields needed for the agreed task.
- 2
Use synthetic demonstration data
Never place real names, birth facts, report IDs, delivery links, or client questions in public screenshots, videos, bug reports, or training fixtures.
Expected result: The demonstration artifact contains synthetic details and no real identifying chart or report data.
- 3
Review before sharing
Confirm subject consent, recipient, channel, expiry, and whether the artifact includes sensitive context.
Expected result: Consent, recipient, channel, expiry, and sensitive contents are confirmed before sharing.
- 4
Separate guidance from professional advice
Do not use Vedastram as medical, legal, financial, mental-health, emergency, or guaranteed-outcome advice.
Expected result: The output remains framed as limited guidance rather than professional advice or a guaranteed outcome.
- 5
Use the controlling policy
Open Privacy for data handling, Terms for product and guidance conditions, and Refund for subscription or add-on expectations.
Expected result: The relevant current Privacy, Terms, or Refund page opens for the controlling details.
High-trust astrology needs restraint
Marriage, health, family, finances, and identity are sensitive areas. Present chart evidence and uncertainty without fear, coercion, or deterministic claims.
Never predict death timing, exploit vulnerability, or turn a single factor into irreversible advice.
Feedback and analytics should be privacy-safe
Help analytics should measure route, search, completion, and helpfulness without collecting natal facts or private report text.
If a support comment requires sensitive context, disclose only what is necessary and use the approved support channel.
Policies can change
Pricing, availability, billing partners, refund rules, and data practices can evolve. The dated policy page and checkout summary take precedence over a help example.
Troubleshooting and recovery
A shared report went to the wrong recipient
Revoke the delivery link when supported, notify the appropriate owner, and follow the applicable privacy incident process.
A billing outcome differs from an old screenshot
Use the live checkout summary, account state, and current Refund policy. Help screenshots are explanatory, not contractual pricing records.
Frequently asked questions
Can I use a client chart in a tutorial with the name hidden?
Use a fully synthetic profile. Removing only the name does not reliably anonymize date, time, place, chart, or report context.
Which page controls a refund request?
The current Refund policy and the actual purchase terms control. Contact the stated support channel with the transaction reference, not private chart data.
Terms used in this guide
- Synthetic data
- Invented demonstration data that does not correspond to a real person.
- Deterministic claim
- A statement that presents an uncertain astrological interpretation as a guaranteed outcome.
Did this guide help you complete the task?
Owner: Vedastram Product Education