Privacy · no cookies until you allow them
Privacy Policy
This site sets no cookies until you say yes, and refusing costs you nothing: every page, every estimator, the readiness check and the contact form work either way. The booking calendar on the contact page is Calendly’s; it loads only when you press Show available times, and Calendly and the services it uses then set their own cookies. Five things happen whatever you answer, each described below. Unless your browser sends Global Privacy Control or Do Not Track, every page view sends Google a signal without cookies, and the server log is read to count visits and returns. An estimate you act on is recorded, and a random identifier links your own estimates to each other. The first page of this visit and the site that sent you are kept until the tab closes, so a message or a booking can say where you came from.
1Who is responsible
This site is operated by Serhii Skrypnyk, a sole trader registered in Ukraine as an individual entrepreneur, working remotely and worldwide. For anything on this page, write to serhii@solutions4sf.com.
Where this site processes your data for its own purposes, the controller is Serhii Skrypnyk. Where personal data is processed on behalf of a client during an engagement, the client is the controller and the role is set out in the Data Processing Addendum.
2What is collected, and when
2.1 What you send deliberately
The contact form on this site creates a record in Salesforce. It carries what you typed:
- Your name
- Your email address
- Your company
- Your message
- Which page you sent it from, anything you had produced on that page, such as an estimate, the symptoms you ticked or a readiness verdict with the measures behind it, and your answers to the three short questions on the home page, if you answered them
- Your browser's time zone, for example America/Chicago, so the confirmation can give the reply time in your own time
- Where this visit started: the first page you opened and the site that sent you, for example google.com, or direct. It is kept in your browser's session storage only until the tab closes, so it describes this visit and no earlier one
- The random identifier described in 2.2, so the message and any estimates you made read as one person
Three other actions also create or update a record in Salesforce:
- Acting on an estimate. Copying, printing, saving or mailing an estimate, showing its payment details, or opening its sample invoice records that estimate under the reference printed on it: the tool, the figure, the lines and phases it was built from, your answers to the estimator, the page it was made on, and the campaign in the page address if there was one. This is what lets a message quoting the reference be answered.
- An address typed into Email it. It is kept with the estimate, a copy of the estimate is emailed to it, and a lead record is created for it. If you type a colleague's address, tell them.
- Asking for the readiness breakdown. The breakdown is sent with the address you give, so it can be emailed to you: the verdict, each measure with its value, the order of work with its weeks and cost, the average deal size behind the exposure figure, the names of the first two files you loaded and the total row count. The page you asked from, with the campaign in its address if there was one, and the identifier in 2.2 go with it. The rows themselves never leave the browser tab.
Using an estimator or the readiness check without doing any of these sends nothing to Salesforce; only the cookieless count in 2.3 notes which tool was used and the figure it gave.
Booking a call. On the contact page the calendar loads from Calendly only when you press Show available times; the booking buttons elsewhere open the same calendar in a new tab. Calendly receives what you enter there: your name, your email address, the time you pick and your answers to its two questions. The second answer is filled in for you: the page you booked from and, if you have not allowed analytics, the first page of this visit and the site that sent you. If you have allowed analytics, those two are replaced by where you first arrived, with any campaign tags in that address, your visit and page counts, and the last two estimates or readiness verdicts you produced. The calendar’s address carries a shorter form of the same details as campaign tags. Calendly receives both as soon as the calendar opens, even if you do not book; you can read and change the answer before booking, and nothing is booked until you press Schedule Event. Once the calendar is open, Calendly and the services it uses set their own cookies, among them cookies for Cloudflare and Google reCAPTCHA checks against bots and for a Stripe check against fraud; Calendly’s privacy notice explains its use of cookies.
2.2 A random identifier, set whatever you answer
The first time you open a page, your browser stores one entry in local storage named s4-visitor. It holds a random string, the date of your first visit, how many visits you have made, the seconds a tab of this site was actually in view, and how many estimator configurations you tried. It is not derived from your device, your IP address or anything else about you, and nothing sends it anywhere until you act on an estimate, ask for a readiness breakdown or send the contact form. Then it travels with that record, together with your browser's time zone and its local day and time, so that several estimates from one person read as one person coming back rather than as several strangers.
It is set whether or not you allow analytics. That is a deliberate choice, and this paragraph is its price. To remove it, clear this site's data in your browser; you then arrive as a new visitor.
2.3 Visits counted without cookies, whatever you answer
Google Analytics 4 runs on every page in Google’s Consent Mode. Until you allow analytics, it runs with storage denied: it sets no cookie, reads none, and stores no identifier in your browser. Each page view and each use of a tool sends one cookieless signal to Google. The signal carries the page, the time, the browser type and the consent state. For a tool it also carries the tool's name, the figure it gave and the choices you made in it, such as the symptoms you ticked or your answers to the three questions on the home page. Google Analytics attaches no lasting identifier to these signals, so they are not linked from one page to the next or to you. It shows them in reports only when a site is large enough for Google to model them. This site is not, so the number of visitors comes from the server log described below. Advertising signals are denied for every visitor, always.
If your browser sends Global Privacy Control or Do Not Track, Google Analytics does not load at all and counts nothing, unless you allow analytics on this page yourself.
The web server also keeps the standard access log that every site keeps: the address requested, the time, the IP address, the browser type and the page you came from. Nothing is stored in your browser for it. Once a day the log is read to count how many people came and how many came back, with each device shown only as a short code made from the IP address and browser type; the IP address itself never appears in a report and is not linked to you or to anything you send.
2.4 What is collected only if you allow it
Allowing analytics is your choice, and refusing costs you nothing: every page, every estimator, the readiness check and the contact form work either way. If you do allow it, three things start:
- Google Analytics 4 cookies. Google Analytics may then set its own cookies, so repeat visits are recognised, and records pages viewed, approximate location from a truncated IP address, device and browser, and which tools you used.
- Salesforce Account Engagement sets a visitor cookie so repeat visits can be recognised.
- A visit history in your own browser, held in local storage: when you first arrived, which page you landed on, the referring site and any campaign parameters, how many visits, which pages you have seen, which tools you used and what those produced.
This is profiling, and it is described plainly because it is. If you then send the contact form, that visit history is attached to your message so a first reply can start from what you actually did rather than from a blank page. If you open the booking calendar, a short form of it goes to Calendly, as 2.1 describes. If you have not allowed analytics, there is no history to attach and none is sent.
You can change your mind at any time on this page. Switching to essential only stops the cookies and the tracker, clears the visit history held in your browser, and leaves only the cookieless count described in 2.3. If your browser sends Global Privacy Control or Do Not Track, that is treated as a refusal and you are never asked.
2.5 Cookies
With analytics refused, this site sets no cookies, and Google Analytics sets none either. The only cookies before a yes come with Calendly’s booking calendar, and only once you open it. This site stores two entries in local storage: your choice, which is what stops it asking again, and the identifier described in 2.2. One more entry lives in session storage for as long as the tab is open: the page this visit started on and the site that sent you, as 2.1 describes; closing the tab removes it.
With analytics allowed, Google Analytics and Account Engagement each set their own cookies, and the visit history above is written to local storage. If you then send the contact form, the Google Analytics client id held in its cookie is sent with it, so the message can be matched to the pages Google Analytics recorded for that browser.
3The legal basis for each of these
- Consent, GDPR Article 6(1)(a). Analytics cookies, the Account Engagement tracker and the visit history. Withdrawable here at any time, with no effect on what happened before you withdrew.
- Steps before a contract, GDPR Article 6(1)(b). Replying to your enquiry and preparing a proposal.
- Legitimate interest, GDPR Article 6(1)(f). Keeping correspondence readable, preventing abuse of the form, recording an estimate you act on so a message quoting its reference can be answered, the identifier in 2.2 that links your own estimates, the cookieless signals to Google Analytics in 2.3, and the count of returning visits from the server log in 2.3. Global Privacy Control or Do Not Track switches off the cookieless Google Analytics count; the server log count cannot see those signals and covers every visit. You can object at any time, as section 7 describes.
4What your data is used for
- Replying to what you wrote, and preparing a scope or estimate if you asked for one
- Sending service information you actively requested
- Understanding which pages are useful, from the server log and, if you allowed analytics, from the analytics cookies
- Detecting abuse of the contact form
It is never used for any of the following:
- Sold or rented to anyone
- Sent to advertising networks or used for cross-context behavioural advertising
- Used to train an artificial intelligence model
- Used for automated decisions that produce a legal or similarly significant effect on you
- Used to send marketing you did not ask for
5Who else touches it
These are the only third parties involved, each under a written agreement that limits them to the purpose listed:
| Service | What it does | Where | Safeguard |
|---|---|---|---|
| Bluehost | Hosting for solutions4sf.com | USA | Standard Contractual Clauses |
| Salesforce | The CRM record created when you send the contact form, act on an estimate, or ask for the readiness breakdown | USA and EU | Data Privacy Framework, Standard Contractual Clauses |
| Salesforce Account Engagement | Visitor tracking, only after you allow analytics | USA | Data Privacy Framework, Standard Contractual Clauses |
| Google Analytics 4 | Counting visits without cookies for every visitor, and site usage with cookies only after you allow analytics, IP anonymised | USA and EU | Data Privacy Framework, Standard Contractual Clauses |
| Microsoft 365 | Email correspondence and the calendar calls are booked into | USA and EU | Data Privacy Framework, Standard Contractual Clauses |
| Calendly | Booking a call: the calendar on the contact page and the booking links | USA | Data Privacy Framework, Standard Contractual Clauses |
Some of these are based in the United States. Transfers rely on the EU-US Data Privacy Framework where the provider is certified, and on Standard Contractual Clauses adopted by the European Commission otherwise, with encryption in transit and at rest as a supplementary measure.
If this list changes, this page changes with it, and clients with an active engagement are told at least thirty days beforehand and may object on data protection grounds. The same commitment is written into the Data Processing Addendum.
6How long any of it is kept
- Contact form, estimate and readiness records in Salesforce: three years from the last contact or action, then deleted, unless you become a client.
- The identifier in your browser: until you clear this site's data.
- Email correspondence: three years from the last message.
- Analytics: fourteen months, then aggregated beyond recovery.
- Server access log: four hundred days, then deleted.
- Visit history in your browser: until you clear it, refuse analytics, or clear your browser storage. It leaves your device only when you send the contact form or, in short form, when you open the booking calendar, as 2.1 describes.
- Client engagement records: the length of the contract plus seven years, which is a tax and professional liability requirement rather than a choice.
7Your rights, and how to use them
If you are in the EU, the UK, or a jurisdiction with equivalent law, you can ask for any of the following:
- Access. A copy of everything held about you.
- Rectification. Correction of anything inaccurate.
- Erasure. Deletion, where there is no overriding legal reason to keep it.
- Restriction. A pause on processing while something is disputed.
- Portability. Your data in a machine readable file.
- Objection. To anything relying on legitimate interest.
- Withdrawal of consent. Immediately, on this page, without writing to anyone.
For all except the last, email serhii@solutions4sf.com with "GDPR request" in the subject. The answer comes within thirty days. If it does not satisfy you, you may complain to the data protection authority where you live.
California residents have a separate set of rights, set out in the California Privacy Notice.
8How it is protected
- HTTPS on every page, with modern transport security
- Two factor authentication on every account that can reach personal data
- Encrypted disks, a password manager, and no client work over public wireless networks
- Access limited to one person, because there is only one person
If a breach affects your personal data, you will be told within seventy two hours.
9Children
This is a business to business service. Data is not knowingly collected from anyone under eighteen. If any is found, it is deleted.
10Changes to this policy
The date at the top of this page changes whenever the policy does. Where a change is material and you have an active engagement, you will be told directly rather than left to notice.
11Contact
Serhii Skrypnyk, Senior Salesforce Administrator. Email serhii@solutions4sf.com. Also on LinkedIn and Trailblazer.