Legal ยท Privacy
Privacy Policy.
This page describes the information EQYERA's current application code can process. It is a structured draft prepared for owner and legal review, not a claim of regulatory certification.
1. Scope and contact
EQYERA is a research and screening product for Indian equities. This policy covers the public website, account and subscription surfaces, and the research workspace. For privacy questions or requests, contact support@eqyera.com.
2. Information the application can process
- Account information: name, email address, optional mobile number, profile image if supplied, referral code, referral relationship, account status and timestamps.
- Authentication information: password hashes, token records, token expiry and revocation state, and browser-local authentication state.
- Subscription and payment records: plan, subscription dates and status, payment amount, currency, status, method and Razorpay order/payment identifiers. EQYERA does not store card or banking credentials; payment details are handled by the payment provider.
- Referral records: referral codes and the relationship between referring and referred accounts.
- Device notification data: a device token and platform may be stored if the device-registration endpoint is used.
- Support communications: information you include in an email or WhatsApp message to support.
- Administration records: administrative audit entries, uploaded chart imagery and operational logs.
- Browser preferences: dashboard theme preference under
eqyera.dashboard.theme, and authentication state in browser storage. - Public-site measurement: some public pages include a Meta Pixel that may send page-view and browser/device information to Meta. The current owner/consent approach for this measurement requires confirmation.
3. How information is used
- To create and authenticate accounts.
- To provide research access and enforce subscription boundaries.
- To process and verify payments and maintain payment and subscription records.
- To operate referrals, account support and administrative audit records.
- To send transactional email or push notifications where a configured service is used.
- To operate, secure and troubleshoot the website and application.
- To measure public-page visits where Meta Pixel is present, subject to the owner's approved consent approach.
4. Service providers and sharing
The current application uses or can use these service categories:
- Razorpay for payment processing and payment-status verification.
- Meta Pixel on some public pages for page-view measurement.
- Firebase Cloud Messaging for push-notification delivery where configured and a device token is registered.
- Email/SMTP infrastructure for transactional email.
- Hosting and infrastructure providers that operate the application, database and logs.
We do not claim that no data is shared. Provider contracts, processing locations and any additional subprocessors require owner/legal confirmation and should be listed here when finalized.
5. Browser storage and cookies
EQYERA uses browser local storage for account session state and the dashboard theme preference. The public site may also load third-party measurement scripts as described above. The current code does not present a consent-management interface; the final consent and cookie approach requires owner/legal approval.
6. Retention and security
Account, payment, referral, audit and log records are retained as needed to operate the service, meet accounting and security needs, and resolve disputes. A definitive retention schedule is not yet stated here and requires owner/legal approval.
Passwords are stored as bcrypt hashes, access tokens are stored as hashes for revocation checks, and access to paid research is enforced by the server. No internet service can promise absolute security. Do not send passwords, card details or sensitive personal information through email or WhatsApp.
7. Requests and account deletion
You can contact support to request access, correction or deletion of your account information. Requests may require identity verification and may be limited by legal, accounting, security or dispute-resolution obligations. This build does not expose an automatic account-deletion endpoint, and this policy does not promise an automatic deletion timeframe.
8. Policy review
This draft is not a representation of GDPR, DPDP or any other statutory compliance. Applicable law, controller identity, lawful basis, retention periods, cross-border processing, consent withdrawal and grievance contacts must be confirmed by the owner and legal adviser before publication is treated as final.