YOM

Acceptable Use Policy

Last updated:

This policy is part of the Terms of Service between you and the company that runs YOM for you: Aapastech Private Limited if you are in India, Aapastech OÜ if you are in the European Union or the United Kingdom, and 14818032 Canada Inc. everywhere else (“we”, “us”). It applies to every account, project, key, token, portal and integration of YOM (Your Own Metrics). Capitalised words have the meaning given in the Terms.

1. Scope

You are responsible for everyone who uses the Service through your account or keys, including your team, your clients and sub-tenants, people who log in to a client portal you create, and any agent or software acting with your credentials.

2. Lawful tracking only

You may use YOM to collect or process information about a person only if you:

  • have a lawful basis or valid consent for that collection under the laws that apply to you and to them;
  • give the notices those laws require, including a privacy notice that discloses your use of analytics and of any destination you forward data to; and
  • honour opt-outs and consent choices.

You must not:

  • configure YOM, or alter its SDK or requests, to defeat a visitor’s consent choice, Global Privacy Control signal or Do Not Track setting where the law requires you to honour it; or
  • use YOM to identify, re-identify or fingerprint individuals who have not consented, or combine YOM data with other data to do so.

3. Sensitive data

Unless we have agreed otherwise in a document signed by both parties, you must not send YOM:

  • health information, including protected health information under HIPAA, or events from pages that reveal a person’s health condition, treatment or appointment;
  • special categories of personal data or sensitive personal information under any applicable law, such as racial or ethnic origin, political opinions, religious beliefs, union membership, genetic or biometric data, sex life or sexual orientation, precise geolocation, or immigration status;
  • government identification numbers, financial account or payment card numbers, passwords or security credentials;
  • personal information of children under 13, or under 16 where a higher age applies, or from services directed at children;
  • any data whose processing would require us to hold a certification, licence or agreement we do not hold.

YOM scrubs some personal-looking parameters from browser events as a safeguard. That safeguard does not make it acceptable to send the data above, and it does not apply to server events you send.

4. Prohibited content and purposes

You must not use YOM, including portals, embeds and email reports, to:

  • break any law or regulation, or help anyone else do so;
  • measure, promote or support illegal goods or services, fraud, phishing, malware or scams;
  • host, send or link to content that is unlawful, infringing, defamatory, harassing, hateful, or sexually exploits minors;
  • send spam, or send email reports to people who have not asked for them;
  • infringe anyone’s intellectual property or privacy rights;
  • conduct surveillance of individuals, or track employees or other people in breach of applicable law;
  • make decisions with legal or similarly significant effects on individuals (such as credit, housing, employment or insurance eligibility) based on YOM data;
  • build or benchmark a competing product, except for ordinary evaluation.

5. Abuse of the service

You must not:

  • access or try to access another customer’s data, account, project or sub-tenant, or circumvent key scopes, sub-tenant bindings, origin allow-lists or embed-token limits;
  • probe, scan or test the vulnerability of the Service except as allowed by our security disclosure policy;
  • interfere with or disrupt the Service, including denial-of-service attacks, flooding ingest endpoints, or sending deliberately malformed or excessive events;
  • use the Service to send traffic to, or attack, a third party, including through webhook or warehouse destinations;
  • reverse engineer the Service, except to the extent the law allows despite this restriction;
  • share, publish or embed secret keys or management keys in client-side code, or resell access to the Service except as part of your own product or client service under the Terms;
  • create accounts by automated means or to evade a suspension or plan limit.

6. Rate limits and fair use

The Service enforces rate limits, request-size limits, plan quotas and per-project caps (for example on events, destinations, portals, exports and scheduled reports). Published limits may change as the Service evolves. You must not work around a limit, for example by splitting one workload across many free accounts. If your use puts the stability of the Service at risk, we may throttle or queue it while we talk to you.

7. Enforcement

If we reasonably believe you or your users have breached this policy, we may remove content, disable keys, tokens, portals or destinations, stop processing specific data, suspend the account, or terminate under the Terms. Where practical and lawful we will tell you first and give you a chance to fix the problem. We may act without notice where needed to prevent harm, to comply with law, or to protect the Service or other customers. We may report unlawful activity to the authorities.

8. Reporting misuse

Report suspected misuse of YOM to contact@aapastech.com. Complaints are handled by our Grievance Officer. Report security vulnerabilities as described in our security disclosure policy.