Privacy Policy
AirNomadNetwork is operated by [Operating Company] LLC (“AirNomadNetwork”, “we”, “us”). This policy explains what we collect when you use our website, app and host software, why, who can see it, and how long we keep it.
The short version
- We never record which sites anyone visits: no website addresses, no destinations, no DNS lookups, for digital nomads or hosts. Nomads’ traffic doesn’t pass through our servers at all.
- We keep what we need to run bookings and handle abuse reports: who booked which host, when, and how much data was used, minute by minute. The host’s router counts the bytes; we get the amounts, never what the data was or where it went.
- Stripe handles ID checks. We keep only whether you passed, not your ID or photos.
- Hosts never learn who nomads are. We don’t sell your information, show ads, or use tracking cookies.
What we collect
| What | Why |
|---|---|
| Account: your email, your password (stored only as a scrambled hash), when you joined, and which versions of our policies you agreed to and when. | To run your account and show you agreed to our rules. |
| Invite requests: email, whether you want to host or book as a nomad, your city, and any note you add. | To decide who to invite to the pilot. |
| ID check result: whether you passed, when, Stripe’s reference for the check, when you agreed to the selfie check, and the reason if it failed. Also a fingerprint: a one-way coded value made from your verified name and date of birth. | So only verified people book or host, and so a closed account can’t return under a new email. The fingerprint can’t be turned back into your name or birth date. |
| Bookings: which nomad booked which host, start and end times, why it ended, the private address and port block assigned, your device’s WireGuard public key, when it last connected, and total data used. | To connect you, show you your stay, and match abuse reports to the booking responsible. |
| Data used per minute: how many bytes each booking sent and received in each minute. Amounts only, never what the data was or where it went. | To check whether a booking was active at the time an abuse report names. |
| Hosting connections: the host’s location label, router address (dynamic DNS name and port), the router’s WireGuard public key, when it last checked in, whether its home network wall is up, pauses, periodic checks that record the host’s public internet address and ports, upload speed tests about twice a week (the speed only), and which 10-minute periods the router was online. | To list hosts, show nomads each host’s measured speed and availability, connect nomads, and keep hosts safe. |
| Abuse reports and actions: notices hosts report from their internet provider (which can include details the provider sent), our findings, warnings, suspensions or bans, messages, and your responses. | To handle abuse fairly and keep a record. |
What we don’t collect: the sites, addresses or services anyone connects to; DNS lookups; the contents of traffic; nomads’ own internet addresses or locations (the host software deliberately leaves them out); logs of visits to our website or app; your WireGuard private key, which is created on your device and never sent to us.
Who sees it
- Hosts see their own bookings by number, with times and data amounts. Never the nomad’s name, email or anything else that identifies them.
- Nomads see a host’s location label, measured upload speed, availability and badges before booking. After booking, the connection details include the host’s router address, and while connected, websites (and the nomad) can see the host’s internet address and approximate area. Nomads never see a host’s name, email or street address.
- AirNomadNetwork’s team sees account and booking records to run the service and handle abuse.
- Service providers that run parts of the service for us: Stripe (ID checks, and payments when they begin), and Google Cloud (hosting our servers). They process data for us under data processing agreements. Our fonts are served from our own site, so your browser doesn’t contact Google Fonts.
- The law: we share records only when legally required, for example by a court order or subpoena, and we share only what’s asked for. We never have browsing records to share.
ID checks with Stripe
When you verify your ID, you give a photo of your ID and a selfie directly to Stripe, on Stripe’s page. Stripe checks them and tells us the result, and we read your verified name and date of birth once, to create the fingerprint above, without storing them. Once your check is decided, we ask Stripe to delete the images and document data; until then Stripe holds them under its own privacy policy.
Comparing your selfie with your ID photo uses biometric data (your face). We ask for your explicit consent, with a box you tick, before the check starts, and we record when you gave it. You don’t have to agree, but without the check you can’t book or host. Stripe decides automatically whether your ID and selfie match; if your check fails and you think it shouldn’t have, contact us and a person will review it.
How long we keep it
- Data used per minute: deleted automatically after six months.
- Speed tests, online periods and router port checks: deleted automatically after 90 days.
- Invite requests: deleted 12 months after you sent them, or 30 days after you sign up.
- Abuse reports and actions: deleted 2 years after they’re resolved. A suspension or ban stays on record while it’s in force.
- Accounts, bookings and ID check results: while your account is open, and afterwards as long as needed to handle abuse reports, legal claims and our legal obligations.
- Fingerprints of closed accounts: kept, so a banned person can’t sign up again.
- Backups: database backups and full server snapshots are kept for 14 days, then deleted.
On your device
The app stores your sign-in and each booking’s WireGuard private key in your browser’s local storage, so they stay on your device. We don’t use cookies for tracking or advertising.
Security
Connections to our site are encrypted. Passwords and host software tokens are stored only as scrambled hashes. ID photos are held by Stripe, not us. Each host’s software token works only for that host. No system is perfectly secure, and if a breach affects your information, we’ll tell you as the law requires.
Your choices
- You can ask to see, correct or delete your information, or to close your account. We’ll do so except where we must keep something for abuse handling, legal claims or the law (for example, a banned account’s fingerprint).
- Hosts can remove our software from their router at any time with our uninstaller.
- You must be at least 18 to use AirNomadNetwork. We don’t knowingly collect information from anyone younger.
If you’re in the EU, EEA or UK
The EU General Data Protection Regulation and the UK GDPR give you extra rights. This section applies to you if you live in the EU, EEA or UK.
Who’s responsible. [Operating Company] LLC is the controller of your information. Our representative in the EU is [EU representative, to be appointed] and in the UK is [UK representative, to be appointed]. Privacy contact: [privacy email, to be added].
Why we’re allowed to use your information.
| Information | Legal basis |
|---|---|
| Account, bookings and hosting connections | To provide the service you signed up for (contract). |
| Invite requests | Steps you ask us to take before an agreement, and our legitimate interest in running an invite-only pilot. |
| Selfie match in the ID check | Your explicit consent (GDPR article 9(2)(a)). |
| ID check result and fingerprint | Our legitimate interest, and our hosts’, in knowing every member is a real, single person and keeping banned people out. |
| Data used per minute, abuse reports and actions | Our and our hosts’ legitimate interest in tracing abuse to the booking responsible and protecting hosts; and legal obligations when a law requires us to keep or share records. |
| Speed tests and online periods | To provide the service (contract), and our legitimate interest in showing nomads measured, honest host information. |
| Security records and backups | Our legitimate interest in keeping the service and your information safe. |
Where it’s processed. We’re based in the US and our servers are in the US (Google Cloud, Iowa). You send your information to us there. Stripe and Google process it for us under data processing agreements, using approved safeguards, such as the European Commission’s standard contractual clauses or the EU–US Data Privacy Framework, where those apply.
Your rights. You can ask us to give you a copy of your information (including in a portable format), correct it, delete it, or limit how we use it. You can object to any use based on legitimate interests, and we’ll stop unless we have compelling reasons, such as an open abuse report. You can withdraw consent at any time; that doesn’t undo checks already done, and without a completed ID check you can’t book or host. You can ask for a person to review an automated ID check result. We answer within one month.
Complaints. You can complain to the data protection authority where you live or work (in the UK, the Information Commissioner’s Office), though we’d like the chance to sort it out first.
Breaches. If a breach puts your information at risk, we’ll notify the authority within 72 hours where the law requires, and tell you without undue delay if it’s likely to affect you seriously.
Changes
If we change this policy in a way that matters, we’ll tell you before the change takes effect.
Contact
To ask about your information or make a request, email [privacy email, to be added]. Until that address is live, reply to your invite email.