Security
How Reinfluence protects your business and your customers.
Sign-in, roles, records, money and keys, as they work in the product.
Sign-in
How passwords, sessions and till codes work.
- Passwords are stored only as salted scrypt hashes, never as text.
- A sign-in session is a random token. Only a hash of it is kept on the server.
- Repeated wrong passwords are rate limited by address and by account.
- Tellers and waiters sign in at the till with a business code, a staff ID and a till code. Five wrong codes lock that person for 15 minutes, and a manager can issue a new one at once.
- Owners and managers cannot use a till code. They always sign in with email and password.
Who can do what
Each person has a role that limits what they can see and do.
- Staff roles from owner to cashier, with server and kitchen roles for restaurants.
- Only owners change settings and integrations. A manager cannot create an owner.
- Voiding a sent line or cancelling an order needs a supervisor and a reason.
- Invitation links work once, expire, and can be revoked. A QR invitation expires in 24 hours and can never grant the owner role.
- Removing a person ends their access at once while their past orders keep their name.
Your records
Each business sees only its own records.
- Every record belongs to one business, and every query is limited to the signed-in business.
- An audit log records orders, voids, payments, team changes, till sign-ins and account changes, with who did them and when.
- Tax settings are copied onto an order when it opens, so changing a setting later never rewrites an old invoice.
- Invoice and receipt links are long random addresses that search engines are told not to index.
Money
How totals, payments and tips are calculated and stored.
- Amounts are kept as whole numbers in the smallest unit, so there is no rounding drift.
- Totals are always calculated on the server from the order's lines. A till can never send its own total.
- A payment sent twice is recorded once. Retries after a dropped connection are safe.
- Card details never pass through Reinfluence. The card machine or Olympus Pay handles them, and we keep the approval code.
- Tips are recorded apart from sales and tax. A company charge is refused when it would pass the account's credit limit.
Keys and connections
How saved keys, webhooks and API access are protected.
- Saved Olympus Pay keys are encrypted with AES-256-GCM and are never shown again.
- Webhooks from Olympus Pay are checked against a signed secret before they are believed.
- A device or API key belongs to one outlet, has only the scopes you give it, and is limited to 180 requests a minute.
- Table QR codes can be replaced one at a time. The old code stops working immediately.
Audits and certifications
Reinfluence has not yet had an independent security audit and holds no compliance certification. The software it is built on is listed under Licenses.
Questions about security?
Write to security@olympuspay.co and we will answer, or read how we handle privacy and data in the Trust Center.
