⚖ Draft — describes current system behaviour, pending legal review.
This page states what the platform actually does today, verified against the running system. It has not been reviewed by counsel. It is published because a service that takes payments should say its terms plainly, and because an honest draft is better than a borrowed template describing software this is not.
Rivet accepts service requests under a contract, dispatches technicians, records the work, and moves payment between client, technician and platform. Contracts define scope and rates between the parties named in them.
Charges are made against a contract for work recorded in the system. Refunds may be issued in full or in part against the original charge. Charge and refund operations are idempotent: a repeated request returns the original outcome and cannot charge or refund twice. Card details are handled by the payment processor and never reach Rivet's servers.
Technicians sign themselves up and accept dispatched jobs. Earnings accrue per completed job and are paid from the same ledger that records the client charge.
Dispatch, contract and payment events are written to an append-only audit record. Entries are not edited after the fact; corrections are added as new entries, so the history of a job remains reconstructable.
The service is provided as-is while in commercial pilot. No uptime guarantee is offered at this stage; a contract may state one.
← BackHome · Pricing · About · How it is built · Contact · Terms · Privacy · Sign up