Relayno is operated by [REGISTERED COMPANY NAME], registered in [COUNTRY OF INCORPORATION] at [REGISTERED ADDRESS] under company number [COMPANY REGISTRATION NUMBER].

For anything in this policy, write to privacy@relayno.com. Our data protection contact is [DATA PROTECTION OFFICER EMAIL].

We handle personal data in two distinct capacities, and the rules differ between them.

As a controller, for data about you as our customer: your account, your billing details, and how you use the product.

As a processor, for data you put into your workspace about your own customers — contacts, orders, reservations, message threads. That data stays yours. We act on your instructions and the Data Processing Addendum governs it.

Account data: name, email address, and the authentication identifiers returned by your sign-in provider. We never receive or store your password when you sign in with Google or Microsoft.

Workspace content: everything you and your team create in the product — contacts, products, invoices, reservations and messages.

Billing data: company details, subscription state and payment metadata. Card numbers go directly to Stripe; they never reach our servers.

Technical data: IP address, browser and device type, and timestamped request logs.

Support data: whatever you tell us when you contact us, and our replies.

To provide the service you signed up for — performance of our contract with you.

To bill you and to keep the accounting records we are legally required to keep — contract and legal obligation.

To keep the platform secure, detect abuse and debug failures — our legitimate interest in a service that works.

To send product and marketing email — consent, which you can withdraw from any message or from your settings.

Messages you send and receive through Relayno pass through WhatsApp, operated by Meta Platforms. Their handling of that traffic is governed by their own terms, not ours.

Connecting a number links a WhatsApp session to your workspace. We store the session credentials needed to keep that connection alive, and the message history you choose to sync.

You are responsible for having a lawful basis to message the people you message.

We do not sell personal data, and we do not share it for advertising.

We use the sub-processors listed on this page, each bound by a data processing agreement.

We disclose data where the law requires it, and we will tell you unless we are legally barred from doing so.

If the business is sold or merged, data transfers with it and you will be told before anything changes.

Workspace content is kept for as long as your workspace is active.

After you close your account, content is retained for 30 days so that an accidental deletion can be undone, then permanently removed.

Invoices and accounting records are kept for the period our tax law requires.

Backups roll off on their own schedule; a deletion propagates through them within 90 days.

Some sub-processors operate outside your country. Where data leaves the EEA we rely on adequacy decisions or Standard Contractual Clauses.

The sub-processor table on this page states the region for each one.

You can ask for a copy of your data, correct it, delete it, restrict or object to how we use it, and receive it in a portable format.

Account owners can export a full workspace in JSON and CSV at any time from the console, without asking us.

To exercise a right, write to privacy@relayno.com. We answer within 30 days.

If we get it wrong, you can complain to your national data protection authority.

Traffic is encrypted in transit with TLS. Data at rest is encrypted by our infrastructure providers.

Access to production data is restricted to staff who need it, and is logged.

Two-factor authentication is available on all plans, and SSO on Enterprise.

If a breach affects you, we notify you and the relevant authority within 72 hours of becoming aware of it.

We use cookies that are strictly necessary to run the service: your session, your locale preference, and CSRF protection.

We do not use advertising cookies or third-party trackers on this site.

We update this page when our practices change and revise the date at the top.

For material changes we email account owners at least 30 days before they take effect.