--- title: "Privacy · 316Software" description: "What 316software.com collects, why, and who else sees it. No selling, no advertising cookies without your yes." canonical: "https://316software.com/privacy" last_updated: "2026-10-21" --- # Privacy. 316Software is **one engineer**, and this site is a few pages with two forms on them. It collects only what that needs. Nothing is sold, and no advertising cookie is set unless you say yes. - **Who**: 316 Software Inc. - **Where**: British Columbia, Canada - **Last updated**: 9 October 2026 - **Ask**: [info@316software.com](mailto:info@316software.com) ## What it collects Six things. Two happen on every visit, because the site can’t be served without them. The rest only happen when you use a form or say yes. - **The contact form**: Your name, email, and message, plus company, phone and the service you picked, if you filled those in. It’s emailed straight to [info@316software.com](mailto:info@316software.com) through Cloudflare Email Sending. Before it goes, TypeSafe reads the message to label which service it’s about. There’s no database behind this site: your message is an email in my inbox, and that’s all. - **The service finder**: What you describe and your email. TypeSafe reads the description to match it to a service and a tier; your email isn’t sent to them. Both are then emailed to me with the match, so I can reply once if I can help. If you ask for it, the recommendation is emailed to the address you gave, once: the service and its prices, with nothing you typed in it. Nothing is stored anywhere else, and you’re not added to a list. - **The bot check on both forms**: Cloudflare Turnstile, which tells a person from a script. It reads your IP address and some properties of your browser and gives the page a token the server checks. It sets no advertising cookie and doesn’t follow you across sites. Cloudflare’s [Turnstile Privacy Addendum](https://www.cloudflare.com/turnstile-privacy-policy/) covers what Cloudflare does with it. - **Page counts**: Cloudflare Web Analytics, which runs on Cloudflare’s network instead of in the page: which page was opened, where the link came from, the country, and roughly what kind of device. No cookie, no fingerprint, no identifier that follows one visitor from one page to the next. - **Server logs**: The ordinary record of a request reaching Cloudflare: IP address, time, URL, user agent. It’s how a site is kept running and attacks get noticed, and it’s short-lived. - **Meta’s and LinkedIn’s ad tags, and only if you accept**: If you accept the cookie bar, the Meta Pixel and the LinkedIn Insight Tag load and report that you opened a page: the URL, your IP address and your browser, to Meta and to LinkedIn. They’re there so ads for 316Software can be shown to people who’ve visited this site, and so I can tell which ads led somewhere. Besides page views they report three moments: a contact message sent, a service finder description sent, and a call booked. Only that it happened, never what you typed. Neither runs before you answer, and a no is remembered exactly as long as a yes. ## Cookies, and how to change your mind A few ad cookies, and they need your yes. Three things kept in the browser that never leave it. - **`_fbp` and `_fbc` · cookies, Meta**: Set only after you accept, so Meta can recognize a browser it has already seen. They last about 3 months. Declining later deletes them. - **`li_adsId` · cookie and local storage, LinkedIn**: Set only after you accept, so LinkedIn can recognize a browser it has already seen. It lasts about 6 months, and declining later deletes it. If you’re signed in to LinkedIn, LinkedIn also reads its own cookies on linkedin.com; those are LinkedIn’s, and its cookie settings are where you change them. - **`316-consent` · local storage**: Your answer to the cookie bar and the date you gave it, kept for a year so you’re only asked once. It’s never sent anywhere, including to me. - **`316-theme` · local storage**: Whether you picked the light theme, the dark one, or your system’s setting. Also never sent anywhere. - **`316:finder` · session storage**: What you typed into the service finder, so it’s still there if you come back to the page. It lasts until you close the tab, and it isn’t sent anywhere. - **The booking calendar**: When a message or a finder description looks like work I do, you’re offered a 30-minute call: in a Cal.com frame on [/contact](https://316software.com/contact), or as a link to Cal.com’s own page from the finder and its email. Opening it puts you on Cal.com, and Cal.com sets its own cookies there under its own policy. If you send the form first, the frame opens with the name and email you just typed already filled in, so you don’t type them twice; nothing else from your message goes over. Not opening it loads nothing and sets nothing. ### Change your answer [Reopen the cookie bar](#cookies) and pick the other one. Accepting starts the tags on the next page; declining stops them and deletes what Meta and LinkedIn set here. ## Who else sees it Six companies, each doing one job. None of them buys anything from me, because nothing here is for sale. - **Cloudflare**: Serves the site, delivers the form email, runs the bot check and counts the pages. United States and its global network. - **Google**: Carries the 316Software mailbox (Google Workspace), so your message lands there. - **Cal.com**: Runs the booking calendar, and only for the people offered a call. If you book one, it holds what a booking is: your name, your email and the time you picked. - **Meta**: Only if you accept: page views, and that a form was sent or a call booked. Handled under Meta’s own terms and policy once it reaches them. - **LinkedIn**: The same, for ads on LinkedIn: only if you accept, the same page views and the same three moments, under LinkedIn’s own terms and policy. - **TypeSafe**: Reads the text of a contact message or a finder description and says which service it sounds like. It gets the words, plus the name and company on a contact message, but never an email address or a phone number. ### Where it goes These are American companies with worldwide networks, so your data is processed outside Canada and is subject to the laws of wherever it sits. That’s the trade-off for a site that loads quickly everywhere. ## What you can ask for PIPEDA and British Columbia’s PIPA give you these rights. One email reaches me, and I’m the one who acts on it. - **A copy, or a correction**: Ask what I hold about you and I’ll send it, or tell me what’s wrong and I’ll fix it. In practice, it’s the email you sent. - **Deletion**: Ask and I’ll delete our correspondence. I keep a message only as long as the conversation is going or the work it led to needs it. - **Your consent back**: [Reopen the bar](#cookies) and decline. No email needed, and nothing else on the site changes. - **A complaint that goes over my head**: If my answer isn’t good enough, the Office of the Privacy Commissioner of Canada and the Office of the Information and Privacy Commissioner for British Columbia both take complaints directly. ### Ask [info@316software.com](mailto:info@316software.com). Same inbox as everything else, and the same 2 business days. --- Page: https://316software.com/privacy The whole site for agents: https://316software.com/llms.txt