Compliance
The constraint, stated once and enforced everywhere
Leads are held in Titan's own database, which makes LeadTitan Pty Ltd the accountable entity under the Australian Privacy Principles and an agency under the New Zealand Privacy Act 2020 — not a processor acting on your behalf. That is why the paragraph below is a constraint on what our engineering team is permitted to build.
Titan collects publicly available business information only. It respects robots directives, published site terms, rate limits and applicable law, and it does not attempt to bypass access controls, logins or protective measures. Records on the suppression or do-not-contact list are excluded from collection and from export.
It appears verbatim inside the product, on the Compliance settings tab, where the people using Titan see it as often as the people building it do.
How it is enforced
Six places the rule is code rather than intention
Robots is a hard gate
Crawl rules and crawl-delay are honoured in the one HTTP layer every fetch goes through — not per scraper, where one exception would quietly become the rule. A disallowed path is never fetched, and a refusal is recorded as the site's answer rather than our failure.
Declared, never inferred
Every batch states the market it was collected in, and anything outside the cleared list is refused with no job and no lead created. An address format is not a country, and a wrong jurisdiction stamped confidently is worse than one declared.
Checked again at the exit
Suppression and do-not-contact are applied at collection, at export and again at the connector boundary — the last gate before data leaves Titan. Exclusions are counted, because a silent one is indistinguishable from a bug.
No shared pool, ever
Every record belongs to exactly one workspace. There is no cross-tenant data and no lead-list resale — your book is yours, and the isolation is tested per endpoint rather than assumed.
Encrypted, never returned
Connector and provider credentials are encrypted at rest, never logged, and never serialised back out of the API. Collector devices are named credentials a workspace can revoke, and revocation is final.
Names and emails stripped by default
Personal details are removed before a prompt is built, and no page bodies or scan payloads are written to logs or error reporting.
Your obligations, and ours
What Titan does not do
Not in the product
- No bulk cold email sending, and no deliverability risk carried on your behalf
- No bypassing logins, paywalls or bot protection
- No buying, selling or sharing of lead lists between workspaces
- No collection in markets we have not cleared
In the product
- A derived jurisdiction on every record, driving retention and eligibility
- Field-level provenance for any record you are asked to justify
- Suppression and do-not-contact lists honoured end to end
- An access log covering what your team viewed and exported
To ask what Titan holds about a business, or to have a record suppressed, write to support@shiningtechnologies.com.au. This page describes how the product works; it is not legal advice about your own obligations when you make contact.
Qualified leads, collected the defensible way.
Open a workspace and see the evidence trail on a real record from your own market.
Collection and scanning are unmetered. Only the AI analysis spends a credit.