Summary
- astral is a private project in development. Access is by invitation only. There is no paid subscription yet, and no payment data is collected.
- We do not sell data, show ads or use third-party analytics or trackers.
- We do not record the content of secure-connection traffic, or the addresses and paths of the pages you open through it. Site names only appear in statistics if those are switched on for a device.
- To run and protect the services we keep account data, the IP addresses of connections and sign-ins, traffic counters and event logs. Retention periods are given below. Most logs that contain IP addresses are kept for at most 12 months.
- Our servers are in Finland, Germany and Russia, and data moves between these countries. See Where data is stored.
- You can download a copy of your data yourself on your astral ID profile, under “My data”, and request account deletion there too. For anything else, write to privacy@astralnet.io.
Who processes data
The services are operated by the astral project, a private individual ("astral", "we"), who decides which data is processed and why. Contact for data questions: privacy@astralnet.io.
This policy covers the astralnet.io site and astral ID single sign-on (id.astralnet.io). It also covers the secure connection: the VPN, its admin panel and the device portal at sub.astralnet.io. It further covers astral mail and the back-office systems these services run on.
The astralnet.io site
The site has no analytics, counters or third-party scripts. Fonts, icons and images load from our own server. The site's server (in Finland) keeps no visit log.
Requests to the site, like requests to all our other addresses, pass through the edge proxy. Its log is described under Edge proxy.
Request and waitlist forms
The site's forms send their data to astral ID. We store:
- your email address;
- your name and message, if you give them (the waitlist form has no message);
- the kind of request, the page language and the time;
- your IP address and browser (User-Agent), which are used to protect against spam and abuse.
One confirmation email is sent to the address you give. Submissions are rate-limited per IP address, and those counters exist only in server memory.
A request or waitlist entry is deleted automatically 12 months after we reply, or 12 months after it arrives if there was no reply. The note of the submission in the security log (email, IP address, browser) is also kept for 12 months. To have your data removed sooner, write to privacy@astralnet.io.
astral ID
astral ID is your account and the single sign-on for every astral service. It stores:
- Profile: email address and whether it is verified, display name, interface language, roles, organisation memberships and invitations. If you have been given an astral mailbox, its address is stored too.
- Sign-in methods:
- your password, stored only as an argon2id hash;
- your authenticator-app secret, encrypted (AES-256-GCM);
- your recovery codes, stored only as one-way check values;
- for each passkey, the public key, a name and when it was last used. The passkey's private key never leaves your device.
- Sessions: sign-in time, last activity, sign-in method, IP address and browser (User-Agent). This lets you see your active sessions and end the ones you don't need. A session lasts up to 7 days, or ends after 12 hours without activity. Its record is deleted 30 days after the session ends.
- Remembered devices: browser and OS family without versions (for example "Firefox, macOS"), the last IP address, and the first and last sign-in times. The device cookie itself is not stored, only a one-way check value derived from it. A device that has not been used to sign in for 12 months is forgotten. You can remove it sooner in your account settings.
- Security emails: we tell you about a sign-in from a new device, a password or second-factor change and similar events. These emails show the time, IP address and browser/OS. They do not show a location, because astral ID does no IP geolocation. Our emails contain no remote images and no trackers.
- Security event log: sign-ins and failed attempts, password, second-factor and other settings changes, and administrator actions. Each entry records the time, IP address, browser and the email of whoever acted. Entries cannot be altered. They are deleted automatically after 12 months, including after an account is deleted.
The failed-sign-in counter is kept on the account and reset after a successful sign-in. Per-IP rate limits are counted in server memory only. - Applications: which astral services you authorised, and the tokens issued to them (stored as hashes). Tokens are deleted once they expire.
- Subscriptions (once they exist): organisation, plan, status and period.
When a subscription changes, astral ID tells the secure connection who its members are: identifier, email with its verified flag, name and role. These notifications are kept in astral ID for 90 days. - Notifications in your account: events about your traffic, access period, devices, sign-ins and mailbox: the event code, its time and figures (for example, a traffic percentage). They are kept for 6 months. You can turn off the emails for these notifications in your profile; security emails are always sent.
The astral ID program's technical log can contain IP addresses. It is size-limited and overwritten.
Sign in with Google
If you sign in with Google, Google gives us your account identifier, email address, whether it is verified, your name and language. We do not request your profile photo. We store the identifier and email to link the Google account to your astral ID account. If the account is created at that first sign-in, the name and language from Google become its profile.
We have no access to your Google mail, contacts, files or other Google data. You can unlink Google in your astral ID account settings.
Secure connection
Devices connect to the entry server in Moscow. From there, traffic reaches the internet either through the server in Frankfurt or directly from Moscow with a Russian IP address, depending on the device's mode.
Not recorded: the content of traffic, the addresses and paths of pages you open, and the IP addresses and ports your devices connect to. Site names are recorded only in the cases described under DNS below.
Kept so the connection works, limits are counted and problems can be investigated:
| What | Why | How long |
|---|---|---|
| Device profile: name, owner's name, link to astral ID, note, connection keys, internal network address, settings (DNS filter, limits, schedule), creation date | Running the connection | While the profile exists |
| Device traffic counters: bytes received and sent per minute | Load graphs | 7 days |
| Device traffic totals per month, including the share that went out directly | Monthly limits, load accounting | While the profile exists |
| Connection history: session start and end, the IP address the device connected from, the provider's network name, protocol, bytes per session | Troubleshooting, detecting a profile used by someone else | The last 100 sessions per device, while the profile exists |
| Speed-test results, if you ran one: speed, latency, provider, protocol | Troubleshooting | The last 50 tests per device |
| Profile change history: what changed and when (name, note, owner, settings) | Investigating mistakes, undoing changes | The last 50 changes per device, while the profile exists |
| Device-portal session: astral ID identifier, email, name (no IP address) | Portal sign-in | 12 hours |
| The panel's user directory: astral ID identifier, email, name, when last seen; for subscriptions, the members, plan and period | Linking devices to people, subscription quotas | While there is a device or subscription; without either, 12 months after the last portal sign-in or mention |
| Panel journal: panel and portal sign-ins (with IP address and email), config and QR-code views and downloads, devices created, renamed and deleted, administrator actions | Security, incident investigation | 12 months |
To show the provider's network name, the connection's IP address is sent to the public whois services of the internet address registries (RIPE NCC and ARIN). The answer is kept in server memory for up to 24 hours.
When a device is deleted, its profile, counters, connection history, speed tests and change history are deleted with it.
DNS
Devices use the astral DNS server. If filtering (ads, threats, family) is on for a device, the DNS server writes its queries to a temporary file in memory. Every 30 seconds the file is processed and cleared. All that remains afterwards is:
- the number of queries the filter blocked, per device per day, kept for 31 days;
- the most frequent site names with query counts (up to 500 per day), only if DNS statistics are on for the device. They are off by default and switched on at the device owner's request. They are kept for 7 days, and everything collected is deleted at once when statistics are switched off.
When troubleshooting, an administrator can switch a device into diagnostic mode for 10 minutes. During that time the requested site names and the route the traffic takes are visible. These records exist only in server memory and are never written to disk.
Connection check page
On the check page inside the connection, your browser itself makes two requests to third-party sites:
- api.ipify.org, to show the IP address websites see. That service receives your external IP address, which is the astral exit address if your traffic goes through the connection.
- mc.yandex.ru, only to test whether the ad filter works. If the filter is on and working, the request is blocked. If not, Yandex receives an ordinary browser request. We do not use Yandex Metrica.
The speed test downloads test data from speed.cloudflare.com and proof.ovh.net. Our server makes those requests, so no data about you is passed to those sites.
Service logs
The connection programs write only warnings and errors to the system log. These can include technical details of failed connections, including IP addresses. The system log is size-limited and overwritten.
The astral mail server (Stalwart) is in Finland. Messages and folders are kept on it until you delete them, or for as long as the mailbox exists.
Incoming mail passes through the edge proxy. The mail server sees the IP address of the sending server, and the proxy records it in its connection log.
The mail server keeps a delivery log: sender, recipient, time, mail-server addresses, and the results of the SPF, DKIM and DMARC checks. It is needed for delivery and to fight spam. It is kept for 30 days. The delivery and encryption reports the server produces itself (DMARC, TLS-RPT) are also kept for 30 days. The mail server's technical log is size-limited and is overwritten in about a week.
A spam filter on our server checks incoming mail automatically. It may look up the sending server's address and domain in public blocklists. The samples the filter learns from are kept for 30 days. We do not read your mail or use it for advertising. The default mailbox size is 5 GB.
Mail servers that receive our mail send us DMARC reports. From them we keep daily summaries: the IP addresses of servers that sent mail as astralnet.io, message counts and check results. These summaries are kept for 400 days. The report emails themselves are kept in a service mailbox for 30 days and then deleted automatically.
Edge proxy
All our addresses run through an edge proxy server in Russia. That includes astralnet.io, id.astralnet.io, the panel, the portals and incoming mail. For web services, the proxy decrypts HTTPS and forwards requests to the right server over an encrypted tunnel. Some connections it passes on without decrypting them.
The proxy keeps a request log. For web requests it records:
- IP address and time;
- site and page address, including query parameters;
- response code and size;
- browser (User-Agent) and referring page (Referer).
For other connections (mail and other protocols) it records the IP address, time, service and size. The log is used to defend against attacks and to diagnose failures, and it is kept for 30 days.
- Traffic map: country and city are derived from the IP address with a local DB-IP database, without calling any third-party service. Only hourly summaries without IP addresses are kept, for 90 days.
- Abuse protection: addresses that attack the services may be blocked automatically, first for minutes or hours. Repeat offences can lead to a permanent block until it is lifted by hand. The per-IP offence record is forgotten after 30 days without new offences. The block journal, with sample requests, is kept for 180 days.
- Proxy administration log: administrator sign-ins and actions, with IP address, are kept for 400 days. The history of system events is kept for 365 days.
Notifications and Telegram
Administrators get service notifications in a private Telegram chat, sent through our notification server in Finland. Telegram processes this data on our behalf. Messages stay in Telegram until they are deleted from the chat. Notifications may include:
- device names and their owners' names;
- the email of a user who added a device in the portal;
- IP addresses and provider names in warnings about suspicious connections, for example one key used from two addresses at once;
- IP addresses of failed or emergency administrator sign-ins;
- email addresses in astral ID account-lock warnings;
- broken-site reports sent from a device: device name, owner and site name.
The notification server keeps:
- events for 30 days (at most 2000);
- a queue of undelivered messages, for up to 48 hours;
- a size-limited log of bot commands.
QR codes sent by the bot are deleted from the chat after 10 minutes. A daily encrypted copy of the connection settings also goes to this chat (see Backups).
Cookies and browser storage
- The astralnet.io site sets a
langcookie (the chosen language, for a year) only when you switch the language. The theme is kept in your browser's localStorage and never sent to the server. - astral ID uses only necessary cookies:
- a session cookie, up to 7 days;
- an unfinished-sign-in cookie, 10 minutes;
- a device cookie, for a year after a successful sign-in, so we recognise your device and avoid unnecessary warnings;
- a form-protection cookie, 7 days;
- short-lived Google sign-in cookies.
- The panel and the device portal use session cookies.
We use no advertising or analytics cookies anywhere.
Legal bases
We follow the EU General Data Protection Regulation (GDPR). Data is processed on these bases:
- Performance of a contract. We need the data to provide the services you use: the account, sign-in, device profiles, limit accounting, mail and security emails.
- Legitimate interests. We protect the services and their users from attacks and abuse, and diagnose failures. This covers the edge-proxy logs, security logs, automatic blocking, DMARC reports and service notifications. Their retention is limited, and they are used for nothing else.
- Consent. This covers access requests and the waitlist, and a device's DNS statistics. You can withdraw consent by writing to us or by switching the statistics off.
- Legal obligation. This applies where the law requires us to keep or disclose data.
Where data is stored
| Country | What runs and is stored there |
|---|---|
| Finland (Helsinki) | astral ID and its backups, mail, the notification server, the site |
| Germany (Frankfurt) | The secure connection's exit to the internet, availability monitoring |
| Russia (Moscow) | The secure connection's entry server and its panel: device profiles, counters, connection history, panel journal, user directory, backups |
| Russia | The edge proxy: every connection to our addresses passes through it. It holds the request log, abuse-protection data and DMARC summaries. |
Your data therefore moves between EU countries and Russia. For example, signing in to astral ID passes through the proxy in Russia and is handled in Finland. A device profile is kept in Russia, with your details coming from astral ID in Finland.
The European Union does not recognise Russia as providing adequate data protection, and we have not concluded separate transfer agreements (EU standard contractual clauses). The transfer is necessary to provide the service you ask for, because the connection runs through the Russian entry server. We limit it to what that requires and protect the data with the measures under How we protect data.
Our servers are rented from a hosting provider. According to the public RIPE NCC registry, the addresses of our servers, including those in Finland and Germany, are registered to a Russian company, LLC "Vektor AiTi Tekhnologii" (OneDash).
Who receives data
We do not sell data or share it for advertising. Data, or part of it, may reach:
- the hosting provider we rent servers from, to the extent it has access to them;
- Cloudflare, the registrar and DNS provider for astralnet.io. Only DNS lookups of our names pass through it; your traffic does not go through Cloudflare;
- Google, if you sign in with Google. Google Postmaster Tools also shows us aggregate delivery statistics for our mail to Gmail, without message content;
- Telegram, for service notifications and encrypted backups (see above);
- RIPE NCC and ARIN, which receive a device connection's IP address in a whois lookup to identify the provider;
- api.ipify.org and mc.yandex.ru, if you open the connection check page (see above);
- Let's Encrypt, which issues our certificates; no user data is sent to it;
- recipients' mail servers, when you send email;
- public authorities, only where applicable law requires it, and only to the extent of the request.
The device portal links to the AmneziaWG app on the App Store, Google Play, GitHub and amnezia.org. When you follow those links and install the app, those services' own terms apply.
Retention
| Data | Kept for |
|---|---|
| astral ID account, sign-in methods, Google link | While the account exists |
| astral ID sessions | Up to 7 days; the record is deleted 30 days after the session ends |
| astral ID remembered devices | 12 months after the last sign-in |
| astral ID security event log | 12 months |
| Access requests and waitlist | 12 months after our reply or receipt |
| Subscription notifications to the secure connection | 90 days |
| Device profile, its monthly traffic totals, connection history (100 sessions), speed tests (50), change history (50) | While the profile exists |
| Per-minute traffic counters | 7 days |
| Blocked DNS queries (counts) / frequent site names (if on) | 31 days / 7 days |
| Device-portal session | 12 hours |
| The panel's user directory | 12 months after last seen, if there is no device and no subscription |
| Secure-connection panel journal | 12 months |
| Edge-proxy request log | 30 days |
| Proxy offence records / block journal | 30 days without new offences / 180 days; a permanent block lasts until lifted |
| Proxy administration log / event history | 400 days / 365 days |
| DMARC summaries | 400 days |
| Messages in a mailbox | Until you delete them or the mailbox is removed |
| Mail delivery log / DMARC and TLS-RPT reports / spam-filter samples | 30 days |
| DMARC report emails in the service mailbox | 30 days |
| Notifications in your astral ID account | 6 months |
| Notification-server events | 30 days |
| Programs' technical logs | Size-limited, overwritten |
| Backups | See the next section |
Backups
- astral ID: a daily database copy, encrypted with age. The decryption key is not kept on the server. The last 14 copies are kept on the same server in Finland.
- Secure connection: a daily copy of the device profiles, encrypted with the backup passphrase (AES-256-GCM). The last 14 copies are kept on the same server in Moscow. The same encrypted copy, together with the server settings, also goes to the service Telegram chat. Logs, connection history and the user directory are not included.
- Mail: a daily copy of the mail server (mailboxes, settings, DKIM keys), encrypted with age; the decryption key is not kept on the server. The last 14 copies are kept on the same server in Finland.
- Edge proxy: a copy of its settings and service data is taken before each update and kept on the same server in Russia. The request log is not included.
Deleted data can remain in backups until those copies are replaced. For astral ID, mail and the secure connection that takes up to 14 days. Apart from those listed, we keep no other copies elsewhere.
How we protect data
- All connections to the services use HTTPS/TLS only. Data travels between our servers over an encrypted tunnel. Secure-connection traffic is encrypted.
- Passwords are stored only as argon2id hashes. Second-factor secrets and signing keys are stored encrypted.
- Backups are encrypted. Data files are readable only by service accounts.
- The admin panels are reached by signing in through astral ID. Important actions are written to logs that cannot be changed after the fact.
- We collect only what is needed to run and protect the services, and we delete data on the schedule in this policy.
If a breach is likely to affect your rights, we will tell the affected users.
Your rights
You have the right to:
- know what data we hold about you and get a copy in a machine-readable form;
- correct inaccurate data;
- have your account and data deleted;
- restrict processing or object to it;
- withdraw consent.
You can change your name, email, password, second factor, passkeys, sessions, devices and Google link in your astral ID account settings. Under “My data” on your profile you can download a copy of your data at any time as a JSON file: profile, sessions, devices, security log entries about your account, notifications, plan and linked sign-in methods. Passwords, second-factor secrets, recovery codes, keys and tokens are never included. The file is built when you ask, handed to you at once and not stored by us; downloading it needs a recent sign-in confirmation. You can also request account deletion there. An administrator reviews the request and approves or declines it, and you get an email about the decision. Your secure-connection devices are removed together with the account.
For correction and any other request, write to privacy@astralnet.io from your account's email address. We reply within 30 days.
Data export and deletion requests are recorded in the security log. Security logs are kept until their period ends even after an account is deleted, because they are needed to protect the services. You can also complain to the data protection authority in your country of residence.
Children
astral services are not intended for anyone under 16, and we do not knowingly collect their data. If you believe a child has given us data, write to privacy@astralnet.io and we will delete it.
Changes
If this policy changes, we will update this page and the edition date at the top. We will email account holders in advance about significant changes, such as the launch of a paid subscription and the addition of a payment provider.
Contact
Data questions and requests: privacy@astralnet.io. General questions: hello@astralnet.io.