Skip to main content
These rules apply to everything consumers see (voucher set content, the provider profile, listing branding) and to your workspace branding. They describe what is allowed; how content is checked is not published.

​
Restricted Markdown

description and termsText fields are restricted Markdown. Allowed:
  • paragraphs and line breaks;
  • bold and italic;
  • bulleted and numbered lists, nested at most two levels;
  • headings of level 3 and 4 (###, ####);
  • links with https URLs.
Not allowed: HTML of any kind, images, tables, code blocks and inline code. Links are rendered with rel="noopener noreferrer nofollow ugc". Invalid Markdown is refused with the field code invalid-markdown.
  • Only https links; no IP addresses as hosts and no user names or passwords in URLs.
  • Links to your own registered domains (allowedLinkHosts of the voucher set, your profile’s websites) pass. Any other host, including URL shorteners, needs AllRide’s confirmation during review.
  • Custom app schemes for deep links must be listed in the set’s allowedLinkSchemes; javascript, data, vbscript, file, blob, about, http and intent are never allowed.

​
Text rules

  • No HTML, scripts or template code, and no encoded text (base64, hex or URL-encoded content).
  • No invisible characters and no characters that change the text direction.
  • No other brands’ names and no look-alike characters that imitate them.
  • Terms and descriptions must never ask customers for passwords, PINs or payment details.
  • Every text needs your partner’s default locale and stays within its length limit.

​
What happens on submit

When you submit or edit a change request, automated checks run, and AllRide reviews every change request. You see the change request’s status and, after the decision, the reviewer’s decisionReason; check results, findings and rule names are never shown. A change request with a problem is not refused when you submit it: it goes to review, and a rejection explains what to change. See Change requests and approval.

​
Workspace branding saves

Workspace branding (PUT /partner/v1/branding/workspace) needs no approval, so its texts are checked when you save. A text that breaks a rule is refused with 422 content-blocked; more.validationErrors lists one entry per field with a public reason in constraint:
Nothing is saved when a field is refused.