Draft · not in force

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.

Legal · draft

Refund Policy

Ritla already publishes an unconditional refund promise. This is the outline of the document that will make it enforceable, once there is a registered company to enforce it against.

Published today, on the pricing section
If your first full report surfaces nothing you think is worth fixing, email hello@ritla.app and we refund you. No form, no argument, no questions about what you tried.

The engine is deterministic, so if it found nothing worth fixing on your site, that is a fact about your site rather than a negotiation. See also the FAQ and pricing.

  1. 01

    Billing is not switched on yet

    The status, stated before anything else so the rest reads honestly: the closed beta charges nothing and no payment provider is connected, so no refund has ever been owed. The promise takes effect with the first charge, which waits on {{ENTITY_NAME}} completing merchant onboarding.

    • {{ENTITY_NAME}}
  2. 02

    What the promise covers

    Which charge the promise applies to — the subscription to the scanner — and which it does not. Project engagements such as an LTR to RTL conversion are scoped, priced and refunded under their own statement of work, and conflating the two would make an unconditional promise about work that is anything but.

  3. 03

    The window, and what happens after it

    How long after a charge a refund can be asked for, whether it covers one billing period or several, and what becomes of the scans and evidence already produced: {{REFUND_WINDOW_DAYS}}.

    • {{REFUND_WINDOW_DAYS}}
  4. 04

    How to ask for one

    Deliberately the shortest section in the document: one email to hello@ritla.app, no form, no justification. It states the little we do need (which account, which charge), how quickly a request is acknowledged, and how the money comes back — to the original payment method, through the payment provider, on that provider's timetable rather than ours.

  5. 05

    Cancelling

    How to cancel, when access actually ends, what happens to a period already paid for, and what stays readable in the dashboard afterwards. Cancelling and refunding are separate acts and the finished document will not let them blur into each other.

  6. 06

    Disputes and chargebacks

    What happens if a charge is disputed with the card issuer instead, and the short route to a person first. A promise this unconditional exists precisely so that nobody has to reach for a chargeback, and the section will say so rather than threaten.

  7. 07

    Changes to this policy

    Notice, version and effective date, plus the commitment that a change never applies backwards to a charge already made: {{EFFECTIVE_DATE}}.

    • {{EFFECTIVE_DATE}}