Last updated: October 31, 2026

Privacy Policy

The Vedika API Platform is operated by XALEN Technology Private Limited (registered office: Pune, Maharashtra, India), the data controller for the purposes of this policy. You can reach us at [email protected].

1. Information We Collect

When you use Vedika API Platform, we collect:

  • Account information (email, name) provided during sign-up
  • API usage data (requests, responses, timestamps)
  • Technical information (IP address, browser type, device information)
  • Payment information (processed securely through third-party providers)
  • Business and contact information you provide in a Google-hosted inquiry form

2. How We Use Your Information

We use your information to:

  • Provide and improve our API services
  • Process your requests and manage your account
  • Send important service updates and notifications
  • Analyze usage patterns to enhance performance
  • Ensure security and prevent fraud

Emails we send

Account, security, billing and service emails are part of running your account, so we always send them. Examples are sign-in and verification codes, receipts, payment problems, a reminder before your trial ends, and help if your API key has not made its first call.

Product news, updates and the newsletter are separate. We send them only if you choose to receive them, with the box at sign-up or the "Newsletter and product news" switch in Settings. In India the sign-up box starts ticked and you can untick it before you continue; everywhere else it starts unticked. We record what you chose, when, where you chose it and which version of this policy applied. We send roughly 2 of these emails a month.

Every product news email has a one-click unsubscribe link and a link in its footer. Unsubscribing takes effect straight away and never stops account, security or billing emails. You can also turn product news back on in Settings.

Google-hosted inquiries

When you send an inquiry through a Google-hosted lead form, we receive the business and contact details you provide and the form and submission details needed to track your request. We use this information to answer your inquiry, follow up about that request and record its status. Sending an inquiry does not give us permission to add you to a marketing list or use your email for advertising matching.

3. Data Storage and Security

Your data is stored securely using industry-standard encryption. We use secure multi-region cloud infrastructure that routes each request automatically. Customers agree any data-residency needs at signup, as part of enterprise terms. The infrastructure includes:

  • Encrypted data transmission (HTTPS/TLS)
  • Secure authentication mechanisms
  • Regular security audits and monitoring
  • Access controls and logging

Chat retention and use

We store chats, including questions, answers and birth details supplied in the conversation. Chats are kept, including for future training. For customers on a signed enterprise agreement, Customer Content is used to train or improve our models only if the customer opts in. Vedika keeps no copy of palm photographs and does not use them to train or improve any model; the AI model providers that make the reading may hold inputs for a limited period under their own terms. Active conversations expire after 24 hours by default, or seven days when created through an enterprise API key. Conversation settings can extend that lifetime. Expiry ends active chat access; it does not mean the stored data is deleted.

Inquiry retention

Our policy is to remove the details of unanswered or inactive inquiries 90 days after the last inquiry activity. This policy applies to inquiries that are not part of a customer account or completed sale. New activity on an inquiry restarts the 90-day period. Before removal, we verify which retention rule applies; records are preserved while that check is unresolved. This inquiry policy does not change the retention rules for customer accounts, completed sales or billing records.

Support ticket retention

We keep a support ticket, with its messages and any attachments you uploaded, for 24 months after the ticket is closed, and then delete it. A ticket that is still open is kept. If you reopen a closed ticket, the 24 months start again when it is next closed. If you ask us to erase your data, we delete your support tickets and attachments sooner. Backups are kept on our normal backup schedule.

4. Data Sharing

We do not sell your personal information. We may share data with:

  • Third-party AI service providers for processing API requests
  • Payment processors for billing
  • Service providers who assist in operations
  • Law enforcement when required by law

5. Your Rights

You have the right to:

  • Access your personal data
  • Correct inaccurate information
  • Request deletion of your account and data
  • Export your data
  • Opt-out of marketing communications

6. Cookies and Tracking

We use cookies and similar technologies to:

  • Maintain your session
  • Remember your preferences
  • Analyze usage patterns

How we ask depends on where you are. We read your country from your connection, using a country code that Cloudflare, which already serves this site, provides; we keep it only in your browser tab. In the European Economic Area, the United Kingdom, Switzerland, Canada, Brazil, South Korea, Japan, Singapore, Mexico, Thailand, Indonesia, Vietnam, South Africa, Colombia and Ecuador, in a few other European countries (Andorra, Monaco, Montenegro, Albania, Moldova, North Macedonia and Serbia), and in the overseas territories and Crown Dependencies of EU Member States and the United Kingdom, we ask first: analytics and marketing stay off and Google's tags do not load until you choose Accept all or Save choices. If we cannot tell where you are, we ask first as well. Everywhere else, Google Analytics, Google Ads measurement and Cloudflare Web Analytics run by default, and you can opt out at any time with Your privacy choices at the bottom of every page. In every region, a Global Privacy Control signal from your browser keeps analytics and marketing off with no prompt, even if you accepted earlier: while the signal is on, Accept all has no effect, and a choice you saved applies again if you switch the signal off. Session replay (Microsoft Clarity) requires an explicit Analytics choice; the Meta pixel requires an explicit Marketing choice. Neither starts from a regional default. Matching an inquiry-form email always needs its own checkbox. We apply Google Consent Mode v2: consent signals start as denied for the places where we ask first, and then follow your choice.

Your choice is kept in your browser for up to 180 days. When you create an account in the same browser, that setting, with the campaign labels and permitted advertising click identifiers, is attached to the account so we can measure which ads led to a sign-up or purchase. Where measurement runs by default, that setting is the default described above, not a click; opting out in Your privacy choices while signed in withdraws it. Residents of US states with privacy-rights laws use Your privacy choices, or a Global Privacy Control signal, to opt out of targeted advertising and sharing.

When ChatGPT ad measurement is configured, it requires an explicit Marketing choice in every region and respects Global Privacy Control. OpenAI may receive public-page visits and approved business conversion outcomes under that permission, using a pseudonymous account identifier and advertising click or browser references when available. Its Pixel uses first-party __oppref cookies for up to 30 days and __obref browser-reference cookies for up to 365 days. We stop using a click reference for new attribution after 30 days. Server-side account consent records may retain the reference for up to 180 days; enterprise inquiry records follow the inquiry retention policy above. Withdrawal clears browser references and stops future measurement once recorded; it does not promise immediate deletion of all server records or events already received by an advertising provider. We do not enable automatic advanced matching or send astrology inputs, birth details, reports, inquiry text, raw email addresses or private application URLs to OpenAI for advertising.

When Analytics is on, we use Google Analytics to measure page views and product usage. When Marketing is on, we use Google Ads measurement to understand visits and approved sign-up, lead and purchase outcomes. Google may receive event, device and campaign identifiers for these purposes. After an approved account outcome, we may send a SHA-256 hash of the consenting account email for enhanced conversion matching. Inquiry-email matching is separate: it requires both the unchecked optional checkbox on that inquiry form and current Marketing permission. We normalize and SHA-256 hash the inquiry email before Google Ads matching; we do not send the raw inquiry email for this purpose. Declining the checkbox leaves submission available. Privacy choices on each public page lets you withdraw Marketing permission and withdraw inquiry-email matching for submissions saved in this browser; withdrawal stops future matching attempts once recorded. If you no longer have that browser, contact [email protected] to withdraw this permission. We do not sell this information or use it to read your API content.

7. Children's Privacy

Our service is not intended for users under 18 years of age. We do not knowingly collect information from children.

8. Changes to This Policy

We may update this privacy policy from time to time. We will notify you of significant changes via email or through our platform.