Cookies
None. Nothing on this site writes a cookie, and there is no consent banner because there is nothing to consent to.
Legal / Privacy
Privacy Policy
What we collect through this website and through sample registration, why we have it, who sees it, and what you can make us do about it.
01Scope
Who this is, and what it covers
1.1Who is responsible
AMALINA Technologies, Inc. operates this website and the laboratory it describes. We decide what personal information is collected here and what happens to it, which under California law makes us the business responsible for it.
1.2What this policy covers
Everything on this website, and the information we hold about you because you sent us a sample or asked us about testing. It covers enquiries, sample registration, the reports we issue, and the records we keep behind them.
It does not cover websites we link to. The directions link in our footer opens Google Maps, and the certification link opens AHRI’s directory; once you are on one of those sites, that site’s policy applies and ours does not. Neither link sends anything to those companies until you click it.
1.3It also does not cover our affiliate
Chiller Services Refrigerant Recovery Reclamation, LLC — Chiller Services Refrigerants — is a separate company under common ownership, in the adjacent unit of this building. It has its own website and its own policy. If you are a customer of theirs, this document is not the one that governs that relationship. What we do with a laboratory result when both companies are involved is section 04.
02Collection
What we collect, and why
Everything we hold reaches us through one of the four sources below. Most of it is not about a person at all — it is about a machine, a cylinder, and what was in them.
| What | Where it comes from | Why we have it |
|---|---|---|
| Name, company, email address, phone number, the subject you pick, and whatever you write in the message field | The contact form, and email or phone calls to us | To answer you. We keep the thread so the next person who picks it up knows what was already said. |
| Sample registration: the same contact details, plus the site or return address, the fluid you are sending, the equipment it came from down to manufacturer, model and serial number, the sample and container identifiers, when the sample was drawn and by whom, and your own job or purchase-order reference | The registration forms, and the paperwork that travels with the sample | To run the correct test. What you declare selects the limits your result is judged against, so it is analytical input, not filing. |
| The result itself, the report, and the laboratory records behind it | Produced by us, from your sample | It is the thing you paid for, and it is a record we have to be able to stand behind if a number is ever disputed. |
| Server logs: IP address, time, the page requested, the browser string, and the page you came from | Recorded automatically by the company that hosts this site | Keeping the site up, and working out what happened when something breaks or someone attacks it. |
What we do not collect
This website takes no payments and has no checkout, so it never sees a card number. We do not collect Social Security numbers, government identifiers, health information, biometrics, precise location, or any of the other categories California treats as sensitive. We do not buy personal information from data brokers and we do not build profiles of visitors.
Most of it is about equipment
A registration is mostly a description of a chiller, a cylinder and a refrigerant. The personal part is small and obvious: who to call, and where to send the report. Where business information and personal information sit in the same record we treat the whole record as personal, because separating them after the fact is exactly the sort of thing that goes wrong.
// For review
Re-read this table against the live field list on both registration forms before publication. Two fields already collected need a decision rather than a description: the name of the person who drew the sample, which is personal information about somebody who is usually not our customer, and your own purchase-order reference, which can carry commercial detail we have no analytical use for. Anything a form starts asking for belongs in this table before the field goes live, not after.
03Cookies and tracking
This site sets no cookies and runs no analytics
That is a statement about the code, and it is checkable: open the developer tools on any page here and look at the storage and network tabs.
Analytics
None. No Google tag, no pixel, no session recorder, no heatmap, no A/B testing script.
Advertising
None. We do not run ad trackers, we do not sell personal information, and we do not share it for cross-context behavioural advertising.
Third-party requests
None on page load. Fonts are served from this domain rather than fetched from Google, so loading a page here tells nobody else you were here.
Because we do not track you, a “Do Not Track” header or a Global Privacy Control signal from your browser has nothing to switch off here. We treat a GPC signal as a valid opt-out request in any case. If analytics is ever added to this site, this section changes first — and you will be able to tell, because the tag will be visible in the page source of every page.
One piece of history, since it may affect you: earlier versions of this website, on the platform this one replaces, loaded a third-party analytics tag on every page with no consent gate. That tag is not part of this site.
// For review
Re-verify at launch and at every deployment that adds a dependency. This section is only true while the code stays this way, and it is the kind of claim that a single well-meant “let’s see how the site is doing” script turns into a false statement. If analytics is added, add a consent mechanism and rewrite this section in the same change.
04Disclosure
Who sees your result
We share a building with a refrigerant reclaimer under the same ownership. You are entitled to know exactly what that means for your numbers, and to read it here rather than find it out.
4.1Your result is yours
The report belongs to the customer who submitted the sample. We do not publish results, we do not use them in marketing, and we do not include them in any aggregated product or industry dataset. If we ever want to use anything from your work as an example, we will ask first and it will be anonymised.
4.2Third-party samples are not shared with the reclaimer
When you send us a sample, the result goes to you. It is not shared with Chiller Services Refrigerants, and the fact that you sent it is not shared either. Our affiliate does not get to see what a contractor or a competing reclaimer is holding, or what condition it is in.
The obvious exception is when Chiller Services Refrigerants is itself the customer — material it owns, submitted by it, for its own batches. Then it is the customer and it sees its own results, the same as you see yours.
If you are selling material to our affiliate and we are testing it, both companies are in that transaction and both see the number, because the number is part of the transaction. The independence page sets out how we keep that from becoming a conflict.
4.3Inside the laboratory
The people who need your information to do the work have it: whoever books the sample in, whoever runs it, and whoever releases the result. Nobody else needs it.
4.4Companies that work for us
The company that hosts this website and the company that carries our email necessarily handle information in transit — a hosting provider sees requests, a mail provider sees messages. They act on our instructions and are not free to use what they see for anything else.
4.5When the law requires it
We will disclose information when we are legally required to: a subpoena, a court order, a lawful regulatory demand. If we are permitted to tell you it happened, we will.
4.6We do not sell your information
We do not sell personal information, and we do not share it for cross-context behavioural advertising — which are the two things California law defines specifically and which people usually mean by “selling data”.
// For review
California also expects a statement covering the preceding twelve months, and this draft does not make one. The site this one replaces ran a third-party analytics tag on every page with no consent gate — section 03 — and whether that counts as sharing under the statute is a question for counsel. It is not one to answer optimistically in our own policy.
05Retention
How long we keep it — not yet decided
Nobody at the laboratory has set a retention period, so this section states none. Three answers are outstanding, and each is named below rather than filled in.
Unknown
Enquiries and contact details
No period has been set for how long a contact-form submission or an email thread is kept. Ask us to delete yours and we will — see section 06.
Unknown
Reports and laboratory records
A result that supports a regulated transaction has to be retrievable for years rather than months, and the applicable record-keeping rules sit on the customer as much as on us. The period has not been fixed.
Unknown
The physical sample
What happens to the refrigerant or oil left in your container after the test — held, returned, or disposed of — is not currently written down anywhere, so we are not going to state it here.
// For review
Three periods to set, with counsel and with whoever keeps the records: enquiries, laboratory records and reports, and physical samples. The third one is not only a privacy question — a retained portion of the sample is what makes split-sample verification at a second laboratory possible, so the answer decides whether that can ever be offered. Until all three are set, this section says unknown.
06California
Your rights, and how to use them
Under the California Consumer Privacy Act as amended by the CPRA. We extend these rights whether or not the statute's thresholds reach a business our size.
| Right | What it means here |
|---|---|
| Know | Ask us what personal information we hold about you, where we got it, what we use it for, and who we have disclosed it to. You can ask for the specific pieces, not just the categories. |
| Delete | Ask us to delete what we hold. We will, unless we are required to keep a record — a laboratory result that supports a regulated transaction is the usual reason. If we keep something, we will tell you what and why. |
| Correct | Tell us something we hold is wrong and we will fix it. This one matters more than usual here: a wrong company name or address on a report is a record-keeping problem for you as well as us. |
| Opt out of sale or sharing | Nothing to opt out of — we do not sell personal information and we do not share it for cross-context behavioural advertising. If that ever changes, a link to opt out appears on every page and this section is rewritten. |
| Limit use of sensitive information | Nothing to limit — we do not collect the categories California classes as sensitive. |
| No retaliation | Using any of these rights does not change your price, your schedule, or whether we will take your work. |
6.1How to make a request
Email info@amalinatechnologies.com, call (562) 404-9955, or write to us at 13564 E. Imperial Hwy, Unit D, Santa Fe Springs, CA 90670. Say what you want — to know, to delete, to correct — and give us enough to find you: the email address or phone number you used with us, and a sample or report number if you have one.
6.2How we check it is you
We will match what you tell us against what we already hold. For a request about a specific sample or report we may ask for a detail only the customer would know — the lab number, the cylinder identifier, the date it was sent. We will not ask you to send us a copy of your driver’s licence, and we will not create an account for you in order to answer.
An authorised agent may act for you if they give us written permission signed by you. We may still contact you to confirm it.
6.3How long we take
We acknowledge a request when it reaches us and aim to answer within 45 days, which is what the statute allows. If a request is complicated we may take another 45 days, and if we do we will tell you before the first 45 are up and say why.
6.4If you are not in California
Ask anyway. We are not going to run two processes, and a request from a contractor in Nevada gets handled the same way as one from a contractor in Norwalk.
// For review
Two questions for counsel. First, whether the CCPA and CPRA thresholds reach this business on its actual revenue and data volumes — this draft extends the rights either way, which is the safe position, but the answer decides what else is mandatory, including a formal request log and the twelve-month disclosure statement. Second, whether anything in the laboratory record set is exempt from deletion by another rule, and which rule.
07The rest
Children, security, and changes
7.1Children
This is a business-to-business laboratory service. The site is not directed at children, nothing here is marketed to them, and we have no reason to collect anything about anyone under 18.
We do not knowingly collect personal information from anyone under 16, and we do not sell or share the information of anyone under 16 — we do not sell or share anyone’s. If we learn we have collected something from a child, we delete it. If you believe a child has sent us information, tell us at info@amalinatechnologies.com and we will.
7.2Security
This site is served only over HTTPS, with strict transport security, framing denied, content-type sniffing off, referrer information trimmed on cross-site navigation, and camera, microphone and location access denied at the browser level. Open the response headers and you can see all of it.
Those are the controls on the website. How laboratory records are stored and who can change one after it is released is a separate question, and a more important one — it is covered in our terms of service. No system is perfect and we are not going to claim otherwise.
7.3Changes to this policy
When this document changes we will change the date on it and say what changed. If a change is material — we start using analytics, we begin sharing something we do not share today — we will say so plainly at the top of the page rather than relying on you to diff two versions.
Until it is adopted, this remains a draft and the banner at the top of this page stays where it is.