Revres · Arteractive LLC

Privacy Policy

Effective date: July 30, 2026

This document describes our current practices in plain language. It is provided for informational purposes only and does not constitute legal advice. If you need legal advice about your rights, consult a lawyer in your jurisdiction.

Summary

Revres is designed so that your relationships, conversations, and shared content live on your devices and the devices of the people you choose. Arteractive LLC operates the marketing site and a small relay server that helps your devices find each other and pass encrypted traffic. We do not read that traffic, do not sell behavioural data, and do not run cross-site trackers on this site.

The marketing site (revres.io)

The public pages at revres.io (this page, the landing page, terms, and any future static pages) collect the following:

• Standard web server access logs (IP address, request path, user agent, timestamp). We retain these for up to 30 days for abuse mitigation and capacity planning, then discard them.
• No analytics cookies, fingerprinting scripts, or cross-site tracking pixels. The pages themselves set no first-party cookies.
• We may show non-personalised advertisements on the landing page through Google AdSense once the account is approved. AdSense loads JavaScript from pagead2.googlesyndication.com and sets first-party cookies for frequency capping and fraud detection. We have configured the AdSense account to deliver only non-personalised ads: targeting is limited to page context and rough geography, and no cross-site behavioural profile is built. Visitors in the EEA, UK, and Switzerland will see a consent prompt before any ad code loads. We do not yet load AdSense on this site; this disclosure documents what will be true once it goes live so the policy does not have to change underneath visitors.
• We do not show ads on legal pages (this privacy policy, the terms of service, or any future legal-notice page) regardless of the AdSense status on the landing page.

The Revres app

The Revres app holds the data you create directly on your device. That includes your identity keys, your contacts, your conversations, your shared content, and trust details like verifications and vouches. None of that data is sent to our servers in readable form.

To deliver messages between devices, the app sends encrypted payloads through a relay we operate. The relay is built to forward and to know as little as it can while still forwarding. It cannot read the contents, and it no longer learns who a delivery is from or who it is for. Each item is dropped at an anonymous mailbox address that the two people's apps work out privately between themselves and change regularly; the relay cannot connect that address to either person. What it does see is the size, the timing, and a coarse category of item (a message, a call, a group update), not the precise kind and not anything inside it.

We do not log message bodies and do not build behavioural profiles from this traffic. Delivery data is held only as long as delivery needs it. Once an item is picked up, the relay deletes its copy, normally within seconds, with a cleanup pass that removes it no later than 24 hours after pickup. An item that is never picked up is deleted when it expires, and nothing may wait longer than 91 days.

To keep the relay from being used to flood people, each account gets an anonymous spending allowance of deliveries per day. The relay can check that an allowance is being honoured without learning whose it is, so there are no abuse counters tied to who sent what to whom.

Two honest limits. First, the network address. Like any server on the internet, a delivery server can see where a request came from. We have built the way around that: a request can travel through a separate service first, so the server that delivers your message never sees where you are connecting from, and the service that does see it gets only a sealed bundle it cannot read. Here is the part that matters, though. That second service is still run by us. Splitting a request across two hops only buys you something real once the two hops answer to different people, so until we hand that first hop to an independent operator, treat this as one company holding both halves. We will say so here the day that changes. Second, because an item already in transit cannot be tied back to any account, deleting your account cannot recall items you have already sent; they are picked up or they expire on their own.

For features that require an email or SMS step (account recovery, throwaway alias delivery), we use standard transactional providers. Those providers see the addresses involved in the relevant message. We do not share your address book or relationship graph with anyone.

Account deletion

Because your data lives on your device, deleting the app removes the data. The Settings screen also offers an explicit "delete account" action that revokes your identity on the relay and asks any paired devices to wipe their copies.

Children

Revres is not directed at children under 13 (or the equivalent digital consent age in your country, where higher). We do not knowingly create accounts for users below that age.

Changes

When we change this policy, the effective date above changes too. We will not retroactively reduce the privacy protections you signed up under without giving you a reasonable opportunity to leave.

Contact

Privacy questions: privacy@arteractive.co.