Support
Airdress support runs over email. There is no ticket portal to sign up for — write to the address that fits your question and you will get a reply from a person.
Get help
For anything about the apps, your Airdress name, your account, or a charge:
Including these makes the first reply the useful one:
- Your Airdress name, or the email address on the account.
- What you did, what you expected, and what happened instead.
- App name and version, and the platform (iOS, Android, CLI, VS Code).
- The time it happened, with a time zone.
Where to write
| Subject | Address | First reply | Resolution target |
|---|---|---|---|
| Product, account, and billing | support@airdress.co | 1 business day | 5 business days |
| Security vulnerabilities | security@airdress.co | 4 business hours | 2 business days |
| Privacy and data requests | privacy@airdress.co | 1 business day | 30 days |
| Abuse reports | report-abuse@airdress.co | 1 business day | 3 business days |
| Legal and law enforcement | legal@airdress.co | 2 business days | 10 business days |
Targets, not guarantees. Business hours are Monday to Friday, 09:00–17:00 Europe/Berlin, excluding German public holidays. Security reports are triaged outside those hours when they describe an active exploit.
Before you write
- Documentation — setup, the operator, the CLI, and the protocol reference
- Service status — live status and incident history for relay, DNS, and the account hub
- GitHub — issues and source for the open components
Account and billing
- Manage your subscription — change or cancel from the account dashboard
- Refund policy — what is refundable and how to ask
- Delete your account — how to close it and what happens to your data
Reporting a vulnerability
Send security reports to security@airdress.co. Please give us a reasonable window to ship a fix before publishing. We do not currently run a paid bug bounty, and we will not pursue action against good-faith research that respects user privacy and service availability.
Machine-readable contact details are published at /.well-known/security.txt.