Privacy notice
How the three sites, the optional joke.scot contact form and outbound charity links handle personal information.
Who runs these sites?
This notice covers ai.scot, si.scot and joke.scot, collectively this independent three-domain satire project.
Data controller: [INSERT OPERATOR'S LEGAL NAME]
Contact email: [INSERT WORKING PRIVACY EMAIL]
Postal contact: [INSERT BUSINESS OR CONTACT POSTAL ADDRESS]
These contact details must be completed by the operator before publication.
What information is collected?
Reading the three sites does not require registering or completing a form. Our web hosting may record an IP address, date, requested page, response, referring page and browser identifier in operational/security logs.
If you use the contact form on joke.scot, you provide your name, email address and message. The contact page also opens a short-lived PHP session for its anti-abuse token and records a one-way hash of your IP address, along with submission timestamps, for rate limiting.
Following a charity donation link takes you directly to the independent charity's own website. We do not take payments or receive donor details through these pages.
Why is this information used?
Technical logs are used to deliver the site, diagnose problems and prevent abuse. The proposed lawful basis is the operator's legitimate interests in running and securing the site, subject to the operator confirming the assessment. When you voluntarily contact us, your name, address and message are used to respond to your enquiry; the anti-abuse cookie and hashed-IP rate limits protect the form. The operator must confirm appropriate lawful bases before publication.
Analytics, adverts and cookies
No advertising or analytics scripts are included. Reading the joke or viewing the charity list does not itself start a site PHP session. Opening joke.scot/contact.php creates a session and an essential session cookie (PHPSESSID by default) for CSRF protection and basic form security. It expires when the browser session ends. The hosting, proxy or CDN may use additional technologies that the operator must verify. See our cookie policy.
Who receives the data?
Hosting and security providers may process technical logs. Contact form messages are transmitted using the operator's existing SMTP provider (PHPMailer), delivered to the operator's configured inbox, and may be stored in the relevant email systems. We do not send visitor information to the listed charities: only when you choose to follow an external link does your browser contact the charity's site. We do not sell visitor lists or include third-party advertising tags.
How long is it kept?
Server logs: [INSERT ACTUAL LOG RETENTION PERIOD]. Contact messages: [INSERT CORRESPONDENCE RETENTION PERIOD]. The form's hashed-IP rate-limit records retain at most the most recent three attempt timestamps inside a rolling one-hour window, but old on-disk files persist until the operator sets up a cleanup task. Session lifetime and storage must be confirmed on the deployed PHP server. The operator must set actual retention/deletion procedures before publishing.
Where is it processed?
[INSERT VERIFIED HOSTING LOCATIONS AND DETAILS OF ANY INTERNATIONAL TRANSFERS / APPLICABLE SAFEGUARDS, OR STATE THAT NO SUCH TRANSFERS OCCUR.]
Your choices and rights
Depending on the circumstances, you can request access to your data, ask for inaccuracies to be corrected, request erasure or restriction, or object to processing based on legitimate interests. Other rights may apply. Please use the privacy contact above. You can also complain to the UK Information Commissioner's Office if UK data-protection law applies.
Other websites and charitable giving
The charity directory links to the charities' own donation pages. Their sites and donation providers control their own payments, cookies and privacy notices. We are not fundraising on their behalf or processing donations, and inclusion does not imply endorsement or an agreed partnership. The site also links to photo and source credits.
Changes to this notice
We will update this page when the site or its data practices change. Last drafted: 3 October 2026.