What this site collects.
Relling Systems runs this website. This page says plainly what it gathers, why, who else touches it, and how to have it deleted. It covers rellingsystems.com only — not the workcells we deploy, whose data never leaves your plant.
What you give us
The forms on this site collect information, and only when you choose to fill one in:
- Contact and intro-call requests — name, company, work email, your role, what you want to automate, and for an intro call the time slot you picked.
- Job applications — name, email, the role, work authorisation, country, an available start date, a link you provide, and anything you write in the message.
- Challenge coin requests — name, company, email, and a postal address, because we post you a coin.
Form submissions are delivered to us by email through FormSubmit, which relays the message and does not need an account or a database of its own. We reply from rellingsystems.com addresses and keep the correspondence in our mailboxes.
What we collect automatically
Six analytics and advertising tools run on these pages. None of them is given what you type into a form, and we do not combine what they report with it.
- Vercel Web Analytics — page views and referrers, aggregated. No cookies, no cross-site identifier.
- PostHog — product analytics: which pages are read, which buttons are used, and whether a form was completed. Sets a first-party cookie to recognise a returning browser. Hosted in the United States.
- Meta Pixel — measures whether an advert on Facebook or Instagram led to a
request. Sets Meta's
_fbpcookie and reports page views and completed forms to Meta, who may match them to a Meta account. - Google Analytics and Google Ads — measures whether a Google search advert led to a
request. Sets Google's
_gacookies and reports page views and completed forms to Google, who may match them to a Google account. - Microsoft Advertising — the same, for adverts on Bing. Sets Microsoft's
_uetsidand_uetvidcookies and reports page views and completed forms to Microsoft. - RB2B — visitor identification. For visitors in the United States, RB2B tries to work out which company, and which person at it, is reading the page, by matching your browser against its own data partners. When it succeeds it gives us a name, a company and a business email address, and we may use that to get in touch. It is the one tool on this list that can tell us who you are before you have told us. It does not run for visitors outside the United States.
When you complete a form, your email address and phone number are also handed to Google and Microsoft so that they can match the conversion to the advert you clicked. Each of them hashes the values in your browser before sending them, and compares the hashes against its own.
When you complete a form we also report that conversion to Meta from our own server, so it is counted even if the pixel in your browser never runs. That report carries the same information the pixel would have sent, plus your IP address and browser user-agent, which Meta uses to match the conversion to an advert. Your email address and your name are each turned into a one-way SHA-256 hash in your browser before they are sent: the values themselves never reach our server, and Meta receives only the hashes, which it compares against hashes of its own. The browser and server reports share an identifier so Meta counts them once, not twice.
If we later record in our CRM that your enquiry was answered or qualified, we report that step to Meta as well, using the same hashed email and name — so an advert is credited only when a real conversation happened, not merely when a form was filled in. Nothing is reported for enquiries we close or disqualify.
Our web host, Vercel, keeps standard server logs, including IP addresses, for a short period to serve and secure the site.
What we do with it
We use what you send to answer you, scope work, and — for applications — to hire. We use the analytics to understand which pages are useful and whether our advertising is worth running. We do not sell personal information, and we do not share it with anyone beyond the processors named on this page.
Turning it off
- Global Privacy Control — if your browser sends a GPC signal, we treat it as an opt-out of advertising analytics.
- Meta — your Meta ad settings control how Meta uses activity from sites like this one.
- Google — your Google ad settings control how Google uses activity from sites like this one.
- Cookies — blocking third-party and analytics cookies in your browser stops PostHog, the Meta Pixel, Google, Microsoft and RB2B. Nothing on this site needs them to work.
- RB2B — if RB2B has identified you and you would rather it had not, email us and we will delete the record and not contact you on the strength of it.
- Anything you sent us — email ping@rellingsystems.com and we will tell you what we hold and delete it on request.
How long we keep it
Enquiries and the correspondence that follows are kept while there is a live conversation and for as long as our records require afterwards. Applications are kept for the role and for future openings unless you ask us not to. Analytics are retained on the schedules set by PostHog, Vercel, and Meta.
Where we operate
Relling is an American company based in San Francisco, and our processors store data in the United States. This site is aimed at US manufacturers; if you contact us from elsewhere, your information will be handled in the United States.
Children
This is a business site. It is not directed at children, and we do not knowingly collect information from anyone under 16.
Changes and contact
If this changes we will update the date at the top of the page. For anything on it, write to ping@rellingsystems.com, or Relling Systems, San Francisco, California.
This page describes our actual practice rather than restating the law, and it is not legal advice.