This page is a section skeleton, not an agreement. Ritla’s operating entity is not registered yet, so there is no company for a policy to bind, and nothing on this page creates one.
Every {{TOKEN}} below marks a blank that one find-and-replace closes once that entity exists. Until it does, read the headings as an outline of what the finished document will say rather than as what it says.
In the meantime, anything you would use these documents for — a request for a copy of your data or its deletion, a refund, a question about what a scan stores — goes to hello@ritla.app and is handled by a person.
Terms of Service
What Ritla will agree to and what it will ask of you. Each heading below is a clause the finished document will carry; the text under it is what that clause will have to address.
- 01
Who this agreement is with
Names the company that operates Ritla and stands behind every clause below, with its trade licence and registered address, so the counterparty is a legal person rather than a brand: {{ENTITY_NAME}}, licence {{ENTITY_REG_NO}}, registered at {{ENTITY_ADDRESS}}.
- {{ENTITY_NAME}}
- {{ENTITY_REG_NO}}
- {{ENTITY_ADDRESS}}
- 02
What the service is
Describes what is actually being bought: a deterministic scanner that crawls a site you nominate, runs a fixed set of Arabic and RTL checks across breakpoints, and returns a scored report with screenshot evidence and selectors. It states just as plainly what the service is not — a diagnostic, never a certification that a law, standard or contract has been satisfied.
- 03
Accounts and access
How an account is created and signed into, the consequence of sign-in being an emailed link (the mailbox is effectively the credential, so its security is yours), your responsibility for whoever you admit to a workspace, and what becomes of a workspace when its last member leaves.
- 04
Acceptable use
The short list of things that suspend an account: attacking or reverse-engineering the scanner, evading rate limits or plan quotas, pointing the crawler at a target as a load generator, and reselling raw output as your own product where the plan does not permit it.
- 05
Scanning sites you do not own
The clause this product needs more than most. It requires that you hold authority to scan every URL you submit, sets out how the crawler behaves toward a target (page budget, robots directives, request volume, identifying user agent), and places the consequences of scanning someone else's site with the person who submitted the URL.
- 06
Plans, payment and renewals
Prices, billing periods, renewal, taxes, and what happens when a payment fails. This section is written last on purpose: nothing is charged during the closed beta and no payment provider is connected, so its content depends on {{ENTITY_NAME}} completing merchant onboarding. The refund commitment is a separate document.
- {{ENTITY_NAME}}
- 07
Availability, changes and support
What uptime is and is not promised at this stage, how maintenance is handled, and — the clause specific to a rule engine — that re-tuning a rule can move your score between two scans of an unchanged page. That is intended behaviour and needs saying out loud rather than being discovered. Support response by plan lands here too.
- 08
Liability and disclaimers
The honest limits of a deterministic scanner: findings are advisory, a clean report is not a warranty that your Arabic surface is correct for your readers, and there is a cap on what can be recovered. Indemnity for third-party scanning is cross-referenced from section 5.
- 09
Suspension and termination
How either side ends the relationship and on what notice, what happens to your scans, reports and stored screenshot evidence afterwards, and which clauses survive termination.
- 10
Governing law and disputes
The law this agreement is read under and the forum that hears a dispute about it: {{GOVERNING_LAW}}, with venue in {{ENTITY_JURISDICTION}}. Both follow from where the entity is registered, which is exactly why both are blank.
- {{GOVERNING_LAW}}
- {{ENTITY_JURISDICTION}}
- 11
Changes to these terms
How a change is announced, how much notice it carries, and the version and effective date printed on the document. This copy carries none, because it is not in effect: {{EFFECTIVE_DATE}}.
- {{EFFECTIVE_DATE}}
- 12
Contact
Where a question about these terms goes: hello@ritla.app. That mailbox is the contact route for all three documents until the entity has a registered address to receive service at.