Billing and refunds

What this page covers

This policy sets out the financial terms of Maatron: the plans and their prices, how payment is taken, taxes, cancellation, non-payment, and what becomes of your data when a subscription ends.

It is read together with Terms of Service, whose commercial clauses it makes precise without widening them. The processing of personal information remains governed by Privacy policy and Data Processing Agreement.

It applies to plans bought self-service. A negotiated contract — the Enterprise plan — carries its own financial terms, written into that contract; where the two differ, the signed contract prevails over this page.

The plans and their prices

Two plans are bought self-service, both monthly and in Canadian dollars: Cellule, 149 CAD per month, up to five declared controllers; Parc, 399 CAD per month, up to twenty-five. Each paid period opens one month of access, and renewal is automatic until the subscription is cancelled.

The amount depends on nothing else. It does not vary with the number of users in your organization, nor with the number of files uploaded, nor with the number of analyses run. There is no usage-based billing, and the only ceiling attached to a plan is its number of controllers.

The Enterprise plan has no public price and cannot be bought from the product: it is negotiated, and it is set on the account the day a contract is signed.

The amount actually charged is checked at every release against the grid published above — currency, amount, monthly recurrence. A discrepancy blocks the deployment rather than reaching a card. A price change follows the rule in Terms of Service: at least thirty days' notice, and no retroactive effect on a period already paid.

The evaluation: fourteen days, one controller, no card

Creating an account opens a fourteen-day evaluation. It starts at sign-up, and its expiry is computed by the server — it is not declared by the client, nor negotiable from the browser.

It gives access to the same functions as a paid plan — upload, analysis, comparison, export — with a single controller.

No card is asked for, and nothing is held against a payment method. The evaluation does not exist at our payment provider: no billing record is created before your first payment attempt. There is therefore nothing to cancel, and an evaluation never turns itself into a paid subscription.

When it expires, and to the second, the account becomes read-only: no new upload and no new analysis, everything already there remaining readable. Nothing is deleted as a result.

Where payment happens, and what we never see

Payment is made by card, on a page hosted by Stripe, our payment provider. The product takes you there; the form does not belong to Maatron and never appears inside our own pages.

No card data passes through our systems, and none is kept there. Not the number, not the expiry date, not the security code: our web application contains no payment field and loads no Stripe script, and our servers keep only Stripe identifiers — that of the customer record and that of the subscription.

What Stripe receives from us is short: the email address of the account owner, the identifier of your organization, and the chosen plan. No backup archive, no cell model and no analysis result is sent to it — the three subprocessors that touch customer content are named in Data Processing Agreement, and Stripe is not one of them.

Receipts, invoices and payment reminders come from Stripe, to the account owner's email address. We issue no billing email ourselves.

Taxes

The prices quoted are exclusive of applicable taxes.

Today, no tax is added at the time of payment: tax collection is not enabled on our payment account. We therefore do not claim to collect or to remit GST or QST, because we do not.

The day that collection is enabled, the tax will appear at payment, before you confirm, and this page will be changed first. The tax obligations that fall on you in your own jurisdiction remain yours.

Refunds: there are none

No payment is refunded, not even in part. An unused month, a forgotten cancellation, a period started and then abandoned: none of these gives rise to a refund or to a credit.

The subscription is monthly and can be cancelled at any time: the maximum commitment is one month, and fourteen days of evaluation without a card come before any payment. An offer you can leave in one click does not need a refund to be fair.

A billing error is not a refund request and is not covered by the above: a double charge, an amount that does not match the grid, a charge taken after a cancellation Stripe has already recorded are defects on our side, and we correct them. Write to info@maatron.dev. Mandatory rules that cannot be waived, recalled in Terms of Service, still apply.

Cancellation

Cancellation happens in the Stripe customer portal, opened from your organization's billing screen. It belongs to the account owner, the only role entitled to commit or to stop a spend.

There is no notice period, no minimum term and no cancellation fee.

Access is kept in full until Stripe has reported the subscription as cancelled. A cancellation scheduled for the end of the paid period therefore cuts nothing before that term: our system reads the state Stripe gives it, and keeps no parallel countdown of its own.

An immediate cancellation, on the other hand, ends access immediately, and the remainder of the paid period is not refunded. If you want that remainder, choose the end of the period rather than immediate effect.

Failed payment, read-only, and your data

A declined payment does not close the account. The subscription becomes past due, and both upload and analysis stay open. An expired card is an administrative incident, not a breach of contract.

That grace period lasts exactly as long as Stripe's own retries last: we do not announce a number of days we do not decide. Once Stripe has exhausted them, or once the subscription is cancelled, the account becomes read-only.

Read-only forbids what is new, and nothing else: no new upload, no new analysis. Everything already there — uploaded backups, cell models, findings, comparisons, reports — stays readable and downloadable. This limit is more than an intention: it is verified automatically on every change to the product, by a check that puts an account into read-only and then requires its data to still exist AND to still be reachable. Both halves are checked separately — data kept but made invisible would be no better than data erased.

Read-only deletes nothing. Deletion happens only at your explicit request, or under the retention deadlines published in Privacy policy and Data Processing Agreement — access revoked immediately, erasure from live systems within thirty days, destruction of backup copies within sixty. The end of the contractual relationship opens the export window set out in Terms of Service before those tiers apply.

Paying reopens writing. The payment path stays reachable for a read-only account — it is precisely the account that must be able to pay — and there is nothing to restore, since nothing was erased. Likewise, moving to a smaller plan removes no controller: being over quota forbids adding one, never losing one.

What does not exist

There is no annual plan, no multi-year commitment, no per-user price and no usage-based billing. Nor is there any service credit: Terms of Service promises no availability figure, so no compensation is attached to one.

Changing plan is not done from the product: no function there lets an account choose its own plan. Write to info@maatron.dev, and we will arrange it.

We write this down rather than let you discover it. The day one of these exists, it will be described here, with a visible revision date.

Questions and changes

For a billing question, an error you have spotted, or a request concerning a subscription: info@maatron.dev. The full identification of the operator — [À COMPLÉTER — raison sociale] — is set out in Legal notice.

Any change to this page is published with a new revision date. A change that touches a price, a refund rule or a cancellation condition follows the notice period in Terms of Service, and never applies to a period already paid.

The governing law and the competent court are those of Terms of Service. This page exists in French and in English, with the same content; neither version is a summary of the other.