Privacy Policy
AZET LLC (“AZET,” “we,” or “us”) is an Ohio limited liability company. It operates azet.io, the azet waitlist, and, when it launches, the azet product. AZET (Korea), a sole proprietorship registered in the Republic of Korea (business registration no. 897-76-00506) and a separate business from AZET LLC, provides advertising and marketing services to clients in Korea under its own contracts and handles those clients’ personal information under the Personal Information Protection Act of the Republic of Korea, as set out in the AZET (Korea) privacy policy (Korean). This policy explains what personal information we collect, how we use it, and the choices you have. We comply with the privacy laws that apply to us.
1. Information we collect and how
We collect only the minimum information needed to run the website and the waitlist, and respond to inquiries.
| Purpose | Information | How we collect it |
|---|---|---|
| Inquiries and consultations | Name, company, phone number, email | Provided by you when you contact us by email |
| Automatic collection | Cookies, IP address, browser and device information, visit history | Generated automatically when you use the website |
| AZET app for Mac (early version) | IP address and basic request information (time, the file requested, and the app’s network library name) when the app checks for and downloads updates | Generated automatically when the app checks downloads.azet.io for updates |
| AZET account (optional) | Username, a salted hash of your password, your sign-in sessions and connected devices, usage records for features that use credits, and one-way hashes of IP addresses used to limit sign-in attempts | Provided by you when you create an account at browser-api.azet.io or sign in from the app’s command-line tool (the hashes and records are generated automatically) |
| AZET security apps (license check) | The product name, a random device ID the app makes for itself and the platform (for example android); if you enter a license key, also the key (we store only a one-way hash of it) and a device name, which is a fixed word for the platform (“Android”, “iPhone”, “Mac” or “Windows PC”). The request reveals your IP address, as any web request does; we do not store it. To limit abuse, trial, activation, release and waitlist requests are counted per hour against a one-way keyed hash of the address | Sent by the app to suite-api.azet.io when a free trial starts, when you activate or release a key, and when the app checks the license, about once a day |
| Sweep for Android: suspicious-text report (optional) | The text you paste or share into the report screen (up to 2,000 characters), the first link in it, the app version and the Android version | Sent to sweep-api.azet.io only after you tick the consent box and tap Send report |
| Sweep for Android: message check with AZET Nunchi (optional, from 0.6.4) | The text you paste or share (up to 2,000 characters) | Sent to sweep-api.azet.io only after you tick the consent box and tap “Check for a scam with AI”; not stored |
| Sweep browser extension: problem report and feedback (optional) | The page address without its query string, the addresses that page requested and what Sweep did with each, the problem type you pick and your notes. In Chrome and Edge, and in Firefox if you allow technical data, also the browser and extension versions and diagnostic details about the page (for example load errors and timing) | Sent to sweep-api.azet.io only when you press Send in the report or feedback form |
| AZET Shield (open beta) | Workspace: the email address you give for alerts (optional), addresses you allow or block and your notes, sites you add for scanning, and a hash of your access token. Server agent: the items listed under AZET Shield below | Provided by you in the dashboard at shield.azet.io; sent by the agent you install on your server |
| Sweep: blocking report (optional) | The page address you report, what happened, your notes, an email address if you give one, and the app, Android and filter-list versions | Provided by you in the form at azet.io/sweep/report, which the app opens in your browser with the blocked domain filled in |
| Store waitlist for security apps | Email address, the product and the plan you picked | Provided by you in the form on a product page or in the app, or by email if you write to us instead |
| Partner and sales inquiries | Your name, work email, company, website, country, company size, what the inquiry is about, your message, the page you sent it from, and a one-way hash of your IP address | Provided by you in the form on our Partners or Contact page (the hash is generated automatically) |
| Waitlist | Email address, the page and language you signed up from, and one-way hashes of your IP address and browser user agent | Provided by you when you join the waitlist on our website (the hashes are generated automatically) |
Partner and sales inquiries. If you send the form on our Partners or Contact page, we use what you send only to reply to you and to discuss the partnership or purchase you asked about. The IP hash is used only to limit automated or repeated submissions. We keep an inquiry for one year from the day we receive it and then delete it automatically; you can ask us to delete it sooner by writing to hello@azet.io. It is stored on Cloudflare, Inc. infrastructure, and we get a notice by email (without your details) when a new inquiry arrives.
Free dub requests. If you send the form on our Dub page, we use your name, email, company or channel, video link and message only to reply and to make the free dub you asked for. To make it we download the video from your link and send its audio to Deepgram, Inc. (US, speech recognition), the transcript to Anthropic, PBC (US, translation) and the translated text to Rime Labs, Inc. (US, voices); none of them may train on it. Deepgram keeps it only as long as needed to process the request, Anthropic deletes it within 30 days, and Rime receives only the translated text. We delete your video and the finished dub 30 days after we send it to you, and the request itself as described above for inquiries. You can ask us to delete any of it sooner at hello@azet.io.
Waitlist. If you join the waitlist, we use your email address only to tell you when azet opens. The hashes are used only to block automated or abusive sign-ups; we don’t store your IP address or user agent themselves. We keep this information until we send the launch notice, or until you ask us to delete it by writing to hello@azet.io. It is stored on Cloudflare, Inc. infrastructure.
AZET app for Mac (early version, added October 3, 2026; applies now). About 15 seconds after it starts and then every hour while it runs (and every hour while it is closed, if you install the optional updater from its command-line tool), the app requests a small version file from downloads.azet.io, and downloads a new version when one is available. These requests carry no account, name, email, or device identifier. Like any web request, they reveal your IP address to Cloudflare, Inc., which hosts downloads.azet.io; we have not turned on request logging for this service and do not use these requests to identify or track you. Everything else the app handles, including your chats, tasks, browsing data, settings, and any provider sign-ins or keys, is stored on your Mac; if you do not sign in to an AZET account, none of it is sent to us. When you run a task with an AI provider you connected yourself (for example Claude or Codex), the app sends your request and the page content the task needs to that provider, under that provider’s own privacy policy. AZET account. An account is optional and open for early testing. We store the account information listed in the table above; we never store your password itself. When you are signed in, a task that uses AZET’s hosted models sends its goal and the page content it needs to browser-api.azet.io. These hosted features are turned off on our servers today, so such requests are refused before their content is read. We keep account information until you ask us to delete your account by writing to hello@azet.io. The app contains no analytics or advertising tools.
AZET security apps (Sweep, AZET Care for Android and iPhone, AZET Care for Mac, AZET Care for Windows; added October 5, 2026; applies now). These apps work on your device. Ad, tracker and scam-site filtering (Sweep) and the checks and cleanup (Care) run on the device; we do not receive the sites you visit, your DNS queries, your file names, your list of installed apps or the results of a scan. What the apps send AZET is the license check (the product name, the random device ID and the platform; if you enter a license key, also the key and a device name, which is a fixed word for the platform, not your computer’s name) and requests for files from azet.io hosts, which carry no identifier: update files and, in AZET Care for Mac, the list of current macOS versions it compares your Mac against. No account is needed, and the device ID is not a hardware identifier. The app keeps the last answer for up to 7 days when the network is down. The license service does not store your IP address; its abuse-limit counters use a one-way keyed hash of the address and are deleted within three days. Sweep for Android and AZET Care for Android are available as betas; AZET Care for iPhone, Mac and Windows are not released yet. What each Care app sends beyond this, only when you turn it on, is listed in its own section below. If you use the store waitlist form, we keep your email address, the product and the plan only to send you one email when checkout opens, and delete them on request.
Sweep for Android (beta). Sweep sets up a local VPN on your phone. From version 0.6.0 your apps’ connections pass through it on the phone: it reads the domain name, the app and the amount of data, and does not decrypt the contents (before 0.6.0 it received DNS lookups only). Filtering happens on the phone: the domain names your apps look up, which app looked them up and the list of what was blocked are never sent to AZET, and the Activity list is kept in memory only. The phone stores daily totals per list and, per app, the data sent, received and estimated as saved and the number of lookups and blocks, by hour, for 90 days; App management clears them on request. Lookups that are not blocked are forwarded to the DNS servers of the network you are on (your carrier or Wi-Fi), the ones your phone would ask without Sweep. A public resolver is used only if you choose one in More, under DNS server, or while the network offers none (then Cloudflare 1.1.1.1). From version 0.7.1 you can instead enter one encrypted server there (https://… for DNS over HTTPS, tls://… for DNS over TLS, sdns://… for DNSCrypt); lookups are then sent to it encrypted. Unless you enter an encrypted server, or while it cannot be set up (the app’s DNS server screen then says so), the lookups are sent as ordinary, unencrypted DNS, even if your phone would otherwise encrypt them with Private DNS. The server that answers sees the domain names and your IP address under its own privacy policy. AZET does not receive them. The app contacts AZET for the following. (1) The license check: the product name, a random device ID and the platform; if you enter a license key, also the key and the fixed device name “Android”. (2) Filter lists from sweep-api.azet.io (from 0.7.1 together with a table of domains and the companies behind them, used to show company names in the log), and the plan prices from suite-api.azet.io when you open the upgrade screen. (3) A version file from azet.io when the app starts and once a day and, when you accept an update, the new app file. These downloads carry no account and no device identifier; like any web request they reveal your IP address to Cloudflare, Inc., which hosts them. (4) Only if you choose to: a suspicious-text report. Sweep never reads your messages by itself and has no SMS permission. When you paste or share a message into the report screen, tick the consent box and tap Send report, the app sends that text (up to 2,000 characters), the first link in it, the app version and the Android version. It sends no sender, no contacts and no device identifier, so we cannot find your report later to delete it; remove names, phone numbers and other personal details before sending. We use these reports to detect scam messages and dangerous links, and delete them after one year. The report service does not store your IP address; it keeps an hourly abuse-limit counter against a one-way keyed hash of the address, separate from the report, and deletes it within three days. “Report a wrong block” opens a form on azet.io in your browser with the blocked domain filled in, and sends what you enter there. Filter lists you add yourself are downloaded from the address you enter. The app contains no analytics or advertising tools. If you are still on version 0.3.0: it forwards lookups to Cloudflare’s public resolver (1.1.1.1) by default instead of your network’s servers, and sends your phone’s model name as the device name when you enter a license key. Updating to 0.4.0 or later ends both.
Sweep for Android: checking a message with AZET Nunchi (from version 0.6.4; added October 8, 2026; applies now). Only if you choose to: when you paste or share a message into Sweep, tick the consent box and tap “Check for a scam with AI”, the app sends that text (up to 2,000 characters) to sweep-api.azet.io, which passes only the text to AZET Nunchi, AZET’s own AI model on the AZET AI API (api.azet.io), and shows you its answer: whether the message looks like a scam, why, and what to do. Nothing is sent before you tick the box. The text is used only to produce that answer. Neither service stores or logs it, and it is not used to train the model; it carries no sender, no contacts and no device identifier. The model runs on Cloudflare Workers AI, so Cloudflare, Inc. processes the text, possibly outside your country, under its own terms. The service keeps an hourly abuse-limit counter against a one-way keyed hash of your IP address, not the address itself, and deletes it within two days. Sending the same message as a report (section above) is a separate, optional step.
Sweep browser extension (Chrome, Edge and Firefox; added October 6, 2026; applies now). Tracker and scam-site blocking and the dashboard run in your browser: the sites you visit and what was blocked are not sent to AZET. The extension contacts AZET for three things. (1) Block lists and settings from sweep-api.azet.io, checked every 15 minutes. These downloads carry no account and no device identifier and, like any web request, reveal your IP address to Cloudflare, Inc., which hosts them. (2) The license check described above, only after you start a trial or enter a license key, then at most once a day. (3) Only when you press Send: a report about a page or a feedback message, with the items listed in the table above. Nothing is sent when you only open the form. The report service does not store your IP address, so we cannot link a report to you; reports are deleted after one year. In Firefox the extension declares this as browsing activity (required, because reports are part of the extension) and technical data (optional: if you decline it at install or later in about:addons, reports go out without the versions and diagnostic details). The extension contains no analytics or advertising tools.
AZET Shield (open beta at shield.azet.io). AZET Shield is different by design: its server agent reports attacks on your server to your hosted dashboard. This is the complete list of what our agent sends. Once, when you install it: the one-time enrollment token, the server’s hostname, the name of its operating system, the CrowdSec version, and the address you ran the installer from (so that address is allowlisted and you are not locked out). Then, every minute, for each new alert the server’s own detection engine decided: the alert’s local number, the source IP address, the name of the rule that matched, the number of events, and the start time. The agent does not read or send log lines, file paths or usernames. Its requests are signed with a key issued at enrollment and, like any web request, reveal the server’s IP address. An attacking address reported by at least three separate workspaces in the last seven days is added to a community blocklist that other workspaces’ servers receive; only the address is shared, not which workspace reported it. The dashboard has no accounts: we store a hash of your access token, not the token. If you give an email address for alerts, we mail it only after you confirm it through the link we send, and every mail has an unsubscribe link; mail is sent through Cloudflare, Inc. Alert and scan mails contain the server’s hostname, the attacking IP addresses and the findings. Vulnerability scans run on our hosted scanner (Cloudflare, Inc.) on your plan’s schedule, and only against sites you have proved you own; ownership is checked again before each scan. We store the site’s host name and the findings (the check that matched, its severity and the address it matched). On the Surface plan the scanner also looks up your domain name in public certificate and DNS sources and checks the hosts it finds, to list subdomains, open ports, web services, certificates and lookalike domains. It runs only for sites proved by a DNS record, and its results are stored and deleted like other findings. When a scan finds subdomains that were not there the previous time, we email you the new ones. How long we keep it. The dashboard shows 30 days of attack history on the Free plan and 90 days on paid plans; attack and activity records are deleted after 90 days on every plan. Findings are replaced by the next scan of the same site, and deleted after 90 days or when you remove the site; records of finished scans are deleted after 90 days and the mail log after 7 days. Creating a workspace is rate-limited with a one-way keyed hash of the requesting IP address, deleted the next day; the address itself is not stored. A workspace, its servers, sites, allowlist and blocklist stay until you remove them: Settings > Delete this workspace deletes the workspace and everything that belongs to it at once, or write to hello@azet.io. CrowdSec. The installer also installs the open-source CrowdSec engine and its firewall component from CrowdSec’s own package repository, and the server fetches packages and detection-rule updates from CrowdSec. The installer leaves the engine unregistered with CrowdSec’s central service, so the engine does not send attack signals to CrowdSec or receive CrowdSec’s blocklist unless you turn that on yourself; if you do, that exchange is between your server and CrowdSec under CrowdSec’s privacy policy. A CrowdSec engine that was already on the server is left as it was.
Packet analyzer (pcap.azet.io; added October 9, 2026; applies now). The capture file you choose (pcap or pcapng) and its results are processed only inside your browser; we do not receive, store or view them. The page downloads only its own files and the detection rule files from our server and talks to nothing else (no analytics). As with any web request, Cloudflare, Inc., which hosts it, sees your IP address and browser information, but we do not keep request logs for this service. If you click a VirusTotal link on the results, that file’s hash goes to VirusTotal (an outside service run by Google). User names and passwords in the results are masked by default. You are responsible for having the right to analyze the file and a lawful basis for any personal information in it.
AZET Pass (beta, pass.azet.io). AZET Pass encrypts your vault on your device with a key made from your master password; the server at pass.azet.io never receives your master password or that key. The server stores: your email address and the name you give, if any; a hash of your master password hash (hashed again on the server with PBKDF2) and the key-derivation settings; your password hint, if you set one, in plain text; your encrypted vault (logins, cards, identities, notes, folders, passkeys, attachments and Sends, all encrypted on your device); your encryption keys, themselves encrypted; the devices you sign in on (type, name and an identifier the app makes) and their last sign-in; and, if you enter one, your license key and its plan and end date. When you enter a license key, the server sends the key, the product name and your account ID to suite-api.azet.io to check it. Website icons: if “Show website icons” is on (the default), the app asks pass.azet.io for each saved website’s icon, so our server sees those website domain names; it fetches the icon itself so the website does not see your IP address, and does not store which account asked. Turn the setting off to send no domain names. The server keeps no request logs. You can delete your account in the app (Settings, Account security, Delete account), which removes everything above, attachments included, from our servers at once. If you forget your master password, we cannot recover your vault.
AZET Care for Android (beta) and for iPhone (added October 6, 2026; applies now). AZET Care reads your files, apps, storage and settings on the phone to find what can be cleaned and to score your security settings; file names, the list of installed apps and scan results stay on the phone and are never sent to AZET. Files are deleted only after you confirm them on screen. The app contacts AZET for the following. (1) The license check described above (the device name is the fixed word “Android” or “iPhone”), and the plan prices from suite-api.azet.io when you open the plans screen. (2) On Android, a version file from azet.io and, when you accept an update, the new app file. On Android, the app also downloads updated cleanup lists from suite-api.azet.io (the folder and file-name patterns it may offer to clean: thumbnails, screenshots, temporary files, messenger media and ad caches); the request carries only a random one-time value the app makes. On iPhone, the list of current iOS versions from suite-api.azet.io, to tell you whether your iPhone is up to date. These requests carry no account and no device identifier; like any web request they reveal your IP address to Cloudflare, Inc., which hosts them. (3) Only if you switch on “Share anonymous usage counts” (off by default, Android): once a day, yesterday’s totals of screen and action names, with the product, the app version and the Android version. No device ID, no file names and no app list are included; we keep only daily totals per version. (4) Only if you use it: the waitlist form in the app, which sends your email address, the product and the plan. The iPhone app is not on the App Store yet; this describes it as built. The app contains no advertising tools.
AZET Care for Mac (added October 6, 2026; applies from its release). The checkup, cleanup, app and threat scans run on your Mac; file names, your list of apps and scan results are not sent to AZET. It contacts AZET for: the license check described above (device name “Mac”, never your computer’s name); the list of current macOS versions, settings for the app (feature switches and notices) and updated threat-detection rules from suite-api.azet.io, which carry no identifier; app updates from azet.io; and only if you choose to, usage counts (off by default, as described for Android, with the macOS version) and the newsletter or waitlist email you enter. To show available updates for your other apps, Care asks Apple’s public App Store lookup about each App Store app by its bundle ID, and fetches each other app’s own update feed from that app’s developer; those servers see your IP address and the app they are asked about, under their own policies. The built-in KnockKnock listing runs with VirusTotal turned off, so nothing is sent to VirusTotal.
AZET Care for Windows (added October 6, 2026; applies from its release). Security, privacy and cleanup checks run on your PC and their results stay there. It contacts AZET for the license check described above (device name “Windows PC”), the plan prices, update checks against azet.io, and, only if you use it, the waitlist email you enter. When you open the apps list, it asks winget’s community source (operated by Microsoft) for newer versions of installed apps, and updates an app through winget only when you pick it; Microsoft and the app’s publisher see those requests under their own policies. It contains no analytics or advertising tools.
Pocket Games: Offline Puzzles for Android (com.neulketing.pocketgames; added October 28, 2026; applies now). Pocket Games has no account or sign-in, and AZET runs no server that receives data from it. Your best scores, levels and sound setting are stored only in the app’s own storage on your phone and are never sent to AZET; uninstalling the app or clearing its data deletes them. The app is free and shows ads from Google AdMob (Google Mobile Ads SDK), with Google’s User Messaging Platform for consent. To show ads, measure and analyze them, prevent fraud such as invalid clicks, and manage consent where the law requires it, the SDK automatically collects the following and shares it with Google LLC: your IP address, which can be used to estimate your approximate (city-level) location; app interactions, such as app launches, taps and ad and video views; diagnostics, such as launch time, hang rate and energy use of the app and the SDK; and device identifiers, the Android advertising ID and the app set ID. This data is encrypted in transit (TLS). Google and its ad partners may also use cookie-like technologies, device identifiers and your IP address to read or store information while serving ads. AZET does not receive or keep this data; in AdMob we see only totals such as impressions, clicks and earnings. Google uses it under the Google Privacy Policy; see also how Google uses information from sites or apps that use its services. Your choices. The advertising ID is optional: you can reset or delete it, or turn off ad personalization, in your phone’s Settings, under Privacy > Ads or Google > Ads (the names vary by phone maker and Android version). After you delete it, the app receives no advertising ID and Google may show you non-personalized ads. In the EEA, the UK and Switzerland, and wherever else Google’s consent message is required, the app shows that message before any ad is requested, and “Ad privacy settings” at the bottom of the game list lets you change your choice at any time. Every game works the same whatever you choose, and with no internet connection no ad is requested and nothing is sent. Pocket Games is intended for users aged 13 and over (14 and over in Korea).
azet agent, the AI coding agent for macOS (added November 12, 2026; applies now). azet runs on your Mac. Your code, files and prompts stay there, except what the agent sends to the AI model you pick: AZET AI API, or another company’s API with your own key, under that company’s terms. To count installs and active users, the installer, azet and azet app send anonymous usage counts to api.azet.io: a random install id made on your Mac, the azet version, the operating system and processor type, the event (install, start or task), how azet was started, and which model provider a task used. They never include your code, prompts, file names, paths or keys. Our server does not keep your IP address; it keeps only the country Cloudflare derives from it (two letters). Counts are deleted after 25 months. Turn them off with azet telemetry off or by setting AZET_TELEMETRY=0; delete ~/.config/azet/id to start over with a new random id.
AZET phone app for iPhone and Android, with pairing, relay and notifications (added November 13, 2026; applies now). The phone app is a remote for AZET on your own computer; it has no account of its own and contains no advertising or analytics tools. What you see and do in it (terminal output, agent chats, files, photos you attach, and voice dictation) travels between the phone and your computer encrypted end to end with keys made during pairing. When the two are not on the same network, that traffic passes through relay.azet.io, which forwards it without being able to read it and keeps only the routing records needed to connect your devices. The camera is used only on the phone to scan the pairing QR code. Dictation is transcribed on the phone or on your paired computer. If you allow notifications, the phone’s push token from Apple or Google goes to your computer, which registers it with push.azet.io; the notification text your computer sends (for example, that an agent finished or is waiting for you) is passed to Apple or Google to show it, and our server deletes delivery records after 24 hours. Turning notifications off or unpairing removes the token. To use the relay, AZET on your computer signs in to an AZET account at login.azet.io with your email address and a one-time code we email from login@azet.io; we keep the email address and sign-in sessions until you ask us to delete the account (section 11).
Sweep for Safari
Sweep for Safari is in development and not on the App Store yet. This section describes the app as built, and applies from its release.
Short version. Sweep for Safari collects no data. It has no account, no analytics, no advertising and no crash reporting. It cannot see the pages you visit.
How blocking works. Sweep gives Safari lists of rules. Safari applies them itself, on your device. Safari does not tell Sweep which pages you open or what it blocked, so Sweep has nothing to record and shows no block counts.
What stays on your device. Your choices (which categories are on, which optional lists you turned on, the websites you allowed, whether automatic updates are on), the downloaded block lists, and the Activity list (up to 200 entries: list updates, reloads and the changes you made, including the names of websites you allowed). They are stored in the app’s own storage on the device, are not synced, and are removed when you delete the app.
What Sweep does online. One thing: it downloads block lists, when you tap an update button and in the background about twice a week (you can switch automatic updates off in Settings).
- From sweep-api.azet.io (AZET): the list index, Sweep Base, Sweep Trackers and Sweep Security.
- From raw.githubusercontent.com (GitHub): the StevenBlack ad-hoc list.
- Only if you turn the optional list on: easylist.to (EasyList, EasyPrivacy), filters.adtidy.org (AdGuard filters), raw.githubusercontent.com (1Hosts Lite, uBlock filters).
These requests contain no account, no device identifier and nothing about your browsing; the only extra header is the app’s name. Like any download, the server that answers sees your IP address. Our list server does not write these requests to a database. Our hosting provider (Cloudflare) and the third-party hosts above process the IP address to deliver the file under their own policies.
Things you start yourself. “Contact support” opens your mail app, and “Report a problem with a website” and “Privacy policy” open web pages in your browser. What you send there is covered by the rest of this policy.
Purchases. You buy Sweep from Apple. Apple handles payment and refunds and does not give us your name, email or payment details.
Children. Sweep collects no data from anyone, including children.
Changes and contact. If a future version changes any of this, this page is updated before that version is released. Questions: hello@azet.io. AZET LLC.
We do not collect sensitive information such as political or religious beliefs, health, or sex life.
Children. Our website and apps are not directed to children. We do not knowingly collect personal information from children under 13 (under 14 in Korea). If you believe a child has given us information, write to hello@azet.io and we will delete it.
2. How we use your information
- To receive and respond to inquiries and share consultation results
- To enter into and perform service contracts, settle payments, and issue invoices
- To operate and improve our services and analyze usage
- To meet our legal obligations
3. How long we keep it
We delete personal information promptly once its purpose has been fulfilled, unless the law requires us to keep it for a set period.
| Record | Retention | Basis |
|---|---|---|
| Inquiry and consultation records | 1 year after the purpose is fulfilled | Internal policy |
| Partner and sales inquiries | One year from the day we receive them, then deleted automatically | Internal policy |
| Waitlist sign-ups | Until we send the launch notice, or until you ask us to delete them | Internal policy |
| Store waitlist for security apps (email, product, plan) | Until the checkout notice is sent, or until you ask us to delete it | Internal policy |
| Security app trial records (device ID, product, platform, trial dates) | 1 year after the trial ends | Internal policy |
| Security app license records (key hash, plan; per activated device: device ID, platform, device name) | While the license is in use; a device’s record is deleted when you release its seat, and the rest when you ask us to delete it | Internal policy |
| Abuse-limit counters of the license and report services (one-way keyed hash of the IP address, and the hour) | Deleted within 3 days | Internal policy |
| Sweep suspicious-text and blocking reports, and Sweep browser extension reports and feedback | 1 year | Internal policy |
| AZET Shield attack and activity records, scan findings and finished scan records | 90 days (findings are replaced sooner by the next scan of the same site) | Internal policy |
| AZET Shield workspace (alert email, servers, sites, allowlist, blocklist, token hash) | Until you delete the workspace in Settings or ask us to | Internal policy |
4. Sharing with third parties
We do not provide your personal information to third parties, except in the case below, with your prior consent, where the law specifically requires it, or when law enforcement requests it through lawful procedures.
Inquiries about advertising and marketing services in Korea are received directly by AZET (Korea), the separate Korean business that provides them (ads@azet.io; see the AZET (Korea) privacy policy, in Korean). If you send such an inquiry to hello@azet.io, we forward that email (your name, company, phone number, email and the inquiry itself) to AZET (Korea) so that it can answer you, only for the purpose you wrote for and over encrypted transport (Article 17(4) of the Personal Information Protection Act of Korea and Article 14-2 of its Enforcement Decree); AZET (Korea) keeps it for the period in its policy.
In Pocket Games, the Google Mobile Ads SDK sends the IP address, app interactions, diagnostics and device identifiers described in section 1 directly to Google LLC (United States and other countries where Google operates), whenever an ad is requested or shown, for advertising, ad measurement and analytics, fraud prevention and consent management. Google keeps it under its own privacy policy. You can limit this as described in that section.
5. Service providers
We use the following service providers to run our services. Our agreements with them require that personal information be handled securely, and we oversee their compliance.
| Provider | Service |
|---|---|
| Cloudflare, Inc. | Website hosting and infrastructure, including the license, filter-list and AZET Shield services and AZET Shield alert mail, and running AZET Nunchi (Workers AI) for Sweep message checks |
| Google LLC | Email, and website analytics (Google Analytics) on the home page, guides, and product, pricing, contact and terms pages |
Because of this, your personal information may be transferred to and processed in countries where these providers operate, including the United States.
6. Cookies and analytics
azet.io uses Google Analytics on the home page, on our advertising and marketing guides, and on product, pricing, contact and terms pages to count visits and see how those pages are used. It sets first-party cookies only; Google signals and ad personalization are turned off. Other pages, such as company, download and policy pages, do not load it. Cloudflare Web Analytics counts page views on every page without cookies. azet.io does not load advertising pixels or session-recording tools, and other parties do not collect information about your activity across other websites through azet.io. Details are in the Cookie policy. You can block cookies in your browser settings; the site still works without them. Our website does not currently respond to “Do Not Track” browser signals.
7. Your rights
You can ask at any time to access, correct, delete, or stop the processing of your personal information. Send your request to the contact below by email or phone, and we will act on it without delay. You may also exercise these rights through a legal representative or an authorized agent.
8. Your California privacy rights
If you live in California, the California Consumer Privacy Act, as amended by the California Privacy Rights Act (together, the “CCPA”), gives you the rights below, to the extent the CCPA applies to AZET. The categories of personal information we collect, where they come from, why we use them, and who we disclose them to are described in sections 1, 2, 5, and 6.
- Right to know. You can ask what personal information we have collected about you, the sources, why we use it, the categories of recipients, and for a copy of the specific information.
- Right to delete. You can ask us to delete personal information we collected from you, except records the law requires us to keep (section 3).
- Right to correct. You can ask us to correct personal information that is inaccurate.
- Right to opt out of sale or sharing. AZET does not sell personal information. The only sharing for cross-context behavioral advertising is in Pocket Games, where the Google Mobile Ads SDK may use your advertising ID for personalized ads. To opt out, delete your advertising ID or turn off ad personalization in your phone’s settings, or change your choice under “Ad privacy settings” in the app where it is shown, as described in section 1. Nothing else we offer shares personal information for advertising.
- Sensitive personal information. We do not collect sensitive personal information (section 1), so we do not use it for any purpose that would give you a right to limit it.
- No discrimination. We will not deny you service, charge you a different price, or give you a different quality of service because you exercised these rights.
How to make a request. Email hello@azet.io with the subject “California privacy request,” tell us which right you want to exercise, and include the email address you used with us, for example to join the waitlist. To protect your information, we verify requests by matching them to information we already hold, such as asking you to confirm from that email address. We will respond within 45 days; if we need more time, we will tell you why and may extend this once by up to 45 more days.
Authorized agents. You may have an authorized agent make a request for you. Unless the agent holds a valid power of attorney, we may ask for your signed permission and ask you to verify your identity with us directly.
9. How we delete information
When the retention period ends or the purpose is fulfilled, we delete personal information without delay. Electronic files are permanently deleted using methods that prevent recovery, and printed records are shredded or incinerated.
10. How we protect information
- Access limited to the minimum number of staff, with managed permissions
- Encryption in transit (HTTPS)
- Access logs retained and protected against tampering
- Physical and technical controls against unauthorized access
11. Contact
If you are in Korea, you can also contact the Personal Information Dispute Mediation Committee (1833-6972) or the Personal Information Infringement Report Center (118) about a privacy concern.
12. Changes to this policy
If we add to, remove from, or change this policy, we will post a notice on the website at least 7 days before the change takes effect.