Matano IT Solutions is the registered trading name of Matano Enterprises LLC, a New Jersey limited liability company. This policy covers matanoit.com, the services we provide to our clients, the free website and email check at /check/, and the assessments we send to businesses we have not worked with before. Questions about anything here go to hello@matanoit.com.
Text messaging privacy
Mobile information will not be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties.
All other categories of information may be shared with the service providers described below, strictly so we can operate the business.
If you give us your mobile number and agree to be texted, we use it to reply to you, to update you on support requests, and to confirm appointments and service windows. That is all. We do not add you to a marketing list, we do not rent or sell the number, and we do not pass it to anyone else for their own use.
You can stop the messages at any time by replying STOP. Full details are in our SMS Terms.
Live chat
Most pages on this site carry a live chat button. It is provided by 3CX, the same platform that runs our phone system. It is not on this page, our Terms or our SMS Terms: as of 8 September 2026 those three carry no chat widget and no analytics tag. Most pages connect you to our sales queue; the emergency and client support pages connect you to our support queue instead, so an outage never lands with sales.
The chat widget is loaded from a 3CX server, which means 3CX can see that your browser requested it, including your IP address, whether or not you open the chat. It runs on most pages of this site, including the support and emergency pages, where it is the only third party code. It is not on this page, the Terms, the SMS Terms, the free check or the websites pages. Where it does run, it causes 3CX to store two things in your browser, both named in the table under Measurement, and what is stored in your browser below.
If you do start a chat, it may ask for your name, email address, and company before connecting you, so we know who we are talking to and can look up your setup. Whatever you type then goes to us through 3CX. Chat transcripts sit in our 3CX system so we can pick up where we left off. Whichever queue you reach, please do not send passwords, card details, or anything else sensitive through it.
The widget may store a small amount of data in your browser so that a conversation survives you moving between pages. It is not advertising, and it is not shared with anyone for advertising. A content blocker will stop the widget loading entirely, and nothing else on the site breaks if you do that.
Measurement, and what is stored in your browser
This section was rewritten on 8 September 2026, because it was wrong. It used to say that this page, our Terms and our SMS Terms were counted by nobody, "in our own records or anyone else’s". Every page here is in fact counted in aggregate, and the chat widget stores something in your browser on the pages that carry it. Both are described below, and every last thing this site stores is now listed by name. We would rather correct a promise in public than quietly let one stop being true.
Every page is counted, in aggregate, by Cloudflare Web Analytics. That is a page count and nothing more: which page was viewed, the country it was viewed from, the site that linked to it, and the kind of browser. It sets no cookie and stores nothing in your browser, and it holds nothing about you. There is no identifier, so one visit is never joined to another, and there is nothing in it we could trace back to a person even if somebody asked us to. It runs on this page too. A count of how many people read our privacy policy is not surveillance, and we would rather say so than claim a purity we do not have.
Google Analytics runs on the free check and on the service pages under /lp/, and nowhere else. Not the home page, not our about or 3CX pages, not this policy, and not the support or emergency pages. Those service pages, the campaign landing page at /lp/email-check/, and /check/ are where our advertising sends people, and knowing which of those pages actually leads to an inquiry is the whole reason it is there. It records which page you viewed, roughly where in the world you are, how you arrived, and, as plain counts with nothing attached, that a check finished or that an inquiry was sent.
There is no advertising pixel on this site. A Meta pixel ran on our marketing pages until 8 September 2026. It was removed that day, along with the cookie it set, and nothing replaced it.
There is no cookie banner, and that is deliberate rather than an oversight. A banner is what a site needs when it cannot tell you plainly what it stores. We can, so here is the whole of it, by name.
| Name | Where | What it is for | How long |
|---|---|---|---|
mit_attrOur cookie |
Any page you land on with a ref or utm parameter in the link, and the free check. Not our client support, emergency or legal pages, which do not carry the script that sets it. |
Remembers which campaign brought you, so that an inquiry weeks later is credited to it. It holds the campaign words from the link, the page you landed on, and the site that referred you. Nothing about you, nothing you typed. | 30 days from the visit that set it. It is not extended by coming back. |
_gaGoogle Analytics |
The free check and the service pages under /lp/, nowhere else. | Tells Google Analytics whether this browser has been here before, so a returning visit is not counted as a new person. | 400 days |
_ga_14RK5WKRY3Google Analytics |
The free check and the service pages under /lp/, nowhere else. | Holds the session state for our property: when this visit started and how many there have been. | 400 days |
lastExternalReferrerGoogle Analytics, local storage |
The free check and the service pages under /lp/, nowhere else. | Google’s own script records the site you arrived from, so the visit is attributed to it. | Until you clear site data |
lastExternalReferrerTimeGoogle Analytics, local storage |
The free check and the service pages under /lp/, nowhere else. | The time that goes with the entry above. | Until you clear site data |
callus.greeting_activated3CX live chat, local storage |
Pages carrying the chat button, which is not this page, the Terms or the SMS Terms. | Remembers that the chat greeting has already been shown, so it does not reappear on every page. | Until you clear site data |
__cf_bm3CX live chat, on 3cx.com |
Set by 3CX’s own server when the chat widget loads, on the same pages as the entry above. It belongs to their domain, not to this site. | 3CX’s filter for automated traffic to their servers. We neither set it nor read it. | About half an hour |
This page, our Terms and our SMS Terms put nothing in your browser at all. No cookie, no local storage, nothing to clear afterwards: the chat widget came off those three on 8 September 2026, and the rows above therefore describe every other page rather than these. Two things are still fetched from outside as you read them, and neither sets anything or carries an identifier: the Cloudflare counter described above, and one image from mailarrive.com, the verification badge of our own sister service, which means that server sees the request the way any image host does. That is the whole of it.
Our own records hold no count at all of a view of this page, our Terms or our SMS Terms. Every other page on this site is counted once, at our edge, with no cookie, no identifier and nothing that says it was you; these three are skipped even by that. What still counts them is the aggregate Cloudflare figure described above, which we cannot switch off for three pages and would not want to claim otherwise.
That is the complete list. If you find something in your browser from this site that is not on it, we have made a mistake and we would like to know: hello@matanoit.com. The build refuses to publish a page that stores a name this table does not carry, which is how we intend to keep it complete.
What none of them ever receives is anything you typed. Not your name, not your email address, and above all not your phone number. Google is given which page was viewed and two counts with no parameters on them; the campaign cookie holds words from a link and never leaves your browser except as the campaign name attached to a form you choose to submit.
This is not a courtesy. Our SMS Terms commit that mobile information is never shared with third parties for marketing, and we hold to that.
We have turned off the Google setting that would join your visit to Google’s cross site advertising profiles. This is measurement of our own pages, not a contribution to an advertising profile of you. We also build the address we send rather than passing on whatever is in your browser bar: only campaign tags survive that step, and anything else in a link is dropped before Google sees it.
You can avoid the analytics entirely, and we have made that genuinely easy:
- Turn on Global Privacy Control in your browser or extension. We check for it, and a browser that signals GPC gets no analytics at all. Nothing on the page breaks.
- Read the pages that have none. The home page, our about and 3CX pages, this policy, the Terms, the SMS Terms, and the support and emergency pages carry no analytics in the first place, and every one of them reaches us perfectly well. So does the phone number, which is on every page.
- Use any content blocker, or turn JavaScript off. Either one stops it, and the aggregate page count at the edge is all that remains.
We still do not sell your personal information, and running an ad does not change that.
What we collect
Information you give us
- Your name and email address, which are required to submit a form.
- Your company name, phone number, the services you check, and whatever you write in the message box. All optional.
- Whether you agreed to receive text messages, along with the date and the exact wording you agreed to. We keep that record so we can prove your consent was properly obtained if a mobile carrier asks.
Information we collect automatically
- The page you viewed, the campaign tag on the link you followed, the domain of the site that referred you, and the country and region (state or province) your request came from. Our network works both of those out from your connection and hands them to us already resolved; we never see or keep the address itself, and we do not record your city.
- Nothing else, in our own records. We do not store IP addresses. The free check and the service pages under /lp/ additionally carry Google Analytics, which is described under Measurement, and what is stored in your browser above and which does receive your IP address as any server your browser talks to does. This page does not carry it, and neither do the home page, the support and emergency pages, or the other legal pages.
Information stored in your browser
If you arrive from a link carrying a ref or utm parameter, we set one first party cookie, mit_attr, recording which campaign it was, so that a later inquiry can be credited correctly. It expires after 30 days, it never leaves your device except as the campaign name attached to a form you choose to submit, and clearing your browser data removes it. Every other thing stored in your browser by this site, ours or a vendor's, is listed by name under Measurement, and what is stored in your browser.
Client information
When we provide IT services, we necessarily encounter information inside your systems: user accounts, mailboxes, device details, network configuration, and the contents of support requests. We access it only to do the work you have asked us to do, we do not use it for any other purpose, and it stays yours. Where a written services agreement is in place, that agreement governs.
The free check at /check/
Anyone can type a domain into the checker on /check/ and see a summary for nothing. That half asks for no personal information at all and we do not know who you are. This section covers what happens if you go on to ask for the full report.
This page carries Google Analytics, because it is a page people reach from our ads. What Google is told is that the page was viewed, that a check finished, and, if you ask for the report, that somebody inquired: three counts, with nothing attached to them. The domain you typed is never sent, and neither is your name or your address. Everything under Measurement, and what is stored in your browser applies here too, including that turning on Global Privacy Control switches it off and the checker goes on working. The full report, which opens at its own private address, carries no analytics at all.
- The summary needs nothing from you. Running a check does not require a name, an address or an account. That does not make it anonymous, and the next point says exactly what is kept.
- What we hold either way. The domain you typed and the result of the check, so a second look does not repeat work already done and the report has somewhere to live.
- What we record when a check is run. The domain you typed, the time, and the request it arrived on: your IP address, the country, region and city your connection reports, the name of the network it belongs to, your browser's user agent, and the page you came from. Alongside that we keep what the link you followed said about itself: any campaign or
utmparameters in it, a referral code if there was one, which page of ours you landed on, the site you came from as your browser reported it, and whether your screen is wide or narrow. None of that is about you; it is how we tell an advert that works from one that does not, and which partner sent you. This is kept whether or not you go on to give us an address, because the visits nobody puts a name to are exactly the ones we cannot otherwise account for. The IP address is erased after fourteen days. What is left after that is the domain, the country and the name of the network, none of which identify anybody, and we keep those so we can see what kind of traffic the page gets. - This changed on 13 August 2026. Until that date the address was hashed and thrown away, and this page said so. It is kept now, and this page says that instead. We would rather tell you than let a promise quietly stop being true.
- Stopping the checker being abused. Separately, a daily ceiling per visitor is counted from a one way hash of your address mixed with the date, so that count cannot be matched against any other day.
- If you ask for the full report. We keep the address you typed, your name if you gave one, and the time you asked. That record of the asking is the whole reason we may write to you, so it is worth keeping accurately. The report itself opens on the page rather than being emailed to you.
- What we do with the address. We give you the report, and we may follow up about it at most once. We do not sell it, we do not share it with an advertising network, and we do not add you to a mailing list. Asking for a report on your own domain is not a subscription to anything.
- Removing it. The report you get carries the same one click removal link as any other. It deletes the report and the address together, immediately, with no reply needed.
- Checking a domain that is not yours. Nothing stops you, because everything it reads is public. It does mean the resulting report is about somebody else's domain, and if they ask us to remove it we will, without asking who ran the check.
Email assessments we send
We sometimes write to a business we have no relationship with, with a report on how its email domain is set up. If you received one of those, this is the section that applies to you. The short version: everything in it came from public records, and one link deletes all of it.
- Where it came from. Your domain's public DNS records, which anyone can look up: SPF, DKIM, DMARC, mail routing and similar. Your business name and a contact address published on your own website or in a public business listing. Nothing came from inside your systems, and nothing came from anyone who was supposed to keep it private.
- What we hold. The domain, the result of that check, the address we wrote to, any notes we made while looking, and whether the report was opened.
- Who ran the check. MailArrive, which is our own service and the same company. It is not a third party, and it does not keep its own copy: the one held here is the only one, which is what makes deleting it on request something we can actually do.
- The report link is private. Each report has its own unguessable address, is marked not to be indexed by search engines, and is listed nowhere. It carries no advertising pixel, no analytics, and sets no cookies.
- How we count a view. That the report was opened, the network and city your internet provider reports, and whether it looks like a person's browser or an automated mail scanner. We do not store your IP address here either. To tell one visitor apart from another we keep a one way fingerprint of it, scrambled using that report's own address, so it cannot be reversed and cannot be matched against any other report. It exists so we can tell our own visits apart from yours, and it answers nothing else.
- Removing yourself. Every one of those emails, and every report, carries a removal link. It deletes the assessment, removes your address so we do not write again, and takes effect immediately. You do not have to reply, and you do not have to explain.
We do not sell this information, we do not share it with an advertising network, and we do not add you to a mailing list. If you would rather see what we hold before deciding, email hello@matanoit.com and we will send it to you.
How we use what we collect
- To answer your inquiry and provide the services you ask for.
- To send support replies, ticket updates, and appointment confirmations, by the method you chose.
- To understand which marketing actually works, in aggregate. We look at how many visits a campaign produced, not at what any individual did.
- To meet our legal, tax, and accounting obligations.
- To tell a business how its email domain is configured, and to see whether the report we sent was read. See Email assessments we send.
Who else handles your information
We use a small number of service providers. Each one only receives what it needs to do its job.
- Cloudflare hosts this website, its database, and our DNS.
- Web3Forms relays form submissions to our inbox as an email.
- Microsoft 365 is our business email and productivity platform.
- 3CX is our phone system, which handles calls and text messages, and which serves the live chat widget on this website.
- Telnyx carries our voice and SMS traffic to the mobile networks.
- Google receives analytics data from the free check and the service pages under /lp/: which page, roughly where from, and how you arrived. It never receives anything you typed, and it receives nothing at all from any other page.
- WhatsApp (Meta) receives your message if you choose to contact us there. Meta operates that service and can see that you contacted us and what you sent. We only receive what you send us there. If you would rather Meta was not involved, use any of our other contact routes and nothing goes to them.
We may also disclose information if the law requires it, or to establish or defend a legal claim. We will not hand over your information because someone simply asked.
What we do not do
- We do not sell your personal information, and we never have.
- We run no advertising tracker anywhere on this site, and no analytics outside the pages named under Measurement, and what is stored in your browser. The assessment reports we send carry none of it either.
- Apart from the live chat and Google Analytics on the pages named above, we do not load fonts or scripts from third party servers. Our fonts are served from our own domain. The one third party image anywhere on this site is the mailarrive.com verification badge in the footer.
- We never send your name, email address, phone number, or anything else you typed to an advertising network. Not hashed, not encoded, not in any form.
- We do not share mobile opt in data or consent with anyone, for any purpose.
How long we keep it
Inquiries are kept while there is a realistic prospect of working together, and after that for as long as we need them for our records. An email assessment is kept while there is a realistic prospect of working together, and goes immediately when someone uses the removal link on their report. Records of text messaging consent are kept for as long as you are opted in and for a reasonable period afterwards, because we are required to be able to evidence consent. Ask us to delete your information and we will, except where we are legally required to keep it.
Your choices
- Stop texts: reply STOP to any message from us.
- See, correct, or delete what we hold: email hello@matanoit.com and we will deal with it.
- Remove a report you asked for: use the removal link at the bottom of it. It deletes the report and the address you gave us together, immediately. See The free check at /check/.
- Remove an email assessment: use the removal link in the email or at the bottom of the report. It deletes the assessment and stops us writing again, immediately, with no reply needed. See Email assessments we send.
- Stop the visit counting: a browser with JavaScript disabled, or any content blocker, prevents it entirely. Nothing on the site breaks.
- Avoid the analytics: turn on Global Privacy Control, which we honor, or use any content blocker. The home page, the support and emergency pages and the legal pages carry none in the first place. See Measurement, and what is stored in your browser.
Children
This is a business to business service. It is not directed at children, and we do not knowingly collect information from anyone under 16.
Changes to this policy
When we add or change something that touches your information, we update this page and change the date at the top. There is no separate archive; the current version is the one that applies.
Contact
Matano Enterprises LLC, trading as Matano IT Solutions
New Jersey, United States
hello@matanoit.com
This policy describes what our systems actually do. If you find something here that does not match your experience of the site, tell us and we will fix whichever end is wrong.