What personal and tax information Aeday collects, how it is used, and the choices you have.
Effective
1. Information we collect
Information you provide directly We may collect name, email address, phone number, mailing address, account credentials, eligibility questionnaire responses, employment or income-category information, tax-year and filing-status information, information about whether you have an existing or prior tax matter, communications, support requests, cancellation requests, and other information you choose to provide.
Your email address in the sign-up The questions page of the sign-up ends by asking where to send your savings estimate. When you press to see your savings, we save the email address you give there on our server with your sign-up, before you see your plan and its price, and we use it to fill in the email box on the payment page. We also keep that address as our record of a person who has given us an email address and has not paid, which is the record the sign-up page where you pay uses too. Under the email address, the questions page also asks for your phone number, which you may leave blank. If you give one, we save it with your sign-up when you press to see your savings, replace it if you give another, and, if you join, use it to fill in the phone number box on the setup page; it is saved to your account only when you continue from that page. On the sign-up page where you pay, we save the email address you type into the email box on our server as soon as it looks like a complete email address, before you press to pay, and we replace it when you change it to another complete address, so we keep one address at a time. We keep it with your sign-up whether or not you go on to pay. Section 2 says what we send to it, and section 5 says what we report to Meta.
Information about your spouse If you add spouse coverage to your membership, we collect the name and phone number you give us for your spouse, and use them to administer that coverage.
Tax and representation information If you submit a tax notice or Request for Representation, we may collect highly sensitive information contained in tax records, including IRS or state tax notices, tax-account information, taxpayer identification information, portions of tax returns, income information, agency transcripts, identity-verification information, correspondence, and documents reasonably necessary to evaluate or perform representation.
Please submit tax documents only through the secure methods Aeday designates.
Payment information Payments are processed by third-party payment processors. Aeday may receive payment status, card brand, last four digits, billing ZIP code, transaction identifiers, renewal dates, and fraud/risk information.
Device, website, and usage information We may collect IP address, device identifiers, browser type, operating system, referring pages, pages viewed, timestamps, approximate location derived from IP address, cookie identifiers, advertising identifiers, campaign attribution information, and website interaction data.
Sign-up step counts Aeday itself counts, on its own server, how many visits reach each step of the sign-up and whether a visit came from a Meta ad, a Google ad or elsewhere. Each count is a step, where the visit came from, and the time, and, on the coverage page, the kind of device and browser app (for example, Instagram on an Android phone), which question you opened and, for a refused payment, the kind of error, with no identifier: nothing in it names you or your browser. It goes to no one outside Aeday, and it continues when advertising measurement is turned off.
Advertising click identifiers If you arrive from a Google or YouTube ad, we collect the ad click identifier Google adds to the link (called gclid, gbraid, or wbraid) and keep it with your sign-up. If you arrive from a Meta ad on Facebook or Instagram, we collect the ad click identifier Meta adds to the link (called fbclid) and keep it the same way.
Advertising browser identifier Meta’s pixel stores a random identifier for your browser in a cookie called _fbp on our sign-up pages. When you press to see your savings at the end of the sign-up questions, when you leave the email box on the payment page holding an email address you typed there or gave on the questions page, when you start to enter a payment with such an address in that box, when you leave or switch away from that page holding an email address you typed there, when the coverage page is first shown to you, when you first reach its payment form, when you complete the card details there, and when you press to pay, our server reads that identifier from your browser, if it is there, and keeps it with your sign-up. We never create one ourselves.
Your name and phone number on the setup page After you join, the setup page asks for your name and phone number so that a practitioner knows who they are working for when you submit a case. We also use them to measure our advertising: the report of your purchase to Meta carries scrambled codes made from them, as section 5 describes, where your choice to turn advertising measurement off is also explained.
5. Sale, sharing, and targeted advertising
Aeday does not sell personal information for money.
We may use third-party advertising or analytics technologies that receive limited cookie, device, or browsing information. Under some state privacy laws, certain disclosures for targeted advertising may be considered a "sale," "sharing," or "targeted advertising."
Where applicable, you may opt out through the privacy-choice mechanism provided on the Site or by contacting privacy@aeday.com.
Aeday does not sell sensitive tax-document information.
Google ad measurement. We use the Google tag, provided by Google LLC, to measure whether our ads on Google and YouTube lead to visits and enrollments. It loads on five pages of my.aeday.com: the four sign-up pages — the questions, the plan and payment page, its plan terms page, and the coverage page, where you choose a plan and pay without the questions — and the setup page you land on after you join. It loads when one of those pages opens, whether or not you arrived from an ad. It does not load anywhere else on my.aeday.com — not on your dashboard, not on your billing page, not where you send us a tax notice, and not where you sign a tax authorization — and it does not load on aeday.com.
The Your Privacy Choices page on aeday.com is where you turn advertising measurement off, and your choice is kept by your browser for aeday.com. It reaches those five pages of my.aeday.com by travelling with you when you follow a link from aeday.com into the sign-up, and is then remembered there. If you reach a sign-up page without passing through aeday.com at all — by typing its address, or by following one of our ads or any other link that points straight at it — your choice cannot travel, and the tag loads on that page until you have been through aeday.com once and turned advertising measurement off there.
When you arrive from a Google or YouTube ad, the ad click identifier is carried into the sign-up on my.aeday.com in the address of the link you follow, and we keep it with your sign-up. If you become a member, the purchase is reported to Google in two ways: from your own browser, by the Google tag on the setup page you land on after you join, and from our server.
The report from your browser carries the amount you paid for the membership, the currency, the address of that page without anything after the question mark, and a reference for your membership, which is what lets Google count one purchase however many times that page is opened. It carries nothing that identifies you. The report from our server carries the ad click identifier, the time, the same amount, and a scrambled code made from your email address instead of the address itself, which helps Google recognize the purchase as yours. The code is a SHA-256 hash, which is not the address and cannot be read back as one, though someone who already knows an address can produce the same code from it. Neither report carries your name, phone number, answers, or any tax information. We delete the code as soon as Google has answered, and in every case at the same time as the ad click identifier, which section 7 covers.
The Google tag itself does something further, which is not part of either report. It may collect an email address, and any name or phone number, that you type into a form on the pages it loads on, and send each to Google as a scrambled code made from what you typed instead of the value itself, so that Google can recognize a sign-up or a purchase as coming from someone who saw or clicked one of our ads. We have seen it do this with the email address typed on the payment page, and it may do the same with the email address you give on the questions page. The code is a SHA-256 hash, which is not the address and cannot be read back as one, though someone who already knows an address can produce the same code from it. Whether the tag does this is controlled by a setting in our Google Ads account, not by anything on the page, and that setting is on. It does not read your answers, your card details, or any tax information.
Meta ad measurement. We use the Meta pixel, provided by Meta Platforms, Inc., to measure whether our ads on Facebook and Instagram lead to visits and enrollments. It loads on the same five pages of my.aeday.com: the four sign-up pages, where you answer the questions, choose a plan and pay, and the setup page you land on after you join. It loads when one of those pages opens, whether or not you arrived from an ad. It does not load anywhere else on my.aeday.com — not on your dashboard, not on your billing page, not where you send us a tax notice, and not where you sign a tax authorization — and it does not load on aeday.com. How your choice to turn advertising measurement off reaches those five pages, and when it cannot, is in the next paragraph.
The pixel records that a page was viewed and, on the sign-up pages, which steps you reach: that you started the questions, which of the questions you answered, that you typed a complete email address, on the questions page or the payment page, that you saw the plan, that you switched between monthly and yearly billing, that you pressed the button that scrolls down to the payment form, that you started to enter a payment, and which boxes of the payment form you completed (the name on the card, the card number, the expiry date, the security code and the ZIP code), never what you typed into them. With each of those it records the address of the page, which can include the ad click identifier you arrived with, from a Google or YouTube ad as well as from a Meta ad; Meta keeps what the pixel records under its own terms. We give it no name, email address, phone number or answer, and we switch off the setting that would let it read what you have typed into a form. On the coverage page it also records that you saw the page; which of our two plans and which billing period you chose, as a product code such as aeday_standard_monthly with that plan’s price, never the words you chose it by; that you pressed the button that takes you to the payment form, or reached that form; how far down the page you scrolled; how long the page was open; which of its questions you opened; that you started to enter a payment and completed the card details; that you pressed to pay; and, if a payment is refused, the kind of error. Where our server also reports one of those steps, the pixel’s report carries the same reference for your sign-up, so that Meta counts the two as one. After you join from the coverage page, the pixel on the setup page also reports your purchase, with the amount, the product code and the same reference for your membership as our server’s report of it, so that Meta counts the two as one. When you first see your plan after the questions (and again, with the same reference, if your sign-up is restarted for you soon after), the pixel also reports that you qualified, as Meta’s standard Lead event, with the same reference for your sign-up as our server’s report of that step, so that Meta counts the two as one, and with the same plan and estimated yearly savings, which are worked out from your answers. Your choice on the Your Privacy Choices page on aeday.com reaches the pixel the same way it reaches the Google tag: it travels with you when you follow a link from aeday.com into the sign-up, and is then remembered there. If you reach a sign-up page without passing through aeday.com at all — by typing its address, or by following one of our ads or any other link that points straight at it — your choice cannot travel, and the pixel loads on that page until you have been through aeday.com once and turned advertising measurement off there.
A sign-up that starts on the coverage page has no questions, so nothing reports that you qualify. Instead our server reports when the coverage page is first shown to you, when you first reach its payment form, and when you complete the card details there, beside the payment step and the purchase described below, each once. Each of these three, and the payment step of such a sign-up, carries the product code of the plan and billing period you had chosen and that plan’s price in US dollars. Our server reports three steps of every sign-up to Meta, each once, whether or not you arrived from an ad: when the questions decide that you qualify, when you reach the payment step, and, if you become a member, when your first payment is taken. The questions end by asking for your email address, so the first of these is reported after you press to see your savings. You reach the payment step, for this report, the first time one of these happens while the email box on the payment page holds a complete email address: you leave the box, holding an address you typed there or gave on the questions page; you start to enter a payment, with such an address in the box; or you leave or switch away from that page, holding an address you typed there. Otherwise it is when you press to pay. It is reported whether or not you go on to pay. Each report carries the time and the address of the page on my.aeday.com where the step happened. The report that you qualify also carries the plan we matched you to and your estimated yearly savings in dollars, the figure the plan page showed you when you qualified; the payment step carries no amount at all; and the purchase carries the amount you paid for the membership and the currency. When you arrive from a Meta ad, the ad click identifier is carried into the sign-up on my.aeday.com in the address of the link you follow, we keep it with your sign-up, and each report carries it too. Each report also carries a reference for your sign-up (for the purchase, a reference for your membership), a random identifier we create, not your name or email address, which is what lets Meta count each step once however many times it is sent.
Those reports also carry things that help Meta recognize the steps as yours: the IP address and the browser description recorded when you started the sign-up (for the purchase, the sign-up you paid from); the browser identifier Meta’s pixel keeps in the _fbp cookie, which we keep with your sign-up until your purchase is reported, or, for a sign-up that does not end in a purchase, until the time section 7 states has passed; a scrambled code made from an identifier of your sign-up; and, on each report made once you have given an email address, a scrambled code made from it instead of the address itself. The code is a SHA-256 hash, which is not the address and cannot be read back as one, though someone who already knows an address can produce the same code from it. On the report that you qualify, the code is made from the email address you gave on the questions page, and, if you gave a phone number there, that report also carries a scrambled code made the same way from it. On the payment step, the code is made from the email address we saved from the email box when that report was made, or, where it was made when you pressed to pay, from the address you paid with; a change you make to the box after that is saved but not reported. On the coverage page’s reports, the code is made from the email address we saved from the email box, where there is one. The purchase also carries scrambled codes made the same way from your first name, your last name and your phone number, which we read when the purchase is reported and keep nowhere else for this. So we hold the report of your purchase until we have your name and phone number, which the setup page asks for, but no later than the first once-a-day run that comes at least 2 hours after your first payment is taken; a purchase reported before we have them is reported without them. We do not send your answers, your country, or any tax information. The plan and the estimated savings on the report that you qualify are worked out on our server from your answers; the answers themselves are not sent. We delete the copy of the browser identifier and the codes that each report carried as soon as Meta has confirmed receiving that report or has told us it took nothing from it, and everything we keep for these reports within the time section 7 states.
You can turn both off on the Your Privacy Choices page on aeday.com. Your choice is kept in your browser’s local storage, not in a cookie, so it applies to that browser, and it reaches the five pages of my.aeday.com in the way described above. Once it has, your browser tells our server when you press to see your savings at the end of the questions, when you leave the email box on the payment page holding an email address you typed there or gave on the questions page, when you start to enter a payment with such an address in that box, when you leave or switch away from that page holding an email address you typed there, when you press to pay and when you save your details on the setup page, and from then on our server sends Meta none of the reports above for your sign-up and keeps no Meta ad click identifier, browser identifier or scrambled code for those reports; a report already sent, or already on its way, when your browser told our server cannot be taken back. That part of your choice reaches our server’s reports to Meta only. For Google, your choice keeps the Google tag, and the report of your purchase from your browser, off those pages; it does not stop our server from keeping a Google or YouTube ad click identifier that arrives in the address of a sign-up page, or from reporting your purchase to Google from our server as described above. Your choice does not stop the email with a copy of your savings estimate that section 2 describes, which is not advertising measurement. Aeday does not act on Global Privacy Control or any other browser-based opt-out preference signal; that page, or an email to us, is how to opt out.
Session recordings. We use Microsoft Clarity, provided by Microsoft Corporation, to see how people use our pages so that we can fix what gets in their way. It loads on every page of aeday.com and on the same five pages of my.aeday.com as the pixel and the tag: the four sign-up pages and the setup page you land on after you join. It does not load anywhere else on my.aeday.com — not on your dashboard, not on your billing page, not where you send us a tax notice, and not where you sign a tax authorization.
Clarity records how you use those pages: where you click and tap, how far you scroll, which pages you open and in what order, what each page shows while you are on it, and the address of each page and of the links on it, which can include the ad click identifier when you arrive from an ad. It does not record what you type into a form: Clarity hides every text box, and we also hide your email address, your name and phone number, the codes we send you, the payment section, the answer choices on the sign-up questions and the plan choices on the coverage page. Hidden text appears in a recording as blocks, though the recording still shows where on the page you tapped. Clarity cannot see inside the card fields, which are Stripe’s. It is told which steps of the sign-up you reach, by the same names the pixel uses, and which of our plans you were shown or chose. We do not give it your name, your email address, or any account identifier.
Clarity sets two cookies of its own for aeday.com as a whole, so they are also sent to my.aeday.com, and Microsoft may set its own cookies on clarity.ms; the Cookie Policy names them. Microsoft receives what Clarity records. Under its own terms for Clarity, Microsoft may use that information as the Microsoft Privacy Statement describes, including to improve its products and to build profiles used for advertising; the statement is at https://privacy.microsoft.com/en-us/privacystatement. Aeday has not linked Clarity to Microsoft Advertising and does not use Clarity to advertise, and our pages do not let Clarity’s script contact Microsoft’s advertising address, bing.com.
The switch on the Your Privacy Choices page on aeday.com turns Clarity off too. On aeday.com it stops Clarity on the page where you press it and on every page after. On the five pages of my.aeday.com your choice reaches Clarity the same way it reaches the pixel and the tag, with the same limit when you open a sign-up page without passing through aeday.com.
7. Data retention
We retain personal information only for as long as reasonably necessary to maintain your membership and account, perform representation, comply with legal and professional obligations, prevent fraud, resolve disputes, and enforce agreements.
When information is no longer reasonably necessary, we may delete, de-identify, or securely archive it as permitted by law.
We keep the email address you give on the questions page, or type into the email box on the payment page, as section 1 describes, with your sign-up, whether or not you went on to pay. We have set no period after which we delete it; until we set one, we keep it. We use it only to fill it back into the sign-up’s email boxes for you, to send the copies of your savings estimate that section 2 describes, to make the scrambled codes that section 5 says we send on the report that you qualify and on the payment step, and, for the address you give on the questions page, to keep the record of a person who has given us an email address and has not paid that section 1 describes. The next paragraph’s limit does not apply to it. We keep the phone number you give on the questions page the same way, with your sign-up and with no period set, and use it only to fill in the setup page’s phone number box for you and to make the scrambled code that section 5 says we send on the report that you qualify.
We delete an ad click identifier, and the browser identifier, scrambled codes and copy of your plan and estimated savings that we keep for advertising measurement, no more than 90 days after we collect them. That limit does not reach what the Meta pixel and Microsoft Clarity record, which can include an ad click identifier in the address of a page, and for Clarity in the address of a link: Meta keeps what its pixel records under its own terms; Microsoft keeps what Clarity records as it keeps Clarity’s recordings, and uses it as section 5 says.
We also keep the record of each savings estimate we send, with a scrambled code made from the address it went to, and the record of each unsubscribe and each re-subscription, with a scrambled code made from that address, so that we can honor your most recent choice and the limits section 2 describes. We have set no period after which we delete these records; until we set one, we keep them. The limit above does not apply to them.
