Deze pagina is op dit moment alleen in het Engels beschikbaar. De Nederlandse versie volgt. Vragen? info@shipitdigital.nl

Cookie Statement

Rvply Last updated: 5 September 2026

---

This page lists every cookie Rvply places, what it is for, and how long it stays. It is short because the list is short.

1. The marketing site places no cookies at all

rvply.nl and the pages under it, including this one, set nothing. There is no analytics script, no advertising tag, no embedded video, no web font loaded from another company's server, and no social media button. Reading about Rvply leaves no trace on your device and sends no request to a third party.

2. The application places two cookies

Both are first-party, both are set by app.rvply.nl itself, and neither is shared with anyone.

rvply_session is set to HttpOnly, which means no script on the page can read it, and to SameSite=Lax, which means another website cannot make your browser send it. Signing out deletes it on the spot, on the server as well as in your browser: the session is a row in our database, not just a signed string, so it stops working the moment you end it.

rvply_taal holds one of three words, nl, en or tr. Nothing else. If you are signed in, the same choice is also stored on your account, so it follows you to another browser.

A third name, rvply_cookies, exists in the application's code and has never been written to anyone's browser. It is the cookie that would hold your answer if we ever introduced a cookie that needs one, and it would keep that answer for six months. It is listed here rather than left as a surprise: the list of cookies the application knows about is generated from the code itself, and you can read the current version at app.rvply.nl/cookies.

3. Why there is no cookie banner

Under Article 11.7a of the Dutch Telecommunications Act, which implements the ePrivacy Directive, consent is not required for cookies that are strictly necessary to deliver a service you asked for, or that have no more than a minor effect on your privacy. A session cookie and a language preference are both in that category. Asking you to agree to them would suggest you have a choice about whether the login works, and you do not: refusing them means refusing the product.

Everything that does require consent, analytics, advertising, profiling, anything that follows you to another website, we do not use.

This is enforced in the code rather than only promised here. Every cookie the application may set is declared in one file, a check that runs with our test suite fails the build if any code sets a name that file does not list, and the same check fails if the source so much as mentions a known analytics or advertising script. The consent request is built and wired and renders nothing at all while every declared cookie is strictly necessary, which is the case today. The day a cookie that needs consent is declared, three things happen at once: this page changes, the request appears before that cookie is placed, and nothing is set until you answer. Refusing is one press, the same size as accepting, and everything keeps working either way.

4. What we use instead of analytics cookies

We keep server logs, which record the address of the page requested, the time, and a truncated IP address. Those are written on our own servers, are not linked to your account for analytics purposes, are used for security and debugging only, and are deleted within 30 days. No cookie is involved, and nothing is shared with an analytics company.

5. Cookies that Google may place

Signing in with Google sends you to Google's own domain, where Google places its own cookies under its own privacy policy. That happens on Google's page, not ours, and we neither set nor read those cookies. When you come back, only the two cookies in section 2 exist on our side.

You can review and withdraw what you have granted us at myaccount.google.com/permissions at any time.

6. Refusing or deleting cookies

Every browser lets you block or delete cookies, per site or entirely. The controls sit under Settings, usually as "Privacy" or "Cookies and site data".

Deleting rvply_taal resets the interface to the language your browser asks for. Deleting or blocking rvply_session signs you out and stops you from signing back in, because there is nowhere left to keep the session. Blocking cookies for rvply.nl therefore blocks the application, which is a legitimate choice, but not one we can work around.

7. Changes

If this list changes, the date at the top of the page changes with it. A change that introduces a cookie requiring consent is announced by email to the primary contact on each account before it takes effect.

8. Contact

ShipIt Digital Torresstraat 50, 1056 RV Amsterdam, Nederland info@shipitdigital.nl KvK 85945579

For everything else we do with data, see the Privacy Policy.