Last updated: 2026-09-20

Effective Date: April 12, 2026 Last Updated: September 20, 2026

Airdress, Inc. (“Airdress,” “we,” “us,” or “our”) is committed to protecting your privacy. This Privacy Policy explains how we collect, use, store, and share personal information when you use the Airdress service, website, and related software (collectively, the “Service”).

This policy applies to all users of the Service, including visitors to our website, registered account holders, and API consumers.

1. Information We Collect#

1.1 Information You Provide#

• Waitlist Information. If you join our waitlist before creating an Account, we collect your email address and, optionally, your intended use case. We also record the country derived from your IP address (country-level only; the IP address itself is not stored), any referral code used, and marketing attribution parameters (UTM tags) from the URL. This information is used to manage the waitlist, send you a confirmation and eventual invite email, and understand demand for the Service. Waitlist data is deleted 90 days after you create an Account or upon request at privacy@airdress.co.
• Account Information. When you register, we collect your name, email address, and password (stored in hashed form). If you register on behalf of an organization, we may also collect the organization name and your role.
• Billing Information. If you subscribe to a paid plan or make a one-time payment, we collect billing details such as your name, billing address, and tax identification number where applicable. Payment card details are collected and processed directly by our payment processor (Stripe) and are not stored on our systems. When you initiate a checkout session, we transmit your email address and ZITADEL user ID to Stripe as customer metadata to associate the transaction with your account.
• Communications. When you contact us for support or send us correspondence, we collect the content of those communications and associated metadata.

1.2 Information Collected Automatically#

• Service Metadata. We collect metadata necessary to operate the relay network, including: Endpoint connection timestamps, tunnel establishment and teardown events, protocol-level routing metadata (Airdress Identifier, Endpoint health status, failover events), and aggregate bandwidth usage per Account.
• Log Data. We collect server logs that may include your IP address, request timestamps, API endpoints accessed, HTTP status codes, and Agent version.
• Device Information. The Agent may report the operating system, architecture, Agent version, and a device identifier to the Service for routing and compatibility purposes.
• Crash and Diagnostic Data. If the Airdress Chat mobile app crashes or encounters an error, the app sends a crash report to our error-reporting provider (Sentry). A report contains the technical stack trace, the app version and build, the device model, operating system version, free memory and storage at the time, and up to fifty of the app’s most recent internal diagnostic log lines. Reports are pseudonymous: they carry a random per-installation identifier and are not linked to your Account, email address, or Airdress Identifier. They never contain the content of your messages, the names or addresses of your contacts, message previews, or authentication tokens — the app removes these fields before a report leaves the device, in addition to never writing them to its diagnostic log in the first place. Screenshots and screen recordings are not captured.
• Security Signals. Separately from crashes, the app sends a small, fixed set of security signals to the same error-reporting provider when it detects a condition that we need to know about across all installations — at present, only that the published identity key of someone you correspond with has changed, which is the condition that would indicate an impersonation attempt. These signals are how we learn that such an attempt may be under way at all: the affected device is the only party able to detect it, so a signal that travelled through our own servers could be suppressed by a compromise of those servers. A signal carries the name of the condition, how the contradicted key had originally been established, how long it had stood (rounded to a bracket such as “less than seven days”), and how many of your correspondents on that device are currently affected. It does not identify the correspondent, and it does not carry either key. It therefore tells us that something happened somewhere and how serious its shape is, and does not tell us who you were talking to. Acting on it requires you to tell us, which the app invites you to do; we cannot work out from the signal alone which conversation it concerned.
• Analytics Data (with consent). If you consent to analytics cookies, we collect usage data through PostHog, including pages visited, features used, session duration, browser type, and approximate location (country/region level). This data helps us understand how the Site and Service are used so we can improve them. Analytics data is not collected if you do not consent.
• Security Data. Cloudflare, which provides DDoS protection and content delivery for the Site, may process your IP address, browser characteristics, and request metadata to distinguish legitimate traffic from threats. This processing is necessary for the security of the Site.

1.2a Screens (the Airdress television app)#

The Airdress app for televisions is a display. It shows what you or someone else on your airdress sends to it, and it originates nothing.

• What it holds. After you pair it, the screen stores one credential for one surface in the television’s local storage. That credential authorises it to read that surface and nothing else — not your messages, not another screen, not your account.
• Where it sends. The screen talks only to the airdress you paired it with. If you run your own operator, that is your own machine and no information reaches us at all. It reports what it is capable of showing (its screen size, and which web features the television supports) and whether a card it was sent actually rendered, so that a picture which fails to appear is a fact somebody can see rather than a silence.
• What it does not do. It does not capture the screen, it does not listen, it has no camera, it does not identify who is in the room, and it does not measure whether anyone is watching. It contains no analytics and no third-party code.
• Pictures sent to a screen. An image you send is stored by the airdress you sent it to and fetched from there by the television. It is not processed by us unless that airdress is one we host for you, and it is never sent to a third party.

Anyone on your airdress can send to a screen you have paired, which is what makes a television in a shared room useful. Each card records who sent it, and the account owner can block any one sender without blocking the others.

A screen makes no sound unless you turn it on. Video sent to a screen plays silently by default, and only the account owner can enable sound, for one screen at a time. Neither the screen itself nor anyone else who can send to it may change that.

1.3 Information We Do Not Collect#

• Traffic Payload. We do not inspect, log, or store the contents of traffic transiting the Airdress relay network. All tunnel traffic is encrypted end-to-end using WireGuard.
• DNS Query Content. While we operate DNS-based routing, we process DNS queries only to the extent necessary for routing resolution. We do not log or sell DNS query data.

2. How We Use Your Information#

We use personal information for the following purposes:

• Providing, operating, and maintaining the Service.
• Managing your Account and authenticating access.
• Processing payments and billing.
• Monitoring and maintaining the security and integrity of the Service.
• Detecting and preventing abuse, fraud, and Acceptable Use Policy violations.
• Responding to your support requests and communications.
• Sending service-related notifications such as maintenance windows and security alerts.
• Complying with legal obligations.
• Improving the Service through aggregated, anonymized analytics.
• Understanding how visitors use the Site through product analytics (with your consent).
• Protecting the Site from malicious traffic, DDoS attacks, and automated abuse through Cloudflare’s security services.

We do not use your information for profiling, automated decision-making, or behavioral advertising. We do not sell your personal information.

3. How We Share Your Information#

We share personal information only in the following limited circumstances:

3.1 Service Providers#

We use the following categories of service providers who process data on our behalf under contractual obligations to protect your information:

We maintain a current list of service providers, available upon request at privacy@airdress.co.

3.1a Domain Registries and Public WHOIS#

This applies only if you register a domain name through Airdress.

A domain registration requires your contact details to be transmitted to the registrar of record (Tucows Domains Inc.) and onward to the registry operator for that top-level domain — for example Verisign for .com and .net, Public Interest Registry for .org, Google Registry for .dev, and Identity Digital for .xyz. These are recipients in their own right, not processors acting on our behalf: their handling of registration data is governed by their own agreements with ICANN.

ICANN requires these details to be accurate, and requires you to confirm your email address within 15 days of registration or of changing it.

WHOIS / RDDS publication. Registration data may be published in the public WHOIS or RDDS directory for the domain. We enable WHOIS privacy at no charge on every top-level domain that supports it, which replaces your details in the public record with the privacy service’s. Not every registry permits it, and where it is unavailable we say so on the order form before you pay, next to the name you are buying.

Registration data is retained by the registrar and registry for periods those parties set under ICANN policy, independently of our own retention in Section 4. We will notify you of material changes to this list.

For information on how Stripe processes payment data, see https://stripe.com/privacy.

3.2 Legal Requirements#

We may disclose personal information if required to do so by law, regulation, subpoena, court order, or other governmental request. Where permitted by law, we will notify you of such requests.

3.3 Business Transfers#

In the event of a merger, acquisition, or sale of assets, your personal information may be transferred to the successor entity. We will notify you before your information becomes subject to a different privacy policy.

3.4 With Your Consent#

We may share information for purposes not described here with your explicit consent.

4. Data Retention#

We retain personal information only as long as necessary for the purposes described in this policy:

• Waitlist data: Retained until 90 days after Account creation (conversion) or upon deletion request. If you never create an Account, waitlist data is retained for 12 months after signup, then deleted.
• Account data: Retained for the duration of your Account and for 90 days following Account closure, unless longer retention is required by law.
• Billing records: Retained for the period required by applicable tax law (generally 7 years for US federal tax purposes).
• Server logs: Retained for up to 90 days, unless a longer period is required for ongoing abuse investigation or legal proceedings.
• Support correspondence: Retained for up to 24 months after resolution.
• Crash reports: Retained for 90 days, then deleted.
• Push-to-talk audio: Held by the Airdress that carries the conversation for a bounded period — 14 days by default — then deleted; the message and its transcript are not deleted with it. Where you run that Airdress yourself, this is your setting and we hold nothing. See Section 12.3.

After the applicable retention period, data is deleted or irreversibly anonymized.

5. Data Security#

We implement appropriate technical and organizational measures to protect personal information against unauthorized access, alteration, disclosure, or destruction. These measures include:

• WireGuard encryption for all tunnel traffic.
• Encryption at rest for stored Account data.
• Access controls limiting personnel access to personal information on a need-to-know basis.
• Regular security reviews of our infrastructure and software.

While we take reasonable measures to protect your information, no method of transmission or storage is completely secure. We cannot guarantee absolute security.

6. International Data Transfers#

The Service is operated from the United States, with infrastructure hosted in the European Union (Germany and Finland). If you access the Service from outside the United States, your information may be transferred to, stored, and processed in the United States or other countries where our service providers operate.

Where we transfer personal data from the European Economic Area, United Kingdom, or Switzerland to the United States, we rely on appropriate transfer mechanisms, including the EU-U.S. Data Privacy Framework (where applicable) and Standard Contractual Clauses approved by the European Commission.

7. Your Privacy Rights#

Depending on your location, you may have certain rights regarding your personal information. We honor these rights regardless of where you are located, to the extent practicable.

7.1 All Users#

All users may:

• Access the personal information we hold about them.
• Request correction of inaccurate or incomplete information.
• Request deletion of their personal information, subject to legal retention requirements.
• Request a copy of their information in a portable format.
• Close their Account at any time.

To exercise these rights, contact us at privacy@airdress.co. We will respond within 30 days.

7.2 California Residents (CCPA/CPRA)#

If you are a California resident, you have the following additional rights under the California Consumer Privacy Act, as amended by the California Privacy Rights Act:

• Right to Know. You may request the categories and specific pieces of personal information we have collected about you, the sources, the purposes, and the categories of third parties to whom we disclose it.
• Right to Delete. You may request deletion of your personal information, subject to certain exceptions.
• Right to Correct. You may request correction of inaccurate personal information.
• Right to Opt Out of Sale or Sharing. We do not sell or share your personal information for cross-context behavioral advertising. No opt-out is necessary.
• Right to Non-Discrimination. We will not discriminate against you for exercising your CCPA rights.

To submit a request, contact us at privacy@airdress.co or by mail at the address below. We may verify your identity before fulfilling a request.

In the preceding 12 months, we have collected the categories of personal information described in Section 1 of this policy. We have not sold personal information. We have disclosed personal information to service providers for the business purposes described in Section 3.

7.3 European Economic Area, United Kingdom, and Switzerland (GDPR)#

If you are located in the EEA, UK, or Switzerland, the following applies:

Data Controller. Airdress, Inc. is the data controller for personal data collected through the Service.

Legal Bases. We process your personal data on the following legal bases under Article 6 of the GDPR:

• Performance of contract (Art. 6(1)(b)): Providing the Service, Account management, billing, and support.
• Legitimate interest (Art. 6(1)(f)): Security monitoring (including Cloudflare), abuse detection, anonymized analytics, and crash and error reporting from the mobile app (pseudonymous, content-free, limited to what is needed to diagnose and fix defects).
• Consent (Art. 6(1)(a)): Product analytics via PostHog. You may withdraw consent at any time through the cookie preferences on the Site.
• Legal obligation (Art. 6(1)(c)): Tax and regulatory compliance.

Additional Rights. In addition to the rights listed in Section 7.1, you have the right to:

• Restrict processing of your personal data in certain circumstances.
• Object to processing based on legitimate interests.
• Withdraw consent at any time, where processing is based on consent, without affecting the lawfulness of prior processing.

Supervisory Authority. You have the right to lodge a complaint with a data protection supervisory authority in your country of residence.

Data Processing Agreement. If you use the Service to process personal data of third parties and require a Data Processing Agreement under Article 28 of the GDPR, contact us at privacy@airdress.co.

8. Cookies and Tracking#

Our website uses strictly necessary cookies for authentication, session management, and security (including Cloudflare bot management and challenge cookies). We also use PostHog for product analytics; analytics cookies are only set after you provide consent through our cookie banner. We do not use advertising cookies, retargeting pixels, or social media tracking widgets.

For more information, including a full list of cookies and how to manage your preferences, see our Cookie Policy at [URL].

9. Children#

The Service is not directed to individuals under 18 years of age. We do not knowingly collect personal information from children. If we learn that we have collected information from a child under 13 (or under 16 in the EEA), we will delete it promptly. If you believe a child has provided us with personal information, contact us at privacy@airdress.co.

10. Do Not Track#

Some browsers transmit “Do Not Track” (DNT) signals. Because there is no common industry standard for DNT, we do not currently respond to DNT signals. However, analytics cookies are never set without your affirmative consent regardless of DNT settings, and we do not engage in behavioral advertising.

11. Changes to This Policy#

We may update this Privacy Policy from time to time. We will notify you of material changes at least 30 days before they take effect by email or through the Service. The “Last Updated” date at the top of this page reflects the most recent revision.

12. The Airdress Chat Mobile App#

Airdress Chat is our mobile application for Android. It is a companion app: it pairs with an Airdress you run, and most of what it handles never reaches our systems. This section describes what it does on your device and what leaves it.

12.1 What the App Stores on Your Device#

• Messages. Conversations are stored in a database local to the app on your device. Messages live only on the devices that were present to receive them; pairing a new device does not transfer your history to it, and we cannot restore history to a device that was not there.
• Credentials. Access tokens and pairing credentials are held in the platform keystore (Android Keystore) rather than in application storage.
• Cached images. Profile pictures fetched for display are cached locally and cleared when the app’s data is cleared.

12.2 Permissions the App Requests#

The app requests only the permissions the features you use require, and Android asks you at the point of use.

• Camera. Used solely to scan a pairing QR code when connecting the app to an Airdress. Camera frames are processed on your device to read the code; they are not stored, and no image is transmitted to us or to anyone else.
• Photos and media (system picker). Used when you choose a profile picture. Only the image you select is accessed. The selected image is uploaded and served from our content delivery network so that people you converse with can see it.
• Microphone. Used for push-to-talk. The app records only while you hold the talk button down, and it shows you that it is recording while it does. It does not listen in the background, it does not start recording on a sound or a wake word, and it runs no background service that could keep the microphone open after you let go. Releasing the button ends the recording.
• Notifications. Used to alert you to messages that have already been delivered to your device. Notifications are generated locally by the app.

The app does not request access to your contacts, your location, your call logs, or your SMS messages.

12.3 What Leaves Your Device#

• Account information. Signing in exchanges your name and email address with our account service via your identity provider, as described in Section 1.1.
• Profile picture. As described above, if you set one.
• Message content and routing. Messages are exchanged with the Airdress you have paired with. Where that Airdress is one you run yourself, we do not hold the message content; where our relay network carries the traffic, it does so encrypted and is not inspected, as described in Section 1.3.
• Voice recordings and their transcripts. A push-to-talk transmission is sent to the Airdress you have paired with, as a message, under the same encryption as any other message in that conversation. Where that Airdress is one you run yourself, we do not hold it. Two points about how it is handled:
  • Speech is turned into text on your device, before the recording is encrypted, using a model that runs locally. Your voice is not sent anywhere to be transcribed — not to us and not to a third party. The transcript travels inside the same encrypted message as the recording it describes.
  • The recording is kept for a limited time and the text is kept. An Airdress holds the audio of a transmission for a bounded period — 14 days by default, configurable by whoever runs it — and then deletes it. The message and its transcript remain. Nobody is able to read either without the keys held by the devices in the conversation.
• Diagnostics. The app reports its version and platform when checking for compatibility. If it crashes, it sends a crash report, and it sends the security signals, both described in Section 1.2 — neither of which carries your messages, your correspondents’ names, or your identity.

The app contains no advertising software development kits and no third-party analytics software development kits. The consent-based analytics described in Section 1.2 apply to our website, not to this app.

12.4 Server-Side Features Are Opt-In#

Features that would require your message content to be processed away from your device — such as server-side search or summarization — are off by default. Where such a feature is offered, it is presented as an explicit choice, per conversation, with its trade-off stated at the point you enable it.

12.5 Deleting Your Account and Your Data#

You can delete your account from within the app at Settings → Delete account, or from the web at https://airdress.co/delete-account. Deletion removes your profile and associated account data as described in Section 4. Messages held locally on your device are removed when you uninstall the app or clear its data.

12.6 Children#

Airdress Chat is not directed to children, consistent with Section 9. We do not knowingly collect personal information from children under 13 (or the applicable minimum age in your jurisdiction).

13. Contact#

For any questions or requests regarding this Privacy Policy or your personal information:

Airdress, Inc. 1111B S Governors Ave # 54153 Dover, DE 19904 United States

Email: privacy@airdress.co Web: https://airdress.co