Atlayo Mini-App Operation Rules

Last updated: 21 July 2026 · Effective: 21 July 2026

These rules apply to all mini-apps submitted to the Atlayo Compass marketplace. They are based on industry practice adapted for EU law and Atlayo’s architecture. Violations may result in rejection, removal or developer account suspension.

1. Basic information

1.1 Name, description and icon

• Must accurately describe functionality — no vague marketing fluff only.
• Must not infringe trademarks or impersonate Atlayo, public bodies or other brands.
• Must not use prohibited superlatives (“#1”, “official”) without proof.
• Icon must be clear, recognisable, and match the service; no Atlayo logos unless authorised.
• Category and tags must match actual services provided.

2. Service category

• Choose the category that matches your core service. Game categories may have additional restrictions.
• Core pages must deliver the declared category without excessive redirects.
• Links in category submission must work and contain lawful content.

3. Functionality and quality

• Submitted builds must be complete — not crash, blank, or “coming soon” only.
• All declared features reachable within two taps from the home screen.
• Provide test credentials if login is required.
• Must deliver genuine utility — not a single static page unless that is the entire product.
• Must not replicate core Atlayo client features (full messaging, social feed clone).
• Must not force users to follow other accounts or install external apps to use basic features.

4. Content standards

• No illegal, pornographic, violent, hateful or fraudulent content under EU law.
• No fake payments, fake red envelopes, or misleading “official” promotions.
• No gambling or prize draws prohibited in target countries.
• No fortune-telling or superstitious “test” content presented as factual.
• Marketing must not exceed 50% of functional screen area with floating ads.
• No inducement to share, follow or rate in exchange for rewards (forced viral loops).
• User-generated content services must provide moderation and reporting tools.

5. Privacy and data

• Collect only data necessary for stated purposes; obtain consent before sensitive APIs.
• Must not ask users to enter Atlayo passwords inside the mini-app.
• Must not display other users’ data without their authorisation.
• Must provide account deletion inside the mini-app if you operate accounts.
• Must filter illegal content (CSAM, terrorism, etc.) if UGC is allowed.
• Location tracking requires clear opt-out instructions.

6. Technical standards

• Use Atlayo UI components where required for consistency.
• No auto-playing video or audio without user gesture.
• No downloading or executing external native code outside approved APIs.
• No dynamic code loading that bypasses review.
• Pop-ups and overlays must be closable.
• Must not mimic system alerts or Atlayo security prompts.

7. Payments

• Digital goods and services in mini-apps must use the developer’s own payment processor — not Atlayo Pay or Atlayo-operated billing.
• Mini-apps may request the card autofill API to pre-fill checkout fields only with explicit user permission; they must not store card tokens.
• Physical goods and real-world services may use approved payment flows with clear pricing in EUR/CZK/GBP/USD as supported.
• Refund policies must comply with EU Consumer Rights Directive where applicable.

8. Common rejection reasons

9. Verification

Certain categories (finance, health, children, news) require enhanced verification and may need local licences. We publish an updated category list in the Developer Portal.

10. Appeals

Rejection reasons are shown in the portal. Appeal within 14 days at developers@atlayo.com with your app ID and changes made.