Privacy
What Afar keeps, and why.
The short version
- No analytics, advertising, tracking pixels or fingerprinting, on the website or in the apps.
- We don’t sell your personal information or share it for advertising.
- The main site pages use no third-party scripts, fonts or embeds; signing in sends you to Apple’s or Google’s own page and back. The Cast receiver loads Google’s Cast framework from Google.
- Your terminal sessions, screens and files travel between your own devices. We never inspect, record or store them, including when they pass through our managed relay.
What your Afar account keeps
You only have an account if you sign in at your account page or in an Afar app.
- Sign-in identifiers. Your Afar account ID, and the account ID Apple or Google gives us for each one you sign in with. Used to sign you in and to link a second sign-in method.
- Email address. The address Apple or Google tells us they’ve verified (with Apple this may be a private relay address), and the address you give Stripe at checkout. Used for account and billing notices, receipts and replies to you.
- Plan and billing. Your plan, its status, trial and billing-period dates, and your Stripe customer and subscription IDs. Never card numbers: Stripe holds your payment details. Used for billing, tax, giving you what you paid for, refunds and disputes.
- Your agreement to automatic renewal. When you buy a plan, the exact renewal terms you were shown, the box you ticked, when, and the Stripe checkout it led to. The law requires us to keep this proof.
- Billing emails we send you. The purchase confirmation and renewal reminders the law requires, exactly as sent, with the address they went to and when our email service accepted them. Kept as proof that we sent them.
- Signed-in sessions. One record per signed-in browser or device, holding a scrambled (hashed) form of its sign-in token and when it started and expires. Used to keep you signed in and to sign you out.
- Managed relay usage. For each of your devices that uses the managed relay: its relay identifier, and how many bytes it says it sent to and received from each of your other devices through the relay, per app session. Used to count your allowance, checking each device's figures against the other side's. Never what the bytes contained. On an iPhone or iPad that supports it, Apple's App Attest key for the app, which shows those reports come from the real Afar app; once a device has used it, its later reports must too.
- Stolen-device records. When you used the emergency revoke and the reason you chose. Used to enforce the revocation and to look into a compromise.
- Request logs. Our host logs each request to the account service (when, which address, the result, and network details such as your IP address) to run and protect it.
Cookies
Signing in sets one strictly necessary cookie, __Secure-afar_rt, on api.fromafar.app. It keeps you
signed in for up to 60 days, is replaced each time it’s used, and page scripts can’t read it. While you sign in,
a second cookie, __Secure-afar_oauth, ties the sign-in to your browser for up to 10 minutes. The Afar
apps keep their sign-in in the device’s keychain instead and set no cookie. We set no analytics, advertising or
cross-site tracking cookies. If Cloudflare needs to check a visitor for abuse, it
may set a short-lived security cookie of its own.
Who handles it for us
- Stripe — takes payments, calculates sales tax and sends receipts. Stripe holds your card details.
- Cloudflare — hosts the website, the account service and its database, sends our billing emails, and forwards email sent to our addresses.
- Apple — Sign in with Apple, and tells us if you stop using it with Afar or delete your Apple ID; on iPhones and iPads that support it, App Attest shows that relay requests come from the real Afar app.
- Google — Sign in with Google.
- n0 (Iroh Services) — carries encrypted managed-relay traffic when you use it.
- Linq — sends pager messages, only if you turn on the Pro Fleet pager.
We also disclose information when the law requires it or to protect someone’s safety.
How long it’s kept
- Account, sign-in, plan, sessions and stolen-device records — until you delete your account. A session that expires can’t be used again.
- Managed relay usage — 400 days, so a billing question can still be answered, or until you delete your account.
- Your agreement to automatic renewal, and the billing emails we sent about it — at least three years after you agreed (or after the email was sent), or a year after the subscription ends if that’s later, even if you delete your account.
- Stripe payment-event IDs — kept so a payment event is never applied twice; deleting your account removes your account from them.
- Restorable database copies — up to 30 days after a change or deletion.
- Request logs — up to 7 days.
- Email you send us — until you ask us to delete it.
- Stripe’s own records — kept by Stripe under its own policies; we can’t delete them.
Your choices
- See your plan and sign-in methods, cancel your plan, and sign out at your account page.
- Sign out every device at once with the emergency revoke.
- Delete your account at any time; the account deletion page lists exactly what that deletes and keeps, and deleting your data covers removing only some data.
- To correct anything else we hold, write to hello@fromafar.app. We’ll confirm it’s you through your Apple or Google sign-in before changing account records.
- Because we don’t track you across other sites or sell or share your information for advertising, a Do Not Track or Global Privacy Control signal has nothing further to switch off.
Children
Afar is for adults (see the Terms of Service) and isn’t directed at children under 13. If you think a child has given us information, write to hello@fromafar.app and we’ll delete it.
What the website’s host sees
fromafar.app is served by Cloudflare. Like any web host, Cloudflare processes each visitor’s IP address, browser details and the pages requested in order to deliver the site and protect it from abuse. We don’t add anything to that and don’t use it to profile visitors. Cloudflare’s handling is described in its privacy policy. The Account & Plans hub at /account is an interactive preview using sample data; your real account is at /account/manage.
If you write to us
Messages to hello@fromafar.app or security@fromafar.app reach a person’s inbox. We use your address and message only to reply, and you can ask us to delete them at any time.
The Afar apps (local and BYO-Network pairing)
Afar connects to the Afar service on your own computer. We don’t run that computer, and we can’t see what passes between your devices.
- What the apps don’t do. No analytics, advertising, tracking or crash-reporting services, and no third-party code that sends telemetry anywhere.
- Where your data goes. In direct-pairing mode (on home Wi-Fi, or over your own Tailscale or VPN with Afar BYO-Network), the apps talk directly to the service address you pair with. On iPhone and iPad, a remote address must use HTTPS with a trusted certificate. Terminal sessions, screen frames, workspace files, job receipts and device status travel directly between your viewer device and your own computer. On iPhone and iPad, iOS also asks for local network access so the app can reach a service on your own network.
- Pairing. A pairing code or link contains no password or token, only where to send the request. You confirm a matching six-digit code and choose Allow on your computer. The app sends your device’s name so you can recognize it there. Your device then gets its own credential, kept only in that device’s secure storage, and you can remove it from your computer at any time.
- Optional service connections. If you enter another service’s address and paste a credential from that service’s operator, the credential stays in your device’s secure storage and is used only for that address. That operator handles what you send it, not us.
Managed relay, Settings Sync and the pager
- Transport-only managed relay (Afar Solo and Afar Pro Fleet). When you connect through the managed Afar relay rather than home Wi-Fi or your own VPN, Imagine That AI LLC and n0 process only the device-authentication metadata and timestamps needed to route packets, and Imagine That AI LLC keeps the byte counts your devices report to enforce your monthly relay allowance (20 GB or 60 GB a month). The relay is an encrypted network conduit and never inspects, records or stores terminal streams, desktop frames or workspace files.
- Zero-knowledge Settings Sync (512 KiB preview). Optional Settings Sync encrypts appearance,
layout and non-secret workspace preferences on your device with
AES-256-GCM, per-deviceHPKEkey wrapping and a 56-character Recovery Key before upload. Our servers store encrypted ciphertext, version metadata and enrolled device identifiers (up to 32 devices); we never hold your plaintext sync key or pairing credentials. - Opt-in pager alerts (Afar Pro Fleet). If you choose to enroll a verified iMessage or SMS contact for unanswered-prompt notifications, we and Linq store that verified handle and delivery status solely to send the alerts you requested, until you disable alerts or delete your account.
Changes and questions
When this policy changes, the date at the top changes with it. For questions about your data, write to hello@fromafar.app.