Privacy
We count visits without knowing who you are.
This statement explains what data the site processes, why it is used, how it is protected and which rights you have.
The short version
Five sentences, if you would rather not read the rest
- Our visitor measurement uses no cookies and never stores your IP address. The identifier is a hash that is replaced every night, so we cannot recognise you tomorrow.
- Google Analytics does not load until you say yes. If you decline — or simply never answer — not a single request is sent to Google.
- If you send an enquiry, we use the information to assess the part and answer you. Your drawing is stored outside the public document root with access limited to authorised users.
- We resell nothing. No ad networks, no data brokers, no tracking pixels, no profiling.
- You can ask for access, correction or deletion at any time by emailing firmapost@rmetall.no.
Responsibility
Who the data controller is
The controller for the personal data described here is:
| Company | Rolvsøy Metallindustri AS |
| Company registration number | 981 465 415 |
| Visiting and production address | Torvstikkeren 20, 1640 Råde, Norway |
| firmapost@rmetall.no | |
| Telephone | +47 69 39 20 50 |
Being the controller means the company — not an individual, and not a supplier — decides why and how the data is used, and answers for it. That responsibility cannot be delegated away. Tasks can be outsourced; the responsibility stays here.
We are not required to appoint a data protection officer, and we have not. Privacy enquiries go to firmapost@rmetall.no and are handled by management.
This statement covers rmetall.no and the data the website collects. If we process data about you in another context — as an employee, as a contact at a supplier, or in a running customer relationship — the same rights apply, but the details are not described here.
Enquiries
When you send an enquiry or contact us
The site has two forms: the contact form and the quote request form. Both write to the same place, so nothing ends up in a side channel.
What you provide yourself
Required in the quote request form: name, email address and a description of what the part has to do.
Optional: company, company registration number, telephone, country, material preference, process preference, critical tolerances, surface requirements, quantity per order, annual volume, required delivery date, target price and a free-text message.
The contact form asks for name, company, email, telephone and message.
We never ask for national identity numbers, health data or other special categories, and you should not type anything of that kind into the free-text fields.
The files you upload
The request form accepts up to ten files, each up to 25 MB, in the formats STEP, STP, IGES, IGS, DWG, DXF, PDF, PNG, JPG, JPEG and ZIP. Both the file extension and the file's actual content have to match; a file pretending to be something it is not is rejected before it is stored.
The files do not go into a public folder. They go onto a closed disk outside the site's document root, in one folder per enquiry, under a randomly generated filename. There is no URL an outsider could guess. The files are only retrieved through an authenticated admin. We also compute a checksum of each file, so the same part submitted twice under two filenames is visible as one part.
Drawings and 3D models are treated as confidential customer material. Access is limited to authorised users and technical service providers processing data on our instructions. If you want a non-disclosure agreement signed before sending anything, tell us.
What is recorded automatically with the submission
- Which page you submitted from, and which language you were using.
- Campaign parameters (UTM) and the referring site, if you arrived through a link or an advertisement.
- A salted hash of your IP address. The IP address itself is never written to the database — the field is cryptographically bound so that a plaintext IP cannot be stored, no matter who writes the next piece of code. The hash is used to detect abuse of the form on the same day, and the salt is replaced at midnight.
- Your browser string (user agent). This is stored in clear text with the enquiry. It is used to tell a person from a script when a submission looks suspicious.
The forms are protected against spam by a hidden trap field and by a limit on how many submissions get through per unit of time. Neither requires cookies.
What happens next
The submission is stored with a reference number and is then followed up by a member of staff. The dialogue that follows — email, telephone and attachments — forms part of the same case.
Visitor measurement
When you are only reading the site
We keep our own visitor statistics on our own servers. They run for everyone, including those who have declined Google Analytics — and the reason they can is that they store nothing in your browser and nothing that can be tied back to you.
The identifier
To tell two page views of one visit apart from two different visits, we compute one number per request:
visitor hash = sha256(IP address | browser string | today's salt)
Three things stop that number from being usable to follow you:
- The IP address and the browser string are read, hashed and discarded. Neither is written to any column, any log file or any queue. The only thing that survives the request is the 64-character hash.
- The salt is 32 randomly generated bytes, minted afresh every day and held only in memory. It is never written to disk and never backed up. When it rotates at midnight, yesterday's hashes cannot be reproduced — not by us, not even with the original IP address in hand.
- The consequence is that "unique visitors" is a daily figure. If you visit on Monday and again on Thursday, you are counted twice. That is accuracy we have deliberately given up in exchange for not tracking anyone.
The hash from the visitor statistics is never joined to an enquiry. The two systems share no identifier.
What is actually stored
Per visitor (per day): the hash, the first and last time we saw it, the number of sessions and page views, country and possibly region if the proxy in front of us reports it, a coarse device type (phone, tablet, desktop), browser family and operating system family — without version numbers, because version numbers are what make a fingerprint precise enough to identify someone — and a flag for whether the traffic is a robot.
Per session: start and end time, duration, the page you entered on and the one you left from, where you came from (direct, search, social, referral, internal, or an AI assistant), up to five campaign parameters, language, device, browser, operating system, country, whether the visit was short enough to count as a bounce, and whether it ended in an enquiry.
Per page view: the path, the full address without its query string, language, page title, page type, timestamp, how long the page stayed open, how far down you scrolled, whether it was the first or last page of the session, the HTTP status code and how many milliseconds the server took.
Per event: the name of the event — and only names on a closed list in the configuration are accepted — plus category, path, a label, a numeric value and a timestamp. What is measured is clicks on call-to-action buttons, clicks on the phone number and email address, the steps through the request form, language switches, searches, outbound links, scroll depth and the technical performance figures Google calls Core Web Vitals.
What we deliberately throw away
- The query string. Only the five UTM parameters are kept.
fbclid,gclid,msclkidand anything else of that kind is discarded — those are identifiers built to follow people across websites, which is exactly the category of data this system exists in order not to hold. - Personal data in free text. Search terms and button labels are scrubbed for anything resembling an email address or a phone number before storage. If someone pastes their email into the search field, it is masked.
Robots
Search engines and the AI crawlers are counted, not discarded. How much the crawlers from ChatGPT, Claude and Perplexity read our pages is a number we want. Bot traffic is kept out of all human figures and totalled separately.
What we can and cannot answer
We can answer how many people read a page, where they came from and how many went on to the request form. We cannot answer who read which page, and we cannot assemble your path across several days. That is not a policy we could choose to change — it follows from the hash being replaced every night.
Processing and retention
Purpose, basis, access and deletion
We process the name, contact details, company information, messages and files you submit in order to assess the enquiry, clarify the production basis and, where relevant, enter into or perform a contract. The legal basis is steps prior to entering a contract and performance of a contract. When you contact us on behalf of a business, processing may also rest on our legitimate interest in answering professional enquiries.
The site keeps first-party operational and visitor statistics without cookies. The IP address is transformed into a salted identifier that cannot be used to recognise you across days. The purpose is secure operation and understanding which pages are useful.
Enquiries and attachments are stored outside the public document root. Access is limited to people who need the information to handle the case, and technical service providers processing data on our instructions. We do not sell personal data or use it for profiling or ad targeting.
Data is retained for as long as necessary for the enquiry, a potential or ongoing customer relationship, documentation of the delivery and statutory obligations. When the purpose and any applicable duties end, the data is deleted or anonymised. Contact firmapost@rmetall.no if you want to know what applies to your case.
Last updated: 24 August 2026.
Your rights
What you can demand, and how to do it
Under the GDPR you have the following rights in relation to us:
- Access. You can ask what data we hold about you, and receive a copy.
- Rectification. If something is wrong or incomplete, you can require it corrected.
- Erasure. You can require data to be deleted once we no longer have a basis for holding it. If we have an order to deliver or a statutory retention duty, we cannot delete everything immediately — but we will say what remains and why.
- Restriction. You can require us to hold the data still while a disagreement is resolved.
- Portability. Data you have given us yourself on the basis of consent or a contract can be handed back in a machine-readable format.
- Objection. Where we process something on the basis of legitimate interests — the operational statistics, for instance — you can object. We then either have to show a compelling reason to continue, or stop.
- Withdrawing consent. Consent to Google Analytics can be withdrawn at any time through "Change consent" at the foot of the page. It does not affect the lawfulness of what was collected before you withdrew it.
You are not subject to automated decisions with legal or similarly significant effects, and we do not carry out profiling.
How to use them
Send an email to firmapost@rmetall.no, or call +47 69 39 20 50. Say what you want done. We normally reply within 30 days. If we need longer because the request is complex, we say so once the production basis is sufficient.
We may ask you to confirm who you are before we hand anything over. That is not suspicion — it is the only way to avoid handing your data to somebody else.
If you think we have got it wrong
Tell us first. We want to know. But you always have the right to complain to the supervisory authority without going through us:
The Norwegian Data Protection Authority (Datatilsynet) — datatilsynet.no
Datatilsynet also advises individuals who are unsure whether something has been handled correctly.
Changes to this statement
If we change what the system does, we change this text at the same time. The description of the visitor measurement is also covered by automated tests: if one of them fails, a claim here is no longer true, and then the claim changes — not the test.
Questions
Something here you do not understand, or do not like?
Send an email. You get an answer from a person who can read the code, not from a legal department recycling a template.