Privacy Policy

Publisher: Vlemon LLP · Contact: privacy@vlemon.com

This Privacy Policy applies to internal, local-development, staging, and QA hostnames operated by Vlemon LLP — including but not limited to dev.vlemon.com, dev.mayanksanghvi.com, dev.mayankmode.com, origindev.vlemon.com, devorigin.vlemon.com, and any other current or future hostname whose dev-style label marks it as a non-production, internal-only environment on a domain Vlemon LLP controls. These are not public products — they are internal tools, work-in-progress builds, and test/staging deployments used by Vlemon LLP personnel, contractors, and authorized automated agents/service accounts. This policy operates alongside Vlemon's master Common Legal Terms.

1. Scope exclusion — OmniSnap.dev

This policy does not cover omnisnap.dev or any of its subdomains. OmniSnap.dev's .dev top-level domain is a permanent product brand, not an environment indicator — it is a real, production, public-facing product with its own dedicated legal pages.

2. Who this is for

Access to environments covered by this policy is restricted to Vlemon LLP employees, contractors, and authorized automated agents/service accounts. These hostnames are not intended to be used by, or to collect data from, members of the public or end customers. If you are a customer or member of the public and have reached one of these hostnames, it was not meant to be public-facing — please contact support@vlemon.com and do not enter personal or payment information.

3. Data we process

Because these are development/testing environments rather than production services, data handling can vary build to build. In general:

• Authentication data — sign-in identity (e.g. Microsoft Entra ID / OAuth account identifiers) for personnel and service accounts accessing the environment, used solely to gate access.
• Diagnostic and telemetry data — request logs, error/crash traces, and performance metrics used to build and debug the product. This data is anonymized where practical, contains no PII or business payloads beyond what's needed for debugging, and is used solely to troubleshoot and improve software under development.
• Test/synthetic data — data entered for the purpose of testing a feature. Real production customer data should not be copied into a dev/staging environment; where it unavoidably is (for example, a sanitized production snapshot for QA), it is handled under the same safeguards as production and deleted once no longer needed for testing.

We do not use data from these environments for advertising, and we do not sell or share it with third parties for marketing.

4. No availability or retention guarantee

Development and staging environments can be reset, wiped, redeployed, or taken offline at any time without notice. Do not rely on data stored in an environment covered by this policy persisting, and do not use these hostnames to store data you need retained.

5. AI & automated output verification

Where an internal/dev tool uses AI, machine learning models, or automated code/script generation, outputs are produced at the operator's direction and must be reviewed and verified before being relied upon or promoted to production.

6. Children's privacy

These environments are internal engineering tools, not directed at children, and are not intended to knowingly collect data from children under 13.

7. Compliance

See our company-wide GDPR Compliance page for data subject rights available to EEA/UK individuals. Shared Common Terms: /legal/common-terms.

8. Changes

We may update this policy as internal tooling and environments change; the effective date above will be revised.

9. Contact

Privacy questions: privacy@vlemon.com
Legal: legal@vlemon.com