Security Built Into Every Part Of Mero.

Every record in Mero belongs to exactly one business. The database checks that on every read and every write — not the screen, not the app server — so a request for another business's data returns nothing, whoever sends it.

• —Row-level security on every business table
• —Your signed-in session carries the one business you are working in
• —Switching businesses is an explicit act, checked against your membership

Four roles — Admin, Inventory Manager, Sales Associate and Accountant — decide what each team member can see and do. Cost and sell prices are hidden by role in the database itself, so a sales associate never sees what a piece cost, through any screen or question to the assistant.

• —Permissions checked by the database on every action
• —Cost and margin hidden from roles that should not see them
• —Unlimited team members, each with their own sign-in

Each person signs in with their own account, and new accounts confirm their email address before they can use it. Every connection to Mero is encrypted in transit over HTTPS, and data is encrypted at rest by our database provider. Especially sensitive values — such as the keys a business lends Mero to read its old system during a migration — are encrypted again inside the database.

• —Email confirmation on every new account
• —HTTPS everywhere
• —Credentials for connected systems encrypted at the application level

When a customer pays an invoice, they enter their card or bank details on Stripe, not on Mero. Mero never sees or stores card numbers or bank account details. Each pay link is a long, unguessable address that opens one invoice, can only start a payment, and is kept out of search engines.

• —Stripe processes and holds all payment details
• —Payment events are accepted only when Stripe's signature checks out
• —Refunds and disputes recorded against the invoice they belong to

Mero's agents and assistant prepare work; they never commit it. Sending an order, changing stock, recording a payment or writing imported data waits for a person who holds the right permission, and that permission is checked again at the moment the change is made, not only when it was approved.

• —Every agent action logged, with the approval behind it
• —The assistant reads only the business you are signed in to
• —It can read who has access, and can never change it

Changes to the records that matter are captured in an audit log with who made them and when, and stock is never edited in place: every movement in or out is its own entry, so the count on hand can always be explained. Pieces with history are archived, never deleted, and any import can be undone.

• —Append-only stock history
• —Audit trail on operational records
• —Any import can be undone