Authority and ownership
You must have authority to submit the app, code, trademarks, content, privacy notice, and support contact. App IDs and organization access may not be sold or transferred outside the Console ownership flow.
Agreement version 2026-07-22
Developer platform rules.
These rules apply to every organization, release, collaborator, and Mini App distributed through Textxt. An organization owner or admin must accept this exact version in Developer Console.
Effective July 22, 2026Developer agreement
User trust
Request only necessary permissions, explain user-visible actions, honor denial, and never misrepresent Textxt approval. Do not auto-send messages, upload data, or create content without clear user intent.
Privacy and data
Publish accurate privacy and support pages. Collect the minimum data needed, use your own authentication for your backend, provide deletion controls, and comply with applicable privacy and child-safety laws.
Operations
Maintain a monitored support and security contact. Fix critical vulnerabilities promptly. Textxt may disable, unpublish, or roll back a release to protect users or platform reliability.
Prohibited apps and behavior
- Malware, credential theft, cryptomining, hidden downloads, obfuscated remote execution, or service-worker persistence.
- Harassment, exploitation, non-consensual intimate content, illegal goods, dangerous instructions, fraud, impersonation, or deceptive monetization.
- Undeclared tracking, fingerprinting, data brokerage, scraping Textxt, or sending chat data to a third party without a clear purpose and notice.
- Bypassing the Bridge, directly accessing Textxt databases, framing credential pages, loading executable code from undeclared origins, or evading review with mutable files.
- Copyright, trademark, privacy, publicity, or other rights violations.
Review and enforcement
| Stage | Platform action | Developer responsibility |
|---|---|---|
| Automated verification | Checks manifest, HTTPS/DNS, redirects, CSP, iframe policy, same-origin executable files, unsafe patterns, size, and digest. | Publish a versioned, immutable release that passes every check. |
| Human review | Targets five business days and records approval or actionable rejection notes. | Provide a functioning mobile experience, accurate disclosures, and test access when needed. |
| Release | Creates an immutable release and may use staged rollout, health checks, rollback, disable, or unpublish. | Monitor metrics and errors, answer support requests, and submit a higher semantic version for changes. |
| Enforcement | May restrict an app, organization, or account for safety, legal, security, or repeated quality violations. | Stop affected processing and cooperate with remediation or appeal through support. |
Default quotas
Current machine-readable limits are published at /mini-apps/platform-policy.json. Defaults include 25 organization members, 50 apps, 10 pending reviews, 10 submissions and 25 invitations per day, 24 executable files, 1 MB per file, and 6 MB total executable release size. Limits may be lowered during abuse or raised after support review.
Executable review archives are retained for at least 365 days. Active, candidate, and current rollback-target archives are extended automatically. Release metadata and review decisions remain auditable after an expired executable archive is removed.