Sign inCreate an accountStart freePrivacy policy
What Align collects about you, why, who it passes through, and how to see, correct or delete it.
In force from 17 November 2026.
Who holds it
NETLCO, Nomad Enterprise TechSolutions Limited, of Trinidad and Tobago, runs Align and answers for everything it collects. Write about anything on this page to:
What stays in your browser
Everything you measure stays here, and so does the sound it is measured from: your transfer functions, traces, captures, sessions and calibration files are kept in this browser and never sent to us, but for the four-mic hour's delays, which a test report sends only if you tick its box for them, and the lines Align's Real-time magnitude graph draws, with their names, and the newest rows of its live spectrograph and the live line of its RTA, which pass through our server only while you have a phone paired as Align's remote, and are not kept; the part on the phone remote, below, says how. So are your settings, but for the few the usage log below names, what the phone remote's replies show, and how Align's Real-time magnitude graph draws its lines, which the phone remote is sent so it draws them the same way. An Align admin can send you a copy of their own view settings, the look, graph layout, ranges and analysis settings; it waits on our server under your account only until your browser next opens Align, which takes it and deletes it; you can change any of them after, as before. The names of the songs in your player's list stay here too, but while a phone is paired as Align's remote, which is sent them. A test run's progress, your answers and your notes stay here too until you delete the run, whether you send it or not.
A browser that keeps Align offline also keeps, in that browser's storage, a random id for the browser, your account's number, the pass that lets Align open offline, when it ends and the keys that check it, the secret it checks in with and the next one it made, when Align's server last answered and the code and time of its last refusal, Align's own count of how long it has been open there, the latest time reached by the browser's clock or by that count, the open time since the last check-in during which the clock read earlier than that or the count's two copies disagreed, and the time of that check-in with how far the browser's clock was from Align's server's, with a second copy of that count kept apart from the first, and whether its two copies disagreed, the day it last told you the pass ends soon, and a copy of Align's own pages, so that it opens offline. Clearing the browser's data for Align removes them.
Once you sign in, your browser also keeps whether your account is an Align admin or a tester, as our server last said, deleted when you sign out, or the next time Align checks and finds you signed out or no longer one.
Your answers to Help improve Align and Adverts that brought you here are kept in this browser under align.helpImprove.v1 and align.adverts.v1, and nowhere else. When Align last asked the Help improve Align question is kept in this browser under align.helpImprove.asked.v1, so a question you close without answering is not asked again for six months. It holds only that date, and nothing is recorded or sent because of it.
What Align collects, and why
Your account
NETLCO, or the system engineer Align is built for, makes most accounts. You can also make a Free account yourself by signing in with Google, Microsoft or GitHub: Align then makes an account with a sign-in name it chooses, never your email, no password, and the email that company says is verified, if no other account has it. You can ask for an account at align@netlco.com, which both read, and for a new password there too, or with Forgot your password on the sign-in once your account has an email. Align keeps:
- a number for the account
- its username
- the name shown for it
- an email address, if you or we set one
- a scrypt hash of its password in place of the password
- how many wrong passwords were tried in a row
- when a pause after too many ends
- whether it is turned off
- when you asked for it, until NETLCO answers
- the email address your sign-in gave when you asked for it, to tell you it is open, until NETLCO answers
- when its password was set
- whether you have chosen its password yourself, and when
- when it last signed in
- the language its emails are written in when no page of yours sends them (a receipt, a change an admin makes), taken from the language you last agreed to the terms in
- whether it has Pro, and until when
- whether we gave it Pro ourselves, without a purchase, and until when, so that a payment taken back never takes that away
- a copy of an admin's view settings sent to you, until your browser next opens Align, which takes it
- when it was made
- when it last changed
- whether an Align admin turned on the Tester switch for your account, which admin and when; deleted when the switch is turned off or your account is deleted. The admin record that the switch was turned on or off is kept one year, like every admin record.
It keeps them to let you in and to stop anyone guessing your password, until NETLCO removes the account or you ask us to. Align uses the email only to let you sign in with it in place of your sign-in name, to send you a code when you forget your password or confirm a new address, and to tell you when your password is reset, when the email changes, at the old address too, and when it is set on Align's admin page, and to send your receipt when you buy Pro, and to tell you if someone tries to make a new account with your email; it sends nothing else to it.
NETLCO and the system engineer Align is built for see each account's name, email, plan, state, last sign-in and whether its owner chose its password; the browsers that keep Align offline for it, when each was added and when its pass ends; how many of its 3 swaps in any 30 days it has used; whether it is measuring now, and since when; the countries its check-ins came from; and any sign that Align's licence was tampered with; on Align's admin page, never its password, to make, change and support accounts, to send an account a copy of their own view settings, and to turn on a Tester switch for an account, which shows a Pro account the tools still being tested, marked Tester. The admin page also lists new accounts as they are made and sales to check, and counts how many browsers used Align each day, never which account they belong to. Each change made there is recorded: who made it, what it was, the account's sign-in name, when, and the plan's end, the browser's name, whether an email was set, changed or removed, or whether the Tester switch was turned on or off, never a password or an email address. Each record is kept for a year from the change, then deleted by a cleanup we run once a day, even if the account is removed first. Align also keeps which accounts open the admin page, and since when, until each is taken off that list or removed.
Removing the account leaves the messages you sent from Help and your test reports, each deleted once it is acted on, or sooner if you ask; NETLCO's copies of the emails Align sent you, kept until we delete them; and your name may stay in the team's working records after the account is gone.
When you sign in with a password you are given, Align asks you to choose your own before anything else opens, and once you have chosen it, the one you were given no longer opens the account.
Signing in with Google, Microsoft or GitHub. If you choose one of these, you sign in on that company's own page, and it tells Align who you are. Align keeps the company's name, the fixed number it gives you for Align, and when you linked it. If the company says your email is verified and your account has no email yet, Align keeps that email as your account's email. Align keeps nothing else the company sends, such as your name or picture, and never your password there. That company learns that you signed in to Align, and when, under its own privacy policy. With a work or school Microsoft account, your organisation can see that too. You can unlink any of them on Your account; we delete the link then, and with your account if it is removed.
When you agree to our terms, we keep a record of it: your account, the date and time, which version of the terms you agreed to, the screen where you agreed (sign-in, choosing your password, or Buy), the words that screen showed and, where we recorded it, the language those words were in. We keep it so we can both see what was agreed if a question ever comes up. We keep it while your account is open, and it is deleted with your account. When you agree on the free tools without an account, the record stays in your own browser and is not sent to us.
When you ask for a code, Align keeps a record of it: which account it is for, none for a code that makes a new account, whether it resets your password, confirms a new email, makes a new account, or opens Align's admin page, and the new email, or the email you are signing up with; a fingerprint of a random key kept in your browser and one of that key and the code together, never the code; when it was made, when it stops working, 15 minutes later, and when it was used; and how many wrong codes were typed. It keeps them to send an account no more than 3 codes of each kind in an hour, an email you are signing up with no more than 3 from one browser and 10 in all, and to let only the browser that asked use a code. A cleanup we run once a night deletes each record once it is a day old, so none lasts more than two days.
Making an account
To make an account you give your email address. We email a code to it to check it is yours, then you choose a password and tick that you are 18 or older and agree to the Terms of use and this policy.
We check the part of your email address after the @ against a list of throwaway email services kept inside Align. Nothing is sent anywhere for this check.
To stop you choosing a password that has already leaked from another site, Align turns your password into a code (a SHA-1 hash) and sends only the first 5 characters of that code to Have I Been Pwned's Pwned Passwords service. It answers with hundreds of possible matches, and Align checks them itself. Your password and the rest of its code never leave Align.
On the sign-up, forgot-password and Contact pages, and on sign-in after 3 wrong tries from one address in 15 minutes, Align shows Cloudflare Turnstile, a check that you are a person. Your browser loads it from challenges.cloudflare.com, and our server sends Cloudflare the check's answer and your IP address to confirm it. Cloudflare uses what it reads, such as your IP address and browser details, to tell people from bots, not to identify or advertise to you. Cloudflare is in the United States.
We write down each attempt to make an account that reaches our checks, whether we let it through or not: when, how you signed up (email, Google, Microsoft or GitHub), your IP address and its network, the email address, an id for your browser, the result with its reason, and which account it made, if any. We use it only to stop abuse, and we delete each entry after 90 days, or sooner with the account it made.
If someone abuses Align, an admin can bar an IP address or network for up to 30 days, renewed only for a stated reason, or an email address or browser for longer. A bar on an account also bars the network, email address and browser it was made with, and its email now, and it stays if the account is deleted, so the same person cannot simply start again. Each bar records what is barred, why, who set it, when, until when, the account it came from, and, if it is lifted or renewed, who did it and when, and for a renewal why. A bar on an email address or browser ends after 2 years unless an admin renews it for a stated reason, and is deleted when it ends. If you think we have barred you by mistake, write to align@netlco.com.
We also note each time an account is made, signed in to, turned Pro or Free, switched off or on, or locked, with when and who did it. This note holds the account's number and, for a new account or a sign-in, how it was made or signed in to (email and password, Google, Microsoft, GitHub or by us), never your address, email, name or browser. We keep the sign-ins to spot one that was not yours and to answer a question about a sign-in that failed, and delete each after 90 days; every note is deleted with the account.
Your browsers
When a browser keeps Align offline, it makes an id for itself at random, from nothing read off your computer, and Align's server keeps, for each browser on your account:
- the id it made, and that it is a browser
- the browser and system it runs on, like Edge on Windows, never your computer's name
- which of your 2 seats it holds
- a fingerprint of the secret it checks in with and of the one before it, which each check-in replaces
- the newest pass Align's server signed for it, when it was signed and when it ends
- whether you or we added it, when it was added, when it last signed in to keep Align offline, and when it last checked in
- whether it was signed out as a copy, and when
- the highest open time, by Align's own count, it has sent at a check-in since it last signed in to keep Align offline, and which sign-in that was, so setting its clock back cannot stretch its pass: a check-in sending a lower one, past a small allowance, is refused as a copy is
- whether its removal was asked for, when and by whom, and when its seat was freed
- each sign-in that turned Offline on in it: when it was made, when it took the seat, and when a copy being caught ended it
- each swap, a browser added after your account's first 2 or one signed in again without the secret it checks in with: when, whether it counted toward the 3 in any 30 days, and whether we made it
- a note each time a browser takes a seat on your account, or signs in again after its removal was asked for, with its name and when
- a fingerprint of each one-time code a sign-in asks for to turn Offline on, which sign-in asked for it, and when it was made and traded
- where each check-in came from: the country its address belongs to, never the address itself, with the time and which browser checked in, kept 90 days
- each sign of tampering Align's server sees, a copy of a browser caught, a third browser or a swap past the limit refused, or a browser's open time coming in lower than before, with what it saw, never your address, when, and which browser
A browser caught copied, or whose open time comes in lower than before, is signed out at once and can sign in again; nothing happens to the account itself before a person at NETLCO reads the record, which is kept a year and deleted with your account.
The browser checks in with Align's server when Align opens online and every hour while it is open and online, sending your account's number, the browser's id, its secret, the next one it made and how long Align has been open in it, by its own count. Each pass holds your account's number, the browser's id and its seat, when it was signed, when it ends, when your Pro ends and Align's address, and Align's server signs it, so a pass changed in the browser no longer opens Align.
Align keeps these to hold your account to 2 browsers, 3 swaps in any 30 days and 30 days offline (3 days at a time while your cancel days are open), to sign out a copy of a browser, and to stop Align opening offline once your Pro ends. A browser's record, its sign-ins and its notes are kept until the account is removed. Each swap is kept for 30 days from when it was made, and each one-time code for a day, then deleted by a cleanup we run once a day.
Measuring in one place at a time
While Align measures, the page asks Align's server every 2 minutes whether your account's turn to measure is still its own, under a random id it makes each time it loads. The server keeps one record of the turn for your account: that id, that it is a browser, and when the turn was taken and when it last asked. Align keeps these so that one place measures at a time: starting to measure in another browser or tab asks whether to measure there instead, and a turn that has not asked for 150 seconds is taken without asking. While your account is measuring, Align's admin page shows NETLCO and the system engineer Align is built for that it is, and since when, from the same record; it cannot show where. The record is deleted when Align stops measuring or closes and lets the turn go, otherwise replaced the next time your account starts to measure, and always deleted with the account.
Cookies
Align itself sets no cookie for advertising. Once you allow it under Help improve Align, Google Analytics and Microsoft Clarity each set two cookies of their own on Align's public pages, as that section says. These are all the cookies a browser holds from Align itself:
__Secure-authjs.session-token
Align's
Keeps you signed in. Set only once you sign in.
Lasts: up to 30 days after your last signed-in visit online for the sign-in that turns Offline on, or until you sign out; any other sign-in stops signing you in after 14 days without a visit
__Host-authjs.csrf-token
Align's
A random token that stops another site sending a sign-in in your name. Set only while Align's sign-in is on, by every page but this one, the notices, Prices, Training, the tool pages and the phone remote's page.
Lasts: Until you close the browser
__Secure-authjs.callback-url
Align's
The page to come back to after signing in. Set only while Align's sign-in is on, by every page but this one, the notices, Prices, Training, the tool pages and the phone remote's page.
Lasts: Until you close the browser
__Host-align-code
Align's
A random key that lets only this browser use the code we email you. Set each time a code is asked for, whether or not an account matched.
Lasts: 15 minutes
__Host-align-device
Align's
A random id for this browser, never for you, which the record of each sign-up attempt keeps, to stop abuse. Set when you ask for the code that makes an account, or sign in with Google, Microsoft or GitHub for the first time.
Lasts: A year from when it is set
__Host-align-link
Align's
A random pass that ties the company you sign in with to your account. Set only while you link a sign-in from Your account.
Lasts: 10 minutes
__Secure-authjs.pkce.code_verifier
Align's
A random key that proves the answer from Google, Microsoft or GitHub is for this browser. Set only while you sign in with Google, Microsoft or GitHub.
Lasts: 15 minutes
__Secure-authjs.state
Align's
A random value that stops another site finishing a sign-in with Google, Microsoft or GitHub in your name. Set only while you sign in with Google, Microsoft or GitHub.
Lasts: 15 minutes
cf_clearance
Cloudflare's
The result of Cloudflare's check for bots, which a script it adds to Align's pages makes again at least every 15 minutes. It belongs to netlco.com, so your browser sends it only to NETLCO's sites.
Lasts: A year
Your IP address
Align reads it only to limit how often one address can try a password (10 wrong ones in 15 minutes, and after 3 wrong ones in 15 minutes it asks for the check that you are a person), ask for a code to reset your password, confirm a new email or make an account, or, for NETLCO's admins, take the extra step into the admin page (5 in 15 minutes), use a link we emailed you to choose your password (10 tries in 15 minutes), send a message from Help (5 in 10 minutes), send a message on the Contact page (5 in 10 minutes), send a test report (5 in 10 minutes), send the usage log, come back to Align from WiPay after paying (20 a minute), or, to keep Align offline, check in (20 times a minute), trade a sign-in code (20 a minute) or ask for one (10 a minute), or, to measure in one place at a time, ask for your account's turn (20 times a minute). For these limits it is held only in the running server's memory and never written down; Making an account above says what the sign-up record and a bar keep of it. When you check in to keep Align offline, Align also keeps the country your address belongs to, never the address itself, with the time and which of your browsers checked in. We keep these for 90 days, to spot one account used in two places at once; a person at NETLCO looks at any such alert before anything happens to the account.
Cloudflare, which carries every visit to Align, adds to each request the country your IP address points to. To show you one choice or two, and to know which of them applies to Meta's pixel, Align reads that country once a page load and keeps only its answer, one or two, in that page until you leave it. Align does not save or log the country it reads for this, or send it to your browser.
Messages from Help and the Contact page
When you use Help, Send feedback, or send a message on the Contact page, Align keeps:
- a random id the page gives it
- when it arrived
- your message
- an email address, only if you give one, to reply to you
- your account's name
- the screen you sent it from
- which build of Align received it
- whether one of our own test runs sent it
- on the Contact page, the topic you chose, and the name you typed if you were not signed in
The team that builds Align, and the system engineer it is built for, read it to act on it, and use the email only to reply to you. Each message is deleted from Align's database once it is acted on, or sooner if you ask; an email sent to you in reply goes through the provider of the mailbox it is sent from and stays in that mailbox. A message's words, and its email and account name when we reply, may also stay in the working records of the AI tools we read it with, for as long as that work goes on and a month or more after, and with Anthropic as its own policy says.
When a message comes in from the Contact page, we email our own mailbox to say one came, its topic, whether you left an email, and when. That email never holds your message, your email or your name.
Test reports
When you follow a plan in Help, Test Align and press Send, Align keeps what the preview showed you:
- a random id for the run, and one for each version of it you send
- when it arrived
- your account's name
- which test plan it follows
- which build of Align received it
- your browser's brands and versions, the platform, and the sizes of your screen and window
- when the run started and finished
- for each step, which step it is, its result as Align ticked it and you answered it (Pass, Fail, Blocked or Skip), when, and what Align showed then: whether Offline was on and how much it had saved, whether you were online, whether Align was open in its own window, how many inputs were open, the sample rate, and whether the browser had agreed to keep Align's data
- what you typed for a step
- whether one of our own test runs sent it
- this browser's usage-log id, only if you tick the box for it
- each input's delay once a minute in the four-mic hour, only if you tick the box for it
Nothing of a run leaves this browser until you press Send, after a preview of every field; a Send made offline waits in this browser, up to 5 reports at a time, and goes the next time Align is open online. A report never carries audio, captures, traces, or device, file or channel names other than any you type in a note, and of what Align measures it carries only the four-mic hour's delays, when you tick their box. The team that builds Align reads each report to see where Align worked and where it failed, and to fix it. With the usage log's box ticked, the report holds this browser's usage-log id beside your account's name, so we can line your run up with the log's readings. Each report is deleted from Align's database once it is acted on, or sooner if you ask, and may also stay in the working records of the AI tools we read it with, for as long as that work goes on and a month or more after, and with Anthropic as its own policy says.
Help improve Align
This is off until you turn it on, and you can turn it off again at any time under Privacy choices at the foot of every page. Turning it on does four things. First, Align keeps the usage log described below. Second, on Align's public pages, /welcome, /what-it-does, /what-you-need, /prices, /training, /stage, /venues, /home-theatre, /car and /competition, Meta's pixel runs. A browser that sends Global Privacy Control never runs it. Meta then receives your IP address, your browser's details, the page you are on and the page you came from, the buttons you press there and the names of a form's fields, never what you type in them, with Meta's own cookie, so we can see which of our adverts bring people to Align. Meta uses what it receives under its own privacy policy, including for its adverts. The pixel never runs inside the tool or on your account pages. Third, on the same public pages, Google Analytics runs, so we can count which of them people visit and how they reached them. Google then receives the address of the page you are on without anything after a question mark, the page that sent you there, your browser and device, and your rough location, and sets two cookies of its own on Align's address, align_ga and align_ga_NBRRP3LWHW, which last up to two years unless your browser ends them sooner. Google says it does not log or store your IP address in Google Analytics. It never receives your name, your email, your account or anything you type. Google handles it under the Google Analytics terms and its own privacy policy, and may process it outside your country. Google deletes the detail of each visit after 2 months, the shortest it offers; the totals it adds those visits up into, such as how many people opened each page, stay in our reports. Fourth, on the same public pages, except in the places named below where you choose two things separately, Microsoft Clarity records how you use them, so we can see where they confuse people: where you move the pointer, click and scroll, and the page's layout with every word on it hidden, with your browser, device and screen size, the site that sent you, and your country, region and town or city. It never receives your name, your email, your account or anything you type. It sets two cookies of its own, _clck and _clsk, on netlco.com, the address Align's is part of, so your browser also sends them to NETLCO's other sites, and Microsoft may keep cookies of its own on its own sites, which its cookie list names as CLID, ANONCHK, MR, MUID and SM; Align cannot delete those, and your browser's settings can. Align tells Clarity not to share what it records with Microsoft's advertising, and not to set Microsoft's advertising cookie. Microsoft is its own controller of what it receives, under the Microsoft Privacy Statement, and may use it for its own purposes, including to create user profiles for purposes that include advertising, and may process it outside your country. We can watch each recording for 30 days, and the heatmaps made from them for up to 9 months. Align remembers your choice in your browser, as align.helpImprove.v1 and align.adverts.v1. Turning it off stops all four from then on and deletes Google's cookies on Align's address and both of Clarity's: what the usage log already holds is deleted by its usual cleanup, what Meta already received stays with Meta, what Google already received stays with Google and is deleted as above, and what Microsoft already received stays with Microsoft. A _ga cookie that Align's earlier version wrote on netlco.com may stay; your browser's settings can delete it.
Visitors in the European Economic Area, the United Kingdom, Gibraltar, Jersey, Guernsey, the Isle of Man and Brazil, and visitors whose country Align cannot tell, choose these two separately: there, Help improve Align turns on only the usage log and Google Analytics, and Adverts that brought you here only Meta's pixel. Microsoft Clarity never runs there.
The usage log
Only while Help improve Align is on, and while you use Align's instrument, its About page or the score window, the page reads what it costs your computer every 5 seconds and sends it to us every 30 seconds, to make Align faster and steadier on real machines, and to count on Align's admin page how much it is used. The tool pages, Prices and Training, which need no account, send none of it. It sends:
- Which Align page it was, whether it was in view, and how long it took to arrive and draw.
- Your browser and system as the browser describes them: its user agent and brand, the platform, whether it is a phone, how many processors and how much memory it reports, whether the page came over a secure connection and runs isolated from other sites' pages, and which of these readings it can give.
- The size of your screen and of the window, and its pixel ratio.
- What the page costs your computer: memory, slow tasks and frames with the code names of the scripts that ran in them, frame rate, timer delay, CPU pressure, how many elements the page holds, and the time the log itself takes.
- How you use the page, counted and never named: how many clicks, how many came three at once in one place without changing anything, how many landed on nothing that can be pressed, how long the page took to answer a press, and how much it moved by itself.
- How much Align keeps in your browser and how long its saves and reads take, counted, never what it keeps; whether the browser has agreed to keep it, and whether Offline is on.
- The connection as the browser estimates it, whether you are online, and how much the page loaded and the log sent.
- The battery level and whether it is charging, where the browser says.
- The audio engine's state: whether it is running, how many inputs it reads, and its FFT size and sample rate, and each time a page asks for your microphone, whether the browser allowed it or the browser's name for why not, how long it took and how many audio inputs it gave, never which device.
- When a script on the page fails: what kind of failure and where it failed, the script's address only if it is one of ours, never its message.
- Its own bookkeeping: how long each reading covers, and rows waiting to send or given up.
- With every reading: when it was taken and when it reached us, its place in the page's count, which build of Align sent it, whether one of our own test runs did, and the two random ids below.
It is filed under two random ids, one kept in this browser (align.telemetry.install in its local storage) and one for each page load, never your name, account or IP address. It never carries audio, captures, traces, file or channel names, device names, or anything you type.
Each row is kept for 90 days from when it reached us, then deleted by a cleanup we run once a day. To have your part deleted sooner, email us the id this browser keeps under that key, which its developer tools show under local storage, and we delete every row filed under it, then your email asking for it, which, like a message from Help, may also stay in the working records of the AI tools we read it with, for as long as that work goes on and a month or more after. A row we have read while studying the log may stay in those working records on the same terms. Email the id rather than send it from Help, which keeps your account name beside it when you are signed in. From this page, delete that key and align.telemetry.sent-journal, and the align-telemetry and align-telemetry-sent databases the same developer tools show under IndexedDB, which hold any log not yet sent and the copy of what was sent; Align then files the log under a new id from the next time it opens.
While Help improve Align is on, a second database in this browser, align-telemetry-sent, keeps a copy of each row this browser sent or tried to send, exactly as it went and with the time it went: the newest 3,000, none older than 30 days. Only the See my usage log panel under Privacy choices reads it, in this browser, and nothing sends it anywhere. Turning Help improve Align off deletes it with the queue. Rows sent as a page closes are noted first in this browser's local storage under align.telemetry.sent-journal, and move into that copy the next time Align writes to it. Turning Help improve Align off deletes this note too.
Buying Pro
When you buy Pro, a one-time payment, you type an email address for the payment, in a box that starts empty. Align sends WiPay the email you type for the payment, and nothing else about you: not your name, your username or your Align account. With it go our order id, the price in US dollars, the page to come back to, and NETLCO's own WiPay account details. When you buy Pro, Buy asks which country you live in, so we can check that we sell Pro there and whether you can cancel. We check it when you press Buy against the country your connection comes from, and keep neither: they are not saved with your order or in any log. Only whether Brazil's, Israel's or Uruguay's law gives you a right to cancel, and which, is kept with your order, and, for those three, whether the two countries matched. When you open Buy or Your account, and when you press Buy, Align also reads the country and region Cloudflare adds to the request. It uses them to fill in the country you live in, which you can change before you pay, to check that the request does not come from a place under sanctions, and to see whether a country's right to cancel applies to you. It keeps none of it, except that, for a purchase where you picked Brazil, Israel or Uruguay, your order notes whether your connection came from that country. Nothing else from it is saved with your order or in any log. When WiPay confirms your payment, Align emails a receipt to your account's email, if it has one, and never to the email you typed for the payment. The receipt gives the date, our order id, WiPay's id for the payment, what you bought and its price, and NETLCO's details.
We count, in totals for each 10 minutes, how often Buy Pro is shown, a buyer presses Pay, a press is refused and why, the country picked differs from the one the connection comes from, and a buyer is sent on to WiPay's page, so we can see where buying stops. The totals name no account, address, email or country, and are deleted after 90 days.
From each sale we keep a number for the sale; a random order id we give it, which WiPay also holds; the account it was for; the plan; the price paid and its currency, US dollars; whether it was a real payment or one of our tests; which version of Align a once licence covers; WiPay's id for the payment; whether it is paid, still open, or replaced by a later try; the end of Pro its payment set, or would have set, which is for good for a once licence; whether it gave Pro, or nothing, as the account already had Pro for good or was turned off or removed, or the payment was taken back before Align confirmed it; when the checkout started, when it was paid, and when a refund, a chargeback or a fraud check took the payment back, or, if WiPay's notice of it came before Align confirmed the payment, when Align confirmed it; when you ticked at Buy that Pro starts as soon as you pay and that you then lose the right to cancel and the language that sentence was shown in; whether Brazil's, Israel's or Uruguay's law gives you a right to cancel it, and which; for a purchase where you picked Brazil, Israel or Uruguay, whether your connection came from that country; when you cancelled it, if you did; when one of our admins cleared a payment WiPay never confirmed, after checking it with WiPay and which admin cleared it; when one of our admins recorded it paid, after WiPay's merchant page showed the payment and no notice of it reached Align and which admin recorded it; when Align emailed us that a payment was still not confirmed; WiPay's reason, in its own words, when it refused a checkout, with any email address taken out; when its receipt email was sent and when Align last began sending it; the tax year its payment counts in. From each of WiPay's notices about a sale we keep WiPay's id for the notice; what WiPay says happened, a payment, a refund, a chargeback or a fraud check; the order and WiPay's payment it is about; the amount and currency WiPay names; when it arrived, and the tax year it counts in. We never keep your card, your name, your address, a phone number, or the email you typed for the payment.
We keep them to give you Pro and prove it was paid for, to answer a question about a payment, a refund or a chargeback, and for NETLCO's tax records. We keep the record of each sale, with WiPay's notices about it, for six and a half to seven and a half years after its payment, or after the last refund, chargeback or other notice WiPay sends about it, whichever is latest, as the tax law asks. We keep it longer only if a tax return is filed more than three years after its year ends, or if the Board of Inland Revenue asks in writing. A cleanup we run then deletes it. A checkout never paid, a test of ours, and a notice about neither are not tax records: the same cleanup deletes each 90 days after it was made, unless the Board of Inland Revenue has asked in writing to keep it. A real checkout WiPay started but never confirmed as paid or declined is kept, with WiPay's notices about it, until WiPay confirms it or one of our admins clears it after checking with WiPay, so that a payment that may have been taken is never forgotten. After that it is kept as a sale or as a checkout never paid, as above.
If your account is removed after you buy Pro, we remove the account and keep only the record of each sale, for the period above; that record then names no account.
The phone remote
Tools, Phone remote pairs your phone with Align on this computer, so you can press Reset average and Capture, start or stop the generator, and play and choose your songs, from where the mic stands, and see Align's Real-time magnitude graph, its live spectrograph and its RTA there. While a phone is paired, and only then, its presses, this computer's short replies, such as what was kept, whether the generator plays, whether the measured input or the reference has no signal, and what the song player is doing, and the live trace and its coherence, a few times a second, pass between the two through Align's server, which Cloudflare carries like every request to Align, and through Align's database, which hands each one back to the server to pass on. With them go the other lines Align's Real-time magnitude graph draws, whichever screen this computer shows, such as a saved trace, an average, the target or the EQ's lines, with the names the graph gives them and how it draws them, so the phone draws that graph as this computer would, and, while the phone shows the spectrograph, its newest rows, and while it shows the RTA, the RTA's live line: each the level at each frequency of the measured input, a few times a second. The names of the songs in the player's list go too, as this computer shows them. Each is passed on as it arrives. Neither our server nor the phone's page writes any of it down, and neither they nor the database keeps any of it. The sound never leaves this computer. The code you scan signs the phone in for that pairing only. Closing the remote ends the pairing: the code then signs no phone in, and within a minute our server takes nothing more from the phone for the remote; anything the phone sends in that minute goes no further than our server and its database, and is not kept.
Who it passes through
What Align collects passes through the companies below. NETLCO shares none of it for advertising, except what Microsoft Clarity sends its maker once you allow it, as its part below says. Align shows no adverts.
Microsoft Azure
Align runs on Microsoft Azure, which keeps its database in Microsoft's East US 2 region in the United States: the accounts, the codes you ask for, the browsers that keep Align offline and the admin page's records, the record of each sign-up attempt and any bars, the messages from Help, the sales, the test reports and the usage log. The phone remote's presses, replies, live trace, the other lines Align's Real-time magnitude graph draws, with their names and how it draws them, the spectrograph's rows, the RTA's live line and the names of your songs pass through Align's server on Azure and through that database, and are not kept there. Azure also keeps backups of that database in the same region for up to 35 days, so anything we delete from it, even at your request, can be brought back from them for that long.
So that what we delete can be deleted again if the database is ever put back from those backups, we keep a note in our own records each time we delete a message from Help or take its email and account name off, delete a test report, remove an account, or delete a browser's part of the usage log other than by the daily cleanup. A note holds when it was made and the message's id, the report's id, the account's number or, for the usage log, a fingerprint of the browser's id that matches that id but cannot be turned back into it, never a name, an address or anything you wrote. Each note is kept for 91 days after its delete was last made, then deleted by a cleanup we run once a day, and the backups we make of those records keep it for about six months more before we delete them.
When something goes wrong, Align's server notes the failure in its own log, which our hosting at Microsoft Azure keeps for 31 days.
Cloudflare
Cloudflare carries every request to Align, to protect it and to speed it up, so it sees your IP address and what your browser asks for. On every Align page a browser loads, it also:
- checks for bots with a script that reads what Cloudflare calls "client-side signals" in your browser and sends them to Cloudflare, which keeps the result in the cf_clearance cookie above, a cookie Cloudflare's own page calls strictly necessary and says "stores the proof of challenge passed";
- asks Chrome, Edge and similar browsers to tell it when a request to Align fails, for a week after a visit: the address asked for, the page that led there, the error and its timing, and your browser's user agent.
Cloudflare's privacy policyCloudflare's cookies
Our email provider
An email you send to either of our addresses goes through it and stays in our mail until we delete it. A reply to it, or to a message from Help, and any answer you send to that reply, go through the provider of the mailbox the reply is sent from and stay in that mailbox until they are deleted. Align's server sends its emails through Cloudflare's Email Service, from codes@align.netlco.com; Cloudflare keeps a record of each one's sender, recipient, subject, delivery and time for 31 days. If Cloudflare cannot send one of them, Align's server sends that email through Microsoft 365, our email provider, from align@netlco.com, and keeps no copy in Align's mailbox; Microsoft keeps a record of its sender, recipient, subject and time for 90 days. An email to an address at netlco.com, NETLCO's own, goes the other way round: Align's server sends it through Microsoft 365 first, and through Cloudflare's Email Service only if Microsoft 365 cannot send it. NETLCO's own mailbox gets a hidden copy (Bcc) of every email Align's server sends, and keeps it in NETLCO's records until we delete it. A code in that copy works only in the browser that asked for it, and only for 15 minutes. When NETLCO, or the system engineer Align is built for, writes to you from align@netlco.com, that email names NETLCO's mailbox in its Cc.
Anthropic
NETLCO's team works with Claude, Anthropic's AI assistant. When we read or answer a message from Help or an email you send us, read a test report, make an account, study the usage log or read our copy of an email Align sends you, what we read passes through Anthropic.
Once you allow it under Help improve Align, Google Analytics loads on Align's public pages from www.googletagmanager.com and sends what it counts to *.google-analytics.com and *.google.com, which are Google's. What it receives, its cookies and how long Google keeps it are under Help improve Align above.
Microsoft Clarity
Once you allow it under Help improve Align, outside the places where you choose two things separately, Microsoft Clarity loads on Align's public pages from *.clarity.ms and sends what it records there and to c.bing.com, which are Microsoft's. Microsoft keeps it as its own controller, under the Microsoft Privacy Statement, and may use it for its own purposes, advertising among them.
WiPay
WiPay takes the payment for Pro. It receives the email you type and our order, as Buying Pro above says, and takes your card, your name and your billing address on its own page, under its own privacy policy. When you come back, WiPay's link back to Align carries your name, email, billing address, phone and the last digits of your card. Align reads only the payment's result and amount, WiPay's id, proof and note for it, and the order number from it, and keeps none of the rest; Cloudflare, which carries every visit to Align, may record the link as it does any page's address.
Other sites, and Do Not Track
Align itself follows nobody across other sites. Once you allow it, Microsoft Clarity sends its maker what its part above says, and that company may link it with what it holds from other sites under its own policy; turning the tick off stops Align sending more. A browser's Do Not Track setting changes nothing here; the ticks are what decide. Cloudflare runs a script on every Align page and sets a cookie of its own; by its own privacy policy, linked above, it processes visitors' IP addresses and traffic data across the many sites it carries, Align among them, for the purposes that policy lists, and may aggregate that data into web traffic reports and statistics.
Seeing, correcting or deleting it
Ask to see what we hold about you, to have it corrected or deleted, or for a copy of it, by email or from Help, Send feedback. We answer within 45 days. If we refuse, reply to say so: we look at it again and tell you the outcome, and why, in writing.
Asking us to free a browser's seat signs it out at its next check-in online, or when its pass ends if it stays offline; its record stays with your account until the account is removed.
NETLCO sells nobody's information; the address below is also where to tell us never to. You can clear Align's cookies and site data in your browser at any time, which signs you out.
Changes
Every change is posted here, in the release of Align that makes it, and moves the date at the top of this page.
- 17 November 2026: Align now has a Contact page where anyone can send us a message, signed in or not, and the page says what Align keeps from it.
- 17 November 2026: Emails Align sends to an address at netlco.com, NETLCO's own, now go through Microsoft 365 first, with Cloudflare's Email Service as the backup, and the page says so.
- 16 November 2026: While your cancel days are open, the records of your browsers now hold you to 3 days offline at a time, not 30.
- 16 November 2026: Your account now also keeps the language its emails are written in when no page of yours sends them, taken from the language you last agreed to the terms in.
- 15 November 2026: The page now says that Buy fills in the country you live in from your connection, which you can change, and that we count where buying stops, in totals that name no account, address, email or country and are deleted after 90 days.
- 14 November 2026: We now also note when you tick at Buy that Pro starts at once, and in which language; whether Brazil's, Israel's or Uruguay's law gives you a right to cancel, and, where you picked one of those countries, whether your connection came from it; and when you cancel a purchase.
- 14 November 2026: The record of your agreement now also keeps the language the words were shown in.
- 14 November 2026: Google's cookies are now set on Align's address alone, under their own names, align_ga and align_ga_NBRRP3LWHW.
- 14 November 2026: The page now says that Align notes each sign-in, how it was made and when, and deletes that note after 90 days.
- 14 November 2026: You can now make a Free account yourself, or sign in, with Google, Microsoft or GitHub. The page now says what each tells Align, what Align keeps, and what each learns.
- 14 November 2026: Align's emails now go through Cloudflare's Email Service first, with Microsoft 365 as the backup, and the page says so.
- 14 November 2026: On 13 November 2026, from 9:53 PM to 12:14 AM on 14 November, Trinidad time (UTC-4), when someone who had allowed Help improve Align moved from a public page to another Align page without reloading, Microsoft Clarity also received that page's address and title, with the browser details its part names, but never its words, clicks or layout. That is fixed.
- 13 November 2026: The page now says that when you press Buy, Align also reads the country and region Cloudflare adds to the request, to check that it does not come from a place under sanctions, and keeps none of it.
- 13 November 2026: The page now says more exactly what Align keeps and why: that WiPay's link back to Align carries your details and Align keeps none of them, the email sent if someone tries to sign up with your address, every limit that reads your IP address, every kind of code, what a bar records and covers, which sign-up attempts are written down, what the admin page shows, the server's 31-day log of failures, and that the usage log also feeds the admin page's counts. Align now asks before it keeps a usage log or lets Meta's pixel run: both stay off until you allow them. The page now says that visitors in the European Economic Area, the United Kingdom, Gibraltar, Jersey, Guernsey, the Isle of Man, Brazil and wherever we cannot tell your country choose the usage log and Meta's pixel separately, where those answers are kept, that Align reads the country Cloudflare adds to each request to show you that choice, and the clicks, errors and microphone answers the usage log now counts.
- 13 November 2026: If Microsoft 365 cannot send one of Align's emails, Cloudflare's Email Service now sends it instead, and the page says what Cloudflare keeps.
- 12 November 2026: The page now says what happens when you make an account: the code we email, the checks on your email address and password, Cloudflare's human check, the record we keep of each sign-up attempt and of any bar, and how long we keep each.
- 12 November 2026: The Tester switch: an Align admin can show a Pro account the tools still being tested.
- 12 November 2026: Align now keeps a record when you agree to our terms: your account, the date and time, the version of the terms, the screen where you agreed and the words that screen showed. When you agree on the free tools without an account, the record stays in your own browser and is not sent to us.
- 12 November 2026: The page now says that Buy asks which country you live in, to check that we sell Pro there, and does not keep it.
- 10 November 2026: A sale now also keeps when one of our admins recorded it paid, after WiPay showed the payment and no notice of it reached Align, and which admin.
- 10 November 2026: When you check in, Align now keeps the country of your address for 90 days, to spot an account used in two places at once. Align's server also keeps a record for a year of each sign of tampering it sees; a copied browser is signed out at once, and a person at NETLCO reads the record before anything happens to the account.
- 9 November 2026: Buying Pro now sends a receipt to your account's email. We now keep a checkout WiPay never confirmed until it is settled, and WiPay's reason when it refuses one.
- 8 November 2026: Align's admin page now also shows, for each account, when each of its browsers was added and when its offline pass ends, how many swaps it has used, and whether it is measuring now, and since when.
- 7 November 2026: An Align admin can now send your account a copy of their own view settings; it waits on our server only until your browser next opens Align.
- 7 November 2026: Buying Pro: what you give at checkout, what WiPay receives, what we keep from each sale, and the end of any Pro we gave your account ourselves.
- 7 November 2026: The phone remote can now show the computer's RTA: while a phone is paired and shows it, the RTA's live line, the level at each frequency of the measured input, passes between the two through Align's server and its database, and none of it is kept. The page's part on the phone remote, its part on what stays in your browser and its sentence on Azure now say so.
- 6 November 2026: The phone remote can now show the computer's live spectrograph and play your songs: while a phone is paired, the spectrograph's newest rows, while the phone shows it, and the song player's state, with the names of the songs in its list, pass between the two through Align's server and its database, and none of it is kept. The page's part on the phone remote, its part on what stays in your browser and its sentence on Azure now say so.
- 26 October 2026: The phone remote now shows the computer's Real-time magnitude graph: while a phone is paired, the lines that graph draws, with their names and how the graph draws them, pass between the two through Align's server and its database, and none of it is kept. The phone is no longer sent the next position. The page's part on the phone remote, its part on what stays in your browser and its sentence on Azure now say so.
- 25 October 2026: The phone remote is new. While a phone is paired with it, the phone's presses, the computer's replies, and the live trace and its coherence pass between the two through Align's server and its database; none of it is kept, and the sound never leaves the computer. The page's part on what stays in your browser now names the phone remote as an exception. Two lines of the list of cookies now name the phone remote's page among the pages that do not set them.
- 24 October 2026: The page now says that an email the system engineer Align is built for writes from align@netlco.com also names NETLCO's mailbox in its Cc.
- 24 October 2026: The copy NETLCO's mailbox gets of each email Align's server sends is now hidden (Bcc), where it was named in the email's Cc; each such email still says so at its foot.
- 24 October 2026: You can now sign in with your account's email address in place of your sign-in name.
- 23 October 2026: Your account can now have an email address. The page now says what Align sends to it, through Microsoft 365, the record each code you ask for leaves and how long it is kept, the cookie that lets only your browser use a code, and that NETLCO's own mailbox gets a copy of every email Align sends.
- 23 October 2026: The page now says that Prices, Training and the tool pages set neither sign-in cookie and send no usage log.
- 23 October 2026: The page now says what Align's server keeps for a browser that keeps Align offline, what that browser keeps in its own storage and what its pass holds. It also says that you ask for an account at align@netlco.com, and that NETLCO and the system engineer Align is built for see accounts on Align's admin page, which records each change made there for a year.
- 21 October 2026: The page now says that Align keeps whether your account has Pro, and until when.
- 19 October 2026: Align now measures in one place at a time on each account: while it measures, the page asks Align's server every 2 minutes whether the account's turn is still its own, and the server keeps one record of the turn. Align also reads your IP address to limit how often one address can ask, and still never writes it down.
- 19 October 2026: Align now has Help, Test Align, a numbered test plan whose report you can send us. Nothing of a run is sent until you press Send after a preview of every field, and this browser's usage-log id and the four-mic hour's delays go with it only if you tick a box for each.
- 18 October 2026: The sign-in cookie now lasts up to 30 days after your last signed-in visit online for the sign-in that turns Offline on; any other sign-in stops signing you in after 14 days without one. Align now also reads your IP address to limit how often one address can check in, trade a sign-in code or ask for one, to keep Align offline, and still never writes it down.
- 15 October 2026: The page now says that Align's two sign-in cookies are set only while its sign-in is on, and that the cookie that keeps you signed in runs from your last signed-in visit. It also says that the script Cloudflare's bot check runs on every Align page sends what it reads in your browser to Cloudflare. The script did so before too; the page had not said it.
- 14 October 2026: Align now also keeps whether you have chosen your account's password yourself, and when. When you sign in with a password NETLCO gives you, Align now asks you to choose your own before anything else opens, and once you have chosen it, the one NETLCO gave you no longer opens the account. Deleting the usage log's key no longer needs every other tab and window that has shown Align closed first: a page still open stops sending the log once the key is deleted, and Align files the log under a new id from the next time it opens.
- 12 October 2026: first posted.