The records are the part you see.

The warehouse sees the products, but not what you paid for them. That only means something if it holds everywhere.

• The same rules bind every grid, report and export, the API and Ask RowFold.
• You can’t get round a hidden field by writing an automation that reads it. The automation won’t save.
• Attachments are checked the same way, and never sit in a public folder.

A change can come from the grid, an import, a form, an inbound email, the API or an automation. They all go through the same door.

• Order and invoice numbers are stamped there, so a record gets its number wherever it came from.
• Automations and webhooks start from there, and only once the save has succeeded.
• History is written there too, so an import shows up in it beside a person’s edit, each labelled for what it was.

Your customers, orders and jobs are linked records, and totals are added up from every row.

• Every change is recorded: who, when, and what it said before, down to the single cell.
• Two people editing different cells of one record both keep their edits.
• A deleted record stays in Trash for 30 days, and you can put it back.

There is nothing for you to host, patch or back up.

• A new version starts beside the old one, and takes over once it is up.
• When it gets busy, it can add more copies of itself.
• Traffic is encrypted in transit, and two-factor secrets and connected-app tokens are encrypted in the database.

When somebody changes a record, it changes on your screen too, without a reload.

• In the Inbox, you can see who else has a ticket open, and when they are typing.
• A laptop that wakes from sleep catches up on what it missed.
• Rows are brought up to date in place, so your ticks and your place on the page stay put.

Automations, reminders, digests and large imports all run on their own.

• Schedules run on your workspace’s clock, not the server’s.
• A webhook that can’t get through is tried 6 times over about half an hour, and the log says what happened.
• A long wait rereads its date when its limit comes, so a chase goes out when it is due, not a month early.

Sending is the easy half. Replies have to find their way home too.

• A customer’s reply lands on the ticket it belongs to, even after that ticket was merged into another.
• Somebody who opts out stops getting those emails, and STOP works by text.
• Ticket replies can go out from your own address, once you have confirmed it and your domain’s signing checks pass.

Each has its own sign-in and its own ways of failing.

• Importing again updates the records it made, and leaves your own columns alone.
• A sync that finds nothing new writes nothing, so it doesn’t set off your automations for no reason.
• A calendar feed that stops answering never frees nights that were already sold.

Deposits, instalments and no-show fees go straight to your own Stripe account. RowFold never holds the money.

• Refunds and disputes stay in your own Stripe dashboard.
• Card details go into Stripe’s own fields, and never touch RowFold.
• Each currency is charged in its own units, so ¥1,250 stays ¥1,250.

It helps you get going, answers questions and takes on the dull parts. It isn’t what holds this up.

• It reads with your permissions, so it can’t show you what you couldn’t open yourself.
• Totals come from the database, not from the model’s reckoning.
• When you ask it to change records, it shows you the change and waits for you to confirm.

Most failures here are quiet: nothing on screen changes, and a reminder just doesn’t arrive.

• When something new breaks, RowFold’s people get an email. It never carries the error’s message, because a message can quote customer data.
• Failures in mail, texts, automations, webhooks, syncs and scheduled jobs are counted on one screen for RowFold’s staff, so a quiet one gets seen.