Security and privacy

Something is published under your name. So Rvply does as little as possible on its own.

This page says who makes Rvply, where your data lives, what the Google connection may and may not do, and which rules are fixed in the product. The legal documents are at the bottom.

Who you are dealing with

A Dutch company, a Dutch address.

Rvply is a product of ShipIt Digital in Amsterdam. The party you contract with, and the name on the invoice, is Shipit.

Seller: Shipit
Chamber of Commerce (KVK): 85945579
Address: Torresstraat 50
1056 RV Amsterdam
The Netherlands
Product: Rvply, replies to Google reviews
Contact: Contact form

Where your data lives

Your database is in Germany. Below is who else is involved, and where.

Server, database and backups

At Hetzner in Nuremberg, Germany. That is where your reviews, drafts and settings are stored. We keep review data for 24 months and the audit log for 12 months.

Drafting the replies

To write a draft, the review, the reviewer's first name and your location's settings go to OpenAI, which processes the request in the United States under the EU standard contractual clauses. We ask OpenAI not to store the response; OpenAI may keep requests for up to 30 days to detect abuse. Your reviews are not used to train models.

Email and payments

Approval and digest emails contain the review, the reviewer's name and the draft. They go through Resend in the United States, under the EU standard contractual clauses. Payments run through Mollie in Amsterdam; we never see card numbers.

The full list, with purpose, location and legal basis, is on the sub-processors page. We announce changes thirty days ahead.

The Google connection

One permission, to read and answer reviews.

When you sign in, Rvply asks for one Google permission on your Business Profile (business.manage) and uses it for three things: listing your locations, reading your reviews and publishing the replies you approve. You can revoke it at any time, in your Google account or with one click in Rvply. We then delete the access token immediately.

×Never publish a reply you have not approved, unless you switch on automatic publishing yourself.
×Never delete, hide or report a review to Google.
×Never change your opening hours, address, photos, category or name.
×Never touch your Gmail, Drive, ads or payments.
×Never sell your reviews, share them with other customers or use them to train models.

Fixed rules

What the product itself enforces, on every plan.

✓

Nothing goes out by itself until you switch it on

A new location starts by approval. You switch automatic publishing on per location, with a confirmation, and only for the stars you choose. You can switch it off at any time.

Illness, injury and claims: always a person

A review about getting ill, an injury or a legal claim is never answered automatically. That rule cannot be switched off. In healthcare and professional services every reply waits for a person.

≠

Flagged drafts wait

A draft flagged by a check, for example because it looks too much like an earlier reply or contains contact details, never goes to Google on its own.

A waiting time you choose

Automatic replies appear at a random moment within the waiting time you choose per location or for your organisation. You can pause at any time.

Four roles, one owner

Owner, admin, editor and viewer. Only the owner manages the Google connection, the team and billing. Who approved what is in the audit log.

↓

Your data is yours

You export your data whenever you like. If you delete your organisation, its review data disappears from the active database. What is on Google stays yours.

No tracking

No analytics cookies, no cookie banner.

This site loads nothing from third parties: no tag manager, no external fonts, no statistics scripts. The only thing it keeps in your browser is whether the opening animation has already played.

The application sets only the cookies it needs to keep you signed in, remember your language and complete the Google sign-in safely. No advertising cookies, no third-party cookies. That is why there is no banner.

A source check in the development environment fails as soon as somebody adds a cookie that is not in the register, or includes a known tracking script. The promise cannot quietly expire.

Read the cookie statement →

Legal

The documents.

All legal documents are in English. The English text is the binding one.

Questions about security or privacy?

Ask them through the contact form. You get an answer by email, within two working days.

Go to the contact form