Your information
Privacy, in plain sight.
What we use. What we keep. What you can change.
Privacy notice · Version 2026.11.17.1 · Updated 17 November 2026
A basic check does not need a personal account.
Report emails and remembered browser preferences are optional.
Who is responsible
8thGuard is operated by Aunatron Systems Ltd, the controller of information we use to provide this service. Correspondence: P.O. Box 14131, Adum, Kumasi, Ghana. For privacy and account requests, email info@8thguard.com.
We provide transaction intelligence and early risk signals. We do not hold your assets or sell raw private information. This notice covers the website and our services through messaging channels where available.
Information we use
- Ask Kev. In Product Guide mode, your questions stay in the browser and closing the chat clears the conversation. In AI Support mode, the chat names the provider before you send a question. We send recent messages to that provider to generate the reply. 8thGuard records request counts and times for abuse prevention and uses a short-lived, coded network identifier to limit usage. Chat text is excluded from our usage records. Contact support opens a separate form where you choose what to share.
- Checks: the public identifier you submit, its chain, optional context, source responses, findings and report references. Public records can still relate to identifiable people.
- Accounts: verified email, minimal profile, language setting, protected session references, terms acceptance and security events. Ordinary account access does not automatically grant a private firm workspace or link messaging accounts.
- Private evidence intelligence pilot, where enabled: authorised firms submit structured evidence references, dependencies, permission observations, service measurements and verification requirements. We save encrypted inputs and results, method versions, integrity hashes and review decisions. A protected fingerprint of a review-evidence reference is kept; the firm retains the underlying supporting record. These records are visible within the authorised firm workspace, not the public verification service. This pilot does not sell submissions, publish them or use them for cross-customer training.
- Firm requests: firm name, verified contact email, request status and review history. Approved workspaces also have membership and signed-agreement evidence. Approval does not buy a paid service.
- Professional Network applications: professional and business details, selected public contacts, credentials, review context, identity-check references, consent records and review decisions. Only the approved profile and contacts you choose are published. Identity verification is separate from professional competence or authority.
- Payments: order, product, amount, status and provider references. Blockchain payments also produce public wallet and transaction information. Card details entered in a provider’s checkout are handled by that provider.
- Messages: contact details, channel identifiers, support messages and delivery status. The contact form collects your name, email, optional organisation, selected interests and brief so we can respond. Report emails are sent when you request them; authentication emails are sent when you request email sign-in.
- Local currency: our hosting provider supplies an approximate country from the connection’s IP address. Unless you choose a currency, we use it to default prices to GHS in Ghana and USD elsewhere. No browser location permission is requested, and we do not add a location cookie or save a location profile for this choice.
- Operation and security: IP address, device/browser details, timestamps and error or abuse logs processed by us or our infrastructure providers. The site adds no advertising or analytics trackers. See our cookie policy.
The identifier and chain are needed to check the intended record; context is optional. Email is needed for an email account or delivery. Without necessary service or payment information, we may be unable to fulfil that request.
Do not put private keys, recovery phrases, passwords, codes, identity documents or unnecessary information about another person into a check, contact form or message. Professional applicants upload an identity document only through the Didit-hosted verification page linked from their dashboard. Input filters cannot detect every secret, and a messaging provider receives your message before our service can screen it.
Why we use it
We use information to provide requested checks, reviews, results and support; manage accounts and firm access; reconcile service payments; prevent abuse; investigate failures; preserve issuance evidence; and meet applicable legal obligations.
Our grounds depend on the purpose and applicable law: steps you request or performance of our service agreement; necessary, proportionate service and security interests; specific legal obligations where applicable; and consent for optional uses where required. You can object to processing based on our interests and withdraw optional consent.
Automated checks produce observations, indicators and coverage limits. They do not establish safety, identity, intent or fraud. You can ask for an explanation or human review of an error or concern. We do not use checks to make employment, lending or similar eligibility decisions about you.
Reading this notice is not blanket consent. Service terms do not opt you into marketing or optional storage. Contact and report details are not automatically added to a marketing list.
Who receives information
- Infrastructure: Supabase for data and authentication, Railway for the check engine, Vercel for the website, and Cloudflare for delivery and security.
- Email: Resend delivers requested reports, authentication emails and contact enquiries to our team. Hostinger handles our support mailbox. Recipients and their mail providers may keep copies.
- Professional identity verification: Didit processes the document and selfie on its hosted page, including biometric comparison after its consent step. 8thGuard receives the result, reference and limited identity details needed for review. We do not store raw identity images or biometric templates in our CMS. The provider shows its terms and privacy notice before capture; an applicant who cannot complete the process can contact the review team.
- Messaging and payments: Telegram or Meta/WhatsApp when you use those channels, and the provider named in your checkout, such as Paystack or Polar. Providers apply their own privacy terms to processing they perform independently.
- Evidence sources: relevant explorers, public RPCs and security-data sources receive the public identifier and chain needed for a lookup. The report identifies source coverage and failures.
- Authorised reviewers: information needed for the review or support you request. Disclosures may also be made where required by applicable law or valid legal process, or where necessary and lawful to protect rights and address abuse.
Our database is hosted in Ireland. Resend processes message data in the United States; other providers may process data in additional countries. Processing is not limited to your country, Ghana or the EU. Applicable safeguards and transfer requirements depend on the service and locations concerned. Contact us for information about providers and safeguards relevant to your request.
Public verification
A verification link shows a proof identifier, product, issue date, hash and status, rather than private report content. Recent-activity summaries may show chain, check kind, indicator count, coverage summary and rounded timestamps. They exclude the submitted identifier, message context and contact details.
Limited metadata can still be linked with other information. Hashing, encryption and removing names do not automatically make information anonymous. 8thGuard cannot erase public blockchains.
How long we keep it
Automated cleanup runs daily. Removal can follow eligibility by about a day; outages can extend that delay.
| Record | Handling |
|---|---|
| Retail check inputs and reports | Eligible for cleanup after 30 days. Encrypted messaging handoff contacts have a 30-day target based on the recorded inbound date. |
| Private evidence intelligence pilot | Encrypted inputs and result content become unavailable after 30 days and are eligible for scheduled erasure. Minimal run references, integrity hashes, review history and audit metadata currently have no automatic expiry; necessity and rights requests are assessed separately. Downloaded copies remain with the recipient. |
| Report email job | Encrypted destination and prepared report expire within 23 hours; cleanup may run later. Delivered email is a separate copy. |
| Contact enquiry job | The encrypted brief and contact details are cleared when the email provider accepts the message or delivery permanently fails; otherwise they expire within 23 hours and cleanup may run later. The team mailbox retains a separate correspondence copy. Request references, keyed email hashes, selected interests and delivery audit records currently have no automatic expiry. |
| Personal account | Kept while open. Confirmed deletion removes the identity, linked profile and sessions, subject to shared-access safeguards. A sign-in session lasts up to eight hours. |
| Deletion confirmation | A minimal completed-deletion record is eligible for removal after 90 days. Uncertain outcomes stay for investigation. |
| Unanswered firm request | Expires after 30 days. Decision, withdrawal or expiry clears contact email and duplicate firm name. Approved membership and agreement evidence need separate offboarding. |
| Professional applications and checks | Active listings retain their application and review evidence while required checks remain current. Drafts, information requests, declined, hidden and withdrawn applications enter the removal queue after 30 days without an update. Unresolved submitted or in-review applications enter it after 90 days. Expired listings enter it 30 days after expiry. Staff coordinate provider and local erasure; entering the queue is not completed deletion. |
| Professional identity-provider records | The network’s Didit application is configured for one-month verification-data retention, with face templates deleted alongside the session. Earlier removal requests require provider confirmation. Limited audit records and encrypted backups have separate handling, and any restored backup must reapply completed removals. |
| Firm check and Ready content, where offered | Seven-year product-policy target, subject to the applicable contract and legal requirements. This is not a universal statutory duty. |
| Payment, terms, proof and security evidence | Separate from account/report cleanup. Proof hashes, limited outcomes and some audit records currently have no automatic expiry. Legacy messaging payment and review records also need separate retention review. Necessity, legal duties and rights requests are assessed individually. |
Providers have separate logs, caches and backup schedules. On the Resend plan used here, email content and logs remain for 30 days and backups for seven days; see Resend’s retention information. This does not set retention for your inbox or every other provider.
Deleting an active account does not immediately erase backups, payment records or required evidence. Rights requests also consider provider-held copies processed on our behalf. We explain retained information and reasons. Independent provider records and public chains are outside our direct control.
Your choices and rights
Depending on applicable law, you can request access, correction, deletion, restriction or portability; object to processing; withdraw applicable consent; and question a significant automated decision. You can ask a person to review an inaccurate result.
Use Your data rights for deletion and other requests, or email info@8thguard.com. We use proportionate checks to confirm control of the account or record. Do not email passwords, sign-in codes or identity documents. We respond within applicable legal timeframes and explain permitted extensions or limits.
Change optional storage through cookie settings. Choosing essential only does not sign you out or prevent a purchase. Clearing cookies or deleting a chat does not delete server records.
You may complain to Ghana’s Data Protection Commission or another competent authority where applicable.
Security, children and changes
We use access controls, encrypted connections, protected credentials and restricted operational access. Selected contact and session fields are encrypted by the application. This does not mean every field is encrypted in the same way or that authorised staff cannot access information needed to help you.
The service is intended for adults aged 18 or over. Contact us if a child has provided personal information so we can assess and address it.
We update this version and date when processing changes. Where a new use requires permission or additional notice, we obtain or provide it before that use begins.