Privacy Policy

RWA Signal is published by Mikayel Nahapetyan (Armenia), who is the data controller for the information described here. Contact for any privacy matter: contact@rwasignal.io.

Reading RWA Signal requires no account and no sign-up. We do not ask for your name, and we do not know who you are.

Aggregated analytics. We use Vercel Analytics and Vercel Speed Insights to see which pages are read and how fast they load. These are cookie-free and reported in aggregate — page views and performance timings, not identified individuals followed across sites.

Presses on links that lead away from us. Two buttons send you elsewhere — “Apply on employer site” on a job, and “Read the full article at …” on a story. When you press one we record which opening or story it was, and when. That is the whole record: no cookie is set, no identifier is stored, and neither your IP address nor your browser is saved with it. We keep it to learn whether any of this is useful at all — it cannot tell us who pressed, and it is not linked to anything else about you.

Searches and filters. When you search the site, or choose a filter — the relevance filter on the home page, or the filters on the job board — we record the words you searched or the filter you chose, and when; for a search of the news, also how many stories it found. As with presses, nothing about you goes with it: no cookie, no identifier, no IP address, no browser. It tells us what readers look for and what the site is missing. The words are kept as typed, apart from capitals and extra spaces, so please do not type personal information into a search box.

Technical logs. Like any web server, ours records requests: timestamp, requested URL, browser user-agent and IP address. They exist to keep the site running and to spot abuse, they are not used to profile readers, and application logs are kept for about seven days before rotating out.

Market figures. The market sizes, fund values and yields in the header strip and the Market Overview card come from CoinGecko and DefiLlama. Our server fetches them; your browser does not contact either service to show them, and no reader or subscriber data is sent to them. Following the “Powered by CoinGecko” link takes you to their site, where their own privacy policy applies.

If you subscribe to the daily digest, we store your email address and the timestamps of the subscription lifecycle — when you signed up, when you confirmed, when a digest was last sent, and when you unsubscribed. Nothing else: no name, no company, no interests.

Double opt-in. Submitting the form creates a pending record and sends one confirmation email. Until you click the link in it, no digest is ever sent. This protects people from being signed up by someone else typing their address into our form.

Each record carries two opaque, single-purpose tokens — one to confirm the address, one to unsubscribe from any digest, in one click from your mail app. We do not put tracking pixels or click-wrapped links in the emails we build.

We set no tracking or advertising cookies — which is why this site shows no cookie consent banner. There are no ad networks, no third-party pixels and no cross-site trackers embedded in these pages. If that ever changes, a consent banner will appear before any such technology is switched on, and this page will say so.

A few preferences live in your browser’s local storage and are never transmitted to us: your light or dark theme choice, the articles you save for later, and a flag noting that you already subscribed so the form does not keep asking. Clearing your browser data removes them.

The share buttons on articles are plain links to X, Telegram and LinkedIn. We embed no social scripts, widgets or like-buttons, so those networks see you only if and when you click through — after which their own privacy policies apply.

Consent — for the email digest. You give it by confirming the double opt-in link, and you can withdraw it at any time through the unsubscribe link, with no consequence other than the digest stopping.

Legitimate interest — for server logs, aggregated analytics and the anonymous records of presses, searches and filters: operating the site, keeping it fast, learning what readers look for, and defending it against abuse. This processing is minimal by design, is not used to identify or profile readers, and is not combined with the subscriber list.

We use a small number of providers, each doing one job. They may access only what that job requires, and may not use it for anything else.

Vercel Inc. (United States) — hosts the website and provides the aggregated analytics described above. Privacy policy.

Hetzner Online GmbH (Germany) — hosts our API server and database, where the subscriber list lives. Privacy policy.

Resend (United States) — delivers the confirmation and digest emails, and therefore processes subscriber addresses. Privacy policy.

Google LLC (United States) — its Gemini models summarize and classify the news articles we ingest. Gemini receives article text from publishers, never reader or subscriber data. No personal information from this site is sent to any AI model. Privacy policy.

The subscriber database sits on a server in Germany. The controller is based in Armenia, and the providers named above operate in the United States and the European Union, so data is processed outside the EEA. Each provider publishes the safeguards it applies to such transfers in the policies linked above.

We publish our own articles to our own pages on Telegram, LinkedIn and Facebook. These integrations are authorized by the site owner, who administers those pages, and we request only the permissions needed to post on behalf of our own page.

Access tokens for these integrations are held as server-side secrets — never published, never committed to our source code, never shared. We do not collect, store, sell or otherwise process data about the users of those platforms, and we use these integrations for nothing except publishing our own content.

Nobody. We do not sell, rent, trade or share personal data with advertisers, data brokers or partners, and we run no advertising networks or cross-site tracking. The only exception would be a legally binding demand from a competent authority, which we would answer on the narrowest reading available to us.

A subscriber record is kept while the subscription is active. After unsubscribing, the record is retained in an unsubscribed state so the address is not accidentally re-added by an old form submission — or deleted outright if you ask. Application logs rotate after about a week. Analytics are aggregated and not tied to a person. Records of presses, searches and filters carry nothing that identifies anyone, so they cannot be traced back to a reader; we keep them to compare what readers do over time.

The site and API are served over HTTPS. Credentials, API keys and integration tokens are stored as server-side secrets, kept out of the source code, and access to the server and database is limited to the site owner. The administration area requires two-factor authentication.

No system is perfectly secure, and we would rather say so than promise otherwise. The most sensitive thing we hold about a reader is an email address, and we keep the amount of data small precisely so that there is little to expose.

You may request access to the data we hold about you, rectification if it is wrong, erasure, restriction of processing, portability of what you gave us, and you may object to processing based on legitimate interest. Where processing rests on consent, you may withdraw it at any time.

In practice this is simple: every digest carries an unsubscribe link, and email clients that support one-click unsubscribe can use it directly. To have your address erased completely rather than marked unsubscribed, or to ask what we hold, email contact@rwasignal.io from that address. We answer within 30 days; given the above, the answer is normally one row in a table. The same instructions, on their own page, are at data deletion.

If you are in the EU or EEA and believe your data has been handled improperly, you also have the right to lodge a complaint with the data protection authority of the country where you live.

This site is intended for adults — our terms set the minimum age at 18 — and we do not knowingly collect personal data from children. If you believe a child has subscribed, write to us and we will remove the record.

If what we collect changes — new features, an account system, paid plans — this page is updated before those features go live, and the date at the top changes with it. We will not quietly start collecting more than is described here.

Questions about this policy go to contact@rwasignal.io. The rules for using the site are in our terms & conditions, and how the feed itself is assembled is described in our editorial guidelines.