Privacy policy.

Who operates this site

Reginald Crampton trading as Crampton IT Solutions operates superintelligence.jobs as part of Intelligence Exchange. This policy covers this website and our inquiry and correspondence paths.

Reginald Crampton monitors [email protected] and [email protected] for inquiries, privacy requests and manual email-preference requests.

Contact us about privacy: [email protected]

Information we receive

• Buyer inquiries: the contact and company information you provide, the question or workflow, desired outcome, process, risk, budget and timing details.
• Expert registrations: the contact, professional background, capability declarations, country/timezone, availability and rate information you choose to provide.
• Messages: addresses, correspondence and delivery information when you contact us or receive a requested acknowledgment.

Why we use it

We use information supplied to review and respond to inquiries, maintain the expert talent pool, discuss relevant work and administer correspondence. Current intake is reviewed manually.

Submitting an inquiry or registration does not enroll you in a newsletter or marketing list. A separately requested update service would need its own clear consent and unsubscribe process.

Please do not submit credentials, private conversations, confidential customer records or sensitive documents through these forms. The current intake does not accept file uploads.

Site and email providers

Our websites and Mailcow mail server run on a Vultr server in Sydney, Australia. Cloudflare supports website delivery and network security. Services handling a request can receive its IP address, browser information, requested URL and technical logs.

Mailcow stores correspondence in our mailboxes. MXroute is our outbound relay only; it does not host our inbox or Sent folders. Relaying messages involves addresses, message content and delivery metadata. Acknowledgment emails use a saved recipient and reference rather than copying the full submitted workflow or profile.

Encrypted database backups are copied to Google Drive. Cloudflare, MXroute, Google Drive and network routes may process information outside Australia. Their exact processing locations and some provider-held queue, log and backup lifetimes have not been verified. We do not represent all handling as confined to Australia or promise an exact deadline for erasing every provider copy.

Cookies and browser storage

Necessary site functions and user-requested preferences are separate from optional analytics. Use Cookie preferences in the footer to review or change this site's optional choice. Ignoring or closing the controls does not give consent.

Optional visit and performance analytics are disabled. If we introduce optional analytics later, we will explain its purpose and the information collected and ask for your choice before activation.

A saved privacy choice lasts 180 days, then the controls ask again. Each domain keeps its own choice; there is no cross-domain consent identifier. Clearing or blocking storage leaves optional analytics off.

Fonts are served from this site. Loading them does not require a Google Fonts request from your browser.

• si-consent-v1 (local storage): necessary to remember this site's category choices, policy/schema versions and timestamps for 180 days. It contains no cross-domain identifier.
• si-theme (local storage): Light, Dark or System after you choose an appearance. It stays until changed or cleared; it does not give permission for analytics.
• si-saved and si-followed (local storage): public vacancy/company identifiers when you save or follow items. They stay until you remove them or clear browser storage.
• si-market-v1 (session storage): temporary state for illustrative market screens in this tab. Live Buyer and Expert forms save submissions to our server; local prototype state is separate.

Keeping and removing information

Our approved working retention schedule is administered manually. Reginald Crampton oversees monthly cleanup reviews and privacy requests. The periods below are review and removal targets, not automatic expiry or a guarantee that every copy disappears on an exact date. The current application does not automatically delete inquiries or expert registrations by age.

We may retain specific information that is still needed for an ongoing engagement, an applicable legal or tax requirement, insurance, a complaint, a dispute or an investigation. Any hold must have a documented reason and review date, be limited to the necessary information and end when the reason no longer applies. It is not a reason to keep every message or attachment indefinitely.

Relevant correspondence, attachments, sent or archived messages and working exports are reviewed with the inquiry or project they relate to. Removing an application record does not itself remove email or exported copies. Our manual cleanup procedure must account for those locations too.

Database backup rotation targets are seven days locally and 30 days offsite. Upload failures, justified holds, Google Drive trash and provider-held copies can retain information longer. Mail backups and provider retention need separate confirmation. Recorded withdrawals and removals must be reapplied before restored data returns to use. These are operator-controlled steps; we do not promise automatic expiry or complete erasure from every provider copy.

You can ask us to review, correct or remove information, or withdraw an expert registration earlier. Requests are reviewed manually, including any narrowly justified information that must be retained. We do not promise immediate deletion from every backup or third-party system.

• Unsuccessful Buyer or research inquiries: target removal 12 months after the last meaningful contact.
• Expert registrations: review annually. After 12 months of inactivity, request reconfirmation and target removal after 30 days without a response. Earlier withdrawal can be requested.
• Commissioned research, where work is agreed: remove unnecessary working files 90 days after acceptance; retain final deliverables for 12 months unless agreed otherwise.
• Minimal contract records: a working target of seven years, subject to confirming applicable legal and insurance requirements and the relevant starting date. This does not mean keeping entire email threads by default.
• Tax records: generally at least five years, with the starting date, longer requirements and exceptions confirmed with an accountant.
• Routine technical logs: a 30-day target; security logs: up to 90 days where needed. Current container rotation limits file size and count rather than guaranteeing age-based expiry; the age targets require additional manual handling or controls.
• Future marketing: retain only the minimum suppression information needed to prevent unwanted marketing, separately from message histories. Marketing is currently inactive and there is no live automated marketing subscription or suppression service.

Email choices

Receipts and messages about a request or account action are different from marketing subscriptions. You can use the email preference/unsubscribe-request link in a message, or contact the address below about optional correspondence.

Those requests are handled manually in the current pilot. Necessary messages about a request you make may still be sent. There is no live automated subscription or suppression service claimed here.

Request email preference changes

Questions, corrections or complaints

Email the privacy contact with the information you want reviewed and the outcome you are seeking. We may need to confirm that a request concerns your information; do not send identity documents unless a suitable method has been agreed.

We will review a concern and respond with the result or next steps. If it remains unresolved, the Office of the Australian Information Commissioner provides information about privacy rights and complaint options.

[email protected]

OAIC privacy information

Changes to this policy

We will update the policy when the site's actual information handling changes. A material change to optional processing requires a new privacy-choice version rather than reusing an old choice for a new purpose.