Your data is your business. This page sets out how Rental HQ stores your data, who can reach it, what happens when something is deleted, and which other services we send data to. Where a protection has a limit, the limit is named.

Infrastructure

Rental HQ runs on Google Cloud Platform in the europe-west2 (London) region. The database, the application and your uploaded files are all held there. Some features send data to other services, which is set out in Data Residency & Third Parties below.

  • Cloud SQL PostgreSQL 16: Managed database with automatic patching and maintenance
  • Cloud Run: Serverless containers that scale automatically and are isolated per request
  • Encryption at rest: Google Cloud encrypts data at rest by default, using AES-256 and Google-managed keys, across Cloud SQL and Cloud Storage
  • Encryption in transit: The app and the API are served over HTTPS only, with HTTP Strict Transport Security set on every response
  • Private file storage: Job attachments, message attachments, client documents and the documents you add to an item are held in a separate bucket with public access prevented, and are only ever handed out as signed links that expire after an hour. Product photographs, vehicle photographs, company logos and profile pictures are on a publicly readable bucket, because they are meant to be shown on quotes, storefronts and warehouse screens. The photo you upload, paste or link for a product is also kept, in the private bucket, for that product alone, with the location and device details a camera writes into it taken out and not stored; only the processed picture is on the public bucket.
  • Files are checked before they open: a file added to a job on the web or in the latest Mac app is held until it has been checked, with a virus scan for documents, drawings and show files, and for pictures, video and audio up to 200 MB. A file that fails the check is removed, and nobody can open it.

Tenant Isolation

Rental HQ uses Row Level Security (RLS) in PostgreSQL to keep one company's data apart from another's. This means:

  • Every table that holds your operational records carries a company identifier: products, assets, jobs, contacts, allocations, quotes, invoices, rates, messages, files and the rest
  • A policy on each of those tables restricts every query to the company the signed-in user belongs to. The database applies it, not the application code, so a mistake in a query cannot widen it
  • The tenant is taken from the signed-in user's token on every request. A company identifier sent by a browser or an app is never trusted

Two limits are worth stating plainly. A small number of account-level tables are read on paths that run before the company is known: the user and company records themselves, device tokens for push notifications, accounting connection records, and the token lookups behind a public quote-approval or upload link. Those are filtered by the application rather than by the database. And a few tables are shared between companies on purpose, which the next section covers.

What Is Shared Between Companies

Not everything in Rental HQ is private to one company, and the exceptions are deliberate rather than accidental.

Product photographs. Rental HQ keeps one shared catalogue of product images, keyed on manufacturer and model. Every hire company in the country stocks the same SM58, so a picture Rental HQ finds for a product is there for every company that adds it after. Pictures go into it only when Rental HQ finds them: a photo you upload, or bring over from your old system, is not added to it. Each entry holds a normalised manufacturer and model string and a link to the processed image, and nothing else. There are no customer names in it, no pricing, no stock levels and nothing about how you run your business. We do record which company each entry was added for, so that we can find and remove one that should not be there. That record is never shown to other companies.

Community place reviews. Reviews of venues and hotels are a community feature and are visible to every Rental HQ company, along with the name and profile photo of the person who wrote each one. They are also served on a public endpoint, so write a review on the basis that anyone may read it. You can only edit or delete your own. Nothing else about a venue is shared: your jobs there, your rates, your contacts and your notes stay private.

The hazard library. The shared library of hazards and control measures used for health and safety documents is reference content maintained by us. Customers do not write to it, and it holds no company data.

Everything else is yours alone.

Authentication

Rental HQ uses Firebase Authentication, run by Google, for all user sign-ins.

  • We never see your password: It goes from your browser or app straight to Firebase, which handles the sign-in. Rental HQ has no password field in its database and no password-handling code of its own, so there is nothing for us to store, log or leak.
  • Token-based auth: Firebase issues a signed JSON Web Token, which our API verifies on every single request
  • Session management: Tokens expire and refresh automatically. Browser sessions have a hard seven-day ceiling, so signing in on a shared or borrowed computer cannot leave an open session behind indefinitely. The installed crew apps are exempt from that ceiling by design, because they are on a device someone carries.

Automated Backups

Your data is backed up automatically every day. No action is required on your part.

  • Daily automated backups: Taken every night at 02:00 UTC and retained for 14 days
  • Point-in-time recovery (PITR): We can restore your data to any specific second within the last 7 days using continuous transaction logs
  • Deletion protection: The database instance itself cannot be accidentally deleted, even by administrators

In a disaster scenario, we can restore the entire database to any point in the last 7 days with second-level precision. For the previous 14 days, we can restore from the nearest daily snapshot.

Deletes & Recovery

Most deletes in Rental HQ are soft. The record is marked as deleted and disappears from every list, search and report, but the row stays in the database and our support team can put it back. Products, assets, jobs, contacts, allocations, categories and messages all work this way, and nothing in the app hard-deletes them.

Contacts have one difference. When you delete or anonymise a contact, their personal details (name, email, phone, address, notes and files) are wiped first, on purpose, so that they are really gone. The record itself stays, so their jobs still add up, but those details can’t be put back, even by our support team. See Contacts & Your Data.

There is one place where data is genuinely removed, and it is worth knowing about before you use it. If you import from your old system and then choose Start over, the import is undone. Only rows the import itself created are touched, so anything you typed in yourself is left alone. Of the rows it does touch:

  • Recoverable: Products, assets, jobs, contacts, allocations and categories are soft deleted, so they can be restored
  • Removed for good: Services on a job, line groups on a job, locations, maintenance records, vehicles, inspection results, asset components, product rates, accessories and supplier costs. These tables have no soft delete, so the way back is to run the import again rather than to restore a row.

Start over is limited to owners and administrators, cannot run while an import is in progress, and the app asks you to confirm before it does anything.

Behind both of those, the daily backups and point-in-time recovery above are the real safety net: anything lost can be recovered from a database restore inside the retention windows.

Need something recovered? If you've accidentally deleted a product, job, or other important record, contact our support team and we can restore it for you. A deleted or anonymised contact can be restored as a record, but not with their personal details, which were wiped.

Data Residency & Third Parties

Your data is stored in Google Cloud's London (europe-west2) region. That covers:

  • Your database and all its backups
  • Uploaded files, documents and product images
  • The application servers that run Rental HQ

Rental HQ is not a closed system, though. Several features work by sending data to other companies' services, and most of those run outside the UK. Here is the full list and what each one receives:

  • Firebase Authentication (Google): Your email address and your sign-in, as described above
  • Google Gemini, on Google Cloud Vertex AI: Everything the AI features work on. Gemini runs in Rental HQ's own Google Cloud project under Google Cloud's terms, stays in the European Union (each request goes first to Google's EU multi-region and, if that is slow to answer, also to Google's Frankfurt region in Germany), and Google does not use what we send to train its models. Spec IQ sends the rider or specification you upload. AI-assisted entry sends the product or vehicle name you typed. Make a job sends what you type to it. Shrink sends your question and the records that answer it, read with your own permissions. Similar products and swap suggestions send the names of products in the same group, never their prices. RF IQ sends your frequency plan. Health and safety drafting is not available at present, and nothing is sent for it. Matching your document design sends the quote or invoice you upload. When a job is marked complete, the job title, the client name, the venue and the internal crew conversation on that job are sent so the lessons summary can be written. Our logs record how much each feature uses, not what was sent or what came back.
  • SerpAPI: Product photo search. When a product has no photo and none is in the shared catalogue, its name is sent to SerpAPI, which searches Google Images for a picture of it. Only the product name is sent.
  • Resend: Outgoing email: the recipient's address, the subject, the message, and any attached PDF such as a quote or an invoice
  • Stripe: Your Rental HQ subscription, and client deposits if you take them. Card numbers go from the payer's browser straight to Stripe and never pass through Rental HQ.
  • Google Places: Venue and hotel lookup: the name, address or coordinates being searched for
  • QuickBooks or Xero: Only if you connect one. It receives the invoices and customer records you choose to sync.

The accounting sync and card payments are yours to turn on or leave alone. The AI features are on for every company and there is no per-company switch for them at present, so if that matters to you, please talk to us before you sign up.

Access Control

  • No per-seat limits: The subscription is a flat monthly price plus the modules you choose. Nothing in Rental HQ counts users or charges for them, so add as many people as you need.
  • Admin controls: Owners and administrators can invite people, change what role they have and remove them. Managers can also create crew users.
  • Audit trail: Assets and products keep a history of who created or changed the record, what changed and when. For assets that includes movements recorded by scanning, quarantine and release, and goods-in. A job’s Activity page lists every scan on that job: who scanned what, and when.

Uptime & Reliability

  • Managed infrastructure: Google Cloud handles hardware, networking, OS patching, and scaling
  • Auto-scaling: Cloud Run scales application containers up and down based on demand, so Rental HQ stays responsive during busy periods
  • Connection resilience: Database connections are pooled and managed to survive transient network issues without data loss

Questions?

If you have specific questions about how your data is protected, or need information for a security review or procurement process, please contact us at support@rentalhq.app.

Was this helpful?
Up next
Back to all articles
You have reached the end of the guides. Browse the full library on the support home page.