PRIVACY
Privacy notice
Last updated: 8 October 2026
Information you send us
If you use the enquiry form, we use the details you provide to respond to your request and prepare a relevant quote. The submission is stored in a private, access-controlled website inbox so it can be reviewed and followed up if email delivery is delayed. Share only the information needed for your enquiry and the work you ask us to prepare. We handle those details privately and use them for your request.
Blog-only quotation offer
On published article pages only, an optional promotion may appear after a desktop exit-intent signal or after the configured period of visible foreground time on a mobile device (60 seconds by default). Merely reading an article, seeing or closing the popup, or opening the quote form directly does not qualify. The one-time 25% discount is available only after you click the offer button, continue to the services page and submit an enquiry. While the offer is enabled in private Admin settings, it can appear again on each qualifying article visit; closing it does not create a frequency cap. Offer frequency does not use an IP address or persistent visitor identifier. An administrator can disable the whole offer or either device trigger. At the offer-button click, a separate first-party session cookie links the verified article, offer trigger and click time to the later form submission. That claim is held server-side, expires after seven days, and is consumed when a qualifying lead is saved. An authorised administrator can see this attribution in the private HQ and may apply the discount once to a quotation for that lead; the quote records the discount and its source.
When any enquiry form is submitted, the server also records the connection IP address it observes with the lead. For an offer lead, that address is shown only to the authenticated HQ owner alongside the source/offer details; it is not sent to the public page or aggregate analytics. The exact lead IP is retained for the period selected in HQ Security settings (7, 30, 60 or 90 days). The system redacts an expired address the next time a form is handled or the authenticated HQ lead inbox is opened; this is not a scheduled, real-time deletion job. If the hosting service uses a proxy, the server-observed address may identify that proxy rather than the visitor’s device. The offer session stores no IP address.
Tender and RFQ documents
Information and documents you provide for tender/RFQ assistance stay private within the company and are used only for your job. We do not reuse them for another client or share them outside the submission or supplier requests you approve. Temporary working copies are securely disposed of after the job is complete. Records needed for business or legal purposes are kept securely and in line with this notice.
Website measurement
The current audience dashboard counts an explicit click on a link to a published article, not an ordinary page load, homepage or archive browsing, article reading without a tracked link click, or service-card visibility. A click is counted at most once for the same first-party browser token, article and South African calendar day. A random browser token is generated only when a tracked article-link click needs to be sent, held in local storage and rotated daily; the server stores a keyed daily de-duplication digest and aggregate article totals, not the token itself. Broad source labels distinguish on-site article links from tagged HQ email article links; full referrer URLs, raw IP addresses, cross-site IDs and IP-based unique-person estimates are not included in these article-click totals. Older general page-view aggregates from earlier measurement may remain separately in historical storage; they can include ordinary page requests, are not reclassified as article clicks and cannot be selectively attributed to a particular owner's devices. Hosting access logs may process connection addresses under the host’s separate settings and retention rules. Search impressions and search clicks are measured separately through Google Search Console if that service is connected.
In private HQ manual emails and quotation/invoice emails, links to published articles may be tagged so a click-through can count after the article landing remains visible briefly. Opening an email alone sends no tracking event; no email-open pixel is used, and recipient-level click reports are not kept. Some email security scanners automatically follow links, so these totals may include false positives and are estimates rather than proof of human readership. Contact-form email is not instrumented. The site owner can exclude a specific browser/device in private admin Settings; this sets a first-party opt-out cookie and local browser flag to suppress future article-click beacons from that browser. The preference must be set separately on each computer/browser. It does not erase earlier events, change form-abuse protection or alter hosting logs.
Mail, client records and business administration
If the company connects a mailbox to its private HQ, the system uses the configured IMAP and SMTP servers to display inbox messages, send correspondence and route website enquiries. Mailbox passwords are encrypted before storage in private server-side storage and are not returned to the browser. The email dashboard records aggregate server-accepted or failed send outcomes, received/sent totals, and a separate aggregate count of clicks on tagged links to published articles in eligible HQ-sent emails. No email-open pixel is used, and recipient-level click reports are not kept. Some email security scanners follow links automatically, so click totals may include false positives. Contact-form email is not instrumented. The mail provider still processes and stores messages under its own terms. Authorised staff may also keep client contact records, quotes, invoices, task notes and their progress history in the private HQ to manage requested work and business records. Keep those records accurate and delete them when no longer needed, subject to applicable obligations.
Restricted security event history
Separately from aggregate article-click analytics, the private HQ can record the exact server-observed connection IP address, requested path, user-agent string and timestamps/hit counts for security review when a browser sends a tracked article-click beacon or a request reaches a monitored PHP endpoint. An opted-out article-click beacon is checked before its security event is recorded. This is a restricted security log, not a visitor-analytics measure or a count of verified people. It is kept for 30 days by default; the authorised administrator can select 7, 30, 60 or 90 days and can delete the log in HQ Settings. Raw IP addresses are not placed in the aggregate article-click files. Bot detection relies on user-agent hints and is heuristic, can be wrong or spoofed, and does not capture every crawler (for example, some JavaScript-disabled bots that never reach a monitored PHP endpoint). Automatic IP blocking is off by default; if the administrator enables it, repeated high-confidence scanner hints may cause a one-address block, with a risk of false positives or effects on people sharing a connection.
Client feedback
We publish a client’s exact feedback and only the approved display name and optional service or area details after confirming that the feedback is genuine and the client has agreed to public display. We do not publish review drafts. A client can ask us to remove their published feedback by contacting info@servicesolution.co.za.
How information is used
We use enquiry information to reply, scope the requested work and keep the related business correspondence. Authorised staff may review, mark as read, export or delete submissions in the private website HQ inbox. To limit automated form abuse, the form may retain a keyed, pseudonymous hash of a submitted connection’s IP address for rate limiting; it is not used in page-view analytics. The exact server-observed IP at form submission is also held in the restricted private lead record and redacted when a form is handled or the authenticated HQ lead inbox is opened after the selected retention period. Only an authenticated HQ administrator can view or export it; older leads without an IP field are not backfilled. Stale rate-limit records are removed on a later form submission. An authorised company administrator may block an exact connection IP address to prevent access to the website. For lookup, the address is encrypted in private storage and represented there by a keyed HMAC; to block static files at Apache, the exact address is also written to a protected managed rule in the root .htaccess file until the administrator removes it. A block can affect other people sharing that address, and proxies or changing addresses can limit its effectiveness. The restricted exact-IP/path security log is separate from the keyed-HMAC analytics and follows the retention and deletion controls described above. We do not sell enquiry details. Mail and hosting providers may process technical delivery information as part of providing their services.
Retention and requests
We keep enquiry correspondence only as long as needed for the enquiry, business records and applicable legal obligations. To ask about, correct or request deletion of information you submitted, contact info@servicesolution.co.za.
Updates
This notice should be reviewed against the company’s actual operating practices, providers and retention periods before the rebuilt site is published. We will update the date and wording when those details are confirmed.