To maintain platform integrity, prevent impersonation, and ensure clarity for all users interacting with applications hosted on the Mayson platform, this Subdomain Policy establishes clear rules governing the creation, usage, and potential reclamation of subdomains issued under the mayson.app domain.
1. Purpose of Subdomain Governance
Subdomains created within the Mayson ecosystem represent publicly accessible endpoints that may be interpreted by users as official platform resources.
Improper naming practices can lead to:
User confusion,
Brand impersonation,
Security risks, and
Misrepresentation of platform authority.
This policy exists to protect both platform users and application builders by ensuring transparent ownership and responsible subdomain usage.
2. Misleading or Impersonating Subdomains
Mayson strictly prohibits the registration or use of subdomains that may falsely suggest affiliation with, endorsement by, or official operation of Mayson or its internal services.
We reserve the unrestricted right to review, suspend, rename, or reclaim any subdomain that:
Attempts to impersonate official Mayson products, infrastructure, or departments;
Creates confusion regarding platform ownership or operational authority;
Mimics internal system environments or administrative services;
Misleads users into believing they are interacting with an official Mayson interface.
Examples of prohibited or reclaimable subdomains include (but are not limited to):
cloud.mayson.appprivacy.mayson.appsecurity.mayson.appsupport.mayson.appadmin.mayson.appbilling.mayson.app
The above examples are illustrative only and do not represent an exhaustive list of reserved names.
3. Reserved and Generic Platform Terms
Certain keywords are inherently associated with platform infrastructure, trust signals, or organizational authority. Subdomains containing such generic or system-level terminology may be restricted or reclaimed at Mayson’s discretion.
Users must avoid registering names that:
Imply ownership or governance of the Mayson platform;
Represent core operational systems;
Suggest verification, certification, or official status;
Create perceived platform-wide legitimacy.
Discouraged or Reserved Examples:
official.mayson.appsystem.mayson.apptrust.mayson.appplatform.mayson.appcore.mayson.app
Mayson may maintain an internal reserved list that evolves over time without prior notice.
4. Recommended Subdomain Naming Practices
Users are encouraged to select subdomains that clearly represent their own identity, organization, or project, ensuring transparency and minimizing user confusion.
Preferred naming conventions include:
Personal identity or username
rahul.mayson.appalex-dev.mayson.app
Company or startup branding
my-startup.mayson.appacme-tech.mayson.app
Project or application names
project-alpha.mayson.appinventory-dashboard.mayson.app
Choosing brand-specific identifiers strengthens credibility and helps users clearly distinguish independent applications from official Mayson services.
5. Subdomain Reclamation Rights
Mayson retains the ongoing right to reclaim, reassign, restrict, or disable any subdomain when necessary to:
Protect platform users,
Preserve brand integrity,
Prevent abuse or fraud,
Enforce evolving security standards, or
Reserve names required for future platform features or services.
Reclamation may occur with or without prior notice, particularly in cases involving security concerns, impersonation, or policy violations.
Where feasible, reasonable efforts may be made to notify affected users and provide guidance for migration to a compliant subdomain.
6. User Responsibilities
By registering or using a Mayson subdomain, users agree to:
Select names that accurately represent their ownership;
Avoid deceptive, confusing, or authoritative terminology;
Maintain honest representation of their services;
Promptly comply with any remediation requests issued by Mayson.
Failure to comply may result in suspension of services, reassignment of the subdomain, or additional enforcement actions under applicable platform policies.
7. Policy Updates
Mayson may modify or expand this Subdomain Policy periodically to address new security risks, product expansions, or ecosystem changes. Continued use of a Mayson subdomain constitutes acceptance of the latest policy version.