SeOMeter.in treats privacy and security as ongoing responsibilities. This page explains the safeguards we aim to apply, shared responsibilities, data lifecycle and what happens if a security concern is reported. It should be read with the Privacy Policy and Terms of Service.
1. Security principles
We aim to protect information using reasonable technical and organizational measures proportionate to the type of data and the risks of the Services. Security is a process, not a promise of perfect protection. The internet, third-party services and software systems can contain vulnerabilities, and no security statement should be interpreted as a guarantee that loss, misuse, intrusion or downtime can never occur.
Our intended principles include limiting access to information based on operational need, maintaining reliable account and payment records, protecting systems against unauthorized activity, reviewing errors and abuse signals, and responding to credible security reports. The precise controls that are live at any moment depend on the actual infrastructure and configuration.
2. Safeguards and implementation accuracy
Depending on the deployed environment, appropriate safeguards may include HTTPS/TLS for data in transit, authentication and permission checks, restricted administrative access, secure secret storage, input validation, rate limiting, dependency updates, backups, logging and monitoring, separation of production access, and recovery procedures. These are examples of safeguard categories, not a certification or a representation that every listed control has been independently audited or is enabled in every component.
SeOMeter.in does not claim ISO 27001, SOC 2, penetration-test certification, end-to-end encryption, a particular encryption standard for all stored data, or a guaranteed recovery time unless a separate current evidence-backed statement expressly says so. Do not rely on this page as an independent security audit.
3. Access, accounts and workspaces
Access to account and workspace information is intended to be limited through authentication and applicable role or permission settings. Organization administrators may have access to members, project settings, report content or other workspace information according to the product's permission model. Administrators should invite only appropriate members, assign the least privilege necessary and promptly remove access when a person leaves the organization.
Users should use a unique, strong password where passwords are used, secure the email account that receives authentication messages, avoid public/shared devices for sensitive work, sign out from shared devices and never disclose one-time codes. Report suspected account compromise promptly. Role-based controls reduce risk only when correctly implemented and configured; they do not replace an organization's own access review.
4. Payment security
SeOMeter.in uses Cashfree for payment processing. Payment credentials are handled by the payment provider and relevant payment rails. SeOMeter.in generally needs transaction identifiers, amount, status, plan and billing information to reconcile a subscription, issue receipts, process refunds and respond to a dispute. The actual fields retained depend on the deployed integration.
Support will not need your card PIN, card CVV, bank password, UPI PIN or one-time password to troubleshoot an account. Never send those secrets by email, chat or a support form.
5. AI and service providers
Some AI-assisted features may send relevant prompts, URLs, page text or report context to a third-party AI provider, including OpenAI, to complete the requested operation. Hosting, email, payments, monitoring or other providers may also process information as needed for their functions. Provider terms, processing locations, retention settings and contractual safeguards can differ.
Before submitting sensitive, confidential or personal information, consider whether the tool needs it and whether you have authorization. Avoid putting passwords, secrets, private keys, customer records or unrelated personal data into a URL or prompt. The Privacy Policy explains the categories of data and types of sharing in more detail.
6. Report expiry and deletion lifecycle
- Temporary reports: reports not saved to a project are designed to expire after 72 hours.
- Saved project reports: saved reports remain under the relevant project/account rules until deleted or otherwise handled under a valid retention rule.
- Account closure: we aim to delete or de-identify relevant account and report data within 90 days after account closure, subject to legal, security, financial, dispute and backup exceptions.
- Billing and security records: some records may be retained longer where required for tax/accounting, fraud prevention, investigation, legal claims or compliance.
These are retention targets rather than a guarantee that a specific record has been removed from every replica or backup. Users can start available deletion actions in account settings or contact support for assistance.
7. Security incidents and breach response
If SeOMeter.in becomes aware of a credible security incident, the intended response is to assess the report, restrict or contain the affected activity where feasible, investigate the likely scope, preserve relevant evidence, take corrective action, and notify affected users or competent authorities where required by applicable law. The exact response depends on the facts, severity, affected data, provider involvement and legal obligations.
Certain cyber incidents may trigger reporting obligations to India's Indian Computer Emergency Response Team (CERT-In) under applicable directions, including a six-hour reporting timeline for specified covered incidents. Other data-protection laws may impose separate obligations, recipients, contents and timelines. The 72-hour expiry for temporary reports is unrelated to a breach-notification deadline. This page does not assert that a formal incident-response programme has been independently audited or that every event can be detected immediately.
If you suspect a security vulnerability or unauthorized disclosure, email support@seometer.in with the subject “Security report”. Include the affected page or feature, observed behaviour, approximate time and a safe description of the issue. Do not include other users' data, exploit the issue further, disrupt the service or publish sensitive details before there is a reasonable opportunity to investigate. Do not send passwords, tokens or live secrets in the first email.
8. What you can do to stay safe
- Use only domains and checkout screens associated with
seometer.inand the genuine payment flow. - Use unique credentials and keep your email account secured.
- Give workspace members only the access they need and review membership regularly.
- Review submitted URLs and prompts for confidential content before running analysis or AI features.
- Download or save important reports you need for your own records; do not assume temporary reports will persist.
- Report unexpected login, billing, permission or deletion behaviour promptly.
9. Availability, backups and recovery
Backups and recovery processes, where present, are intended to reduce the impact of technical failures. They cannot guarantee that every item can always be restored or that all downtime can be avoided. Restoration may return an older state, and deletion from a live database may not be reflected immediately in an isolated backup before its rotation expires. We will handle recovery and retention consistently with applicable law and our disclosed data lifecycle.
10. No absolute security guarantee
We do not represent that any system is completely secure or invulnerable. To the extent permitted by law, we disclaim guarantees that cannot reasonably be made about the internet or third-party systems, while continuing to respect mandatory security, privacy, consumer and breach-notification duties. Nothing here limits a right that cannot lawfully be waived.
11. Contact and escalation
Security and privacy reports — SeOMeter.in
Operator and Grievance Officer: Alok Chaurasia
Email: support@seometer.in
Address: Rajendra Nagar, Gorakhpur, Uttar Pradesh, India
Please read this page together with the other SeOMeter.in legal pages.