Privacy & Data Protection

Privacy Policy

Effective: September 1, 2026

This Privacy Policy explains how TrustLens processes information when you use our digital safety tools, accounts, subscription features and scam-reporting services.

1. About TrustLens

TrustLens is a digital safety tool developed and operated by GeekyAce Digital Hub. It helps users identify possible scam, phishing and fraud warning signs in messages, websites, QR codes and screenshots.

2. Information We Process

Depending on how you use TrustLens, we may process information such as your email address, profile information, account identifier, subscription status, Family membership information, usage counts, safety-check history, submitted text, URLs and scam reports.

We may also process technical information necessary to operate the service, such as authentication session information, request data, timestamps and service logs generated by our infrastructure providers.

3. Account Information

When you create a TrustLens account, information such as your email address and profile details may be stored so that we can authenticate you, provide account features, associate your saved history with your account and manage plan access.

TrustLens currently uses Supabase for authentication and database services.

4. Safety Checks and History

When you submit content for analysis, TrustLens may process the text, URL, QR content or extracted screenshot text needed to generate a risk result.

Signed-in users may have their check history stored in their TrustLens account. This history may include the submitted input, risk score, risk level, reasons, recommendation, check type and related URL information where applicable.

If cloud history saving is unavailable, TrustLens may fall back to browser-based storage for that check.

5. Guest Use and Browser Storage

Users who are not signed in may have limited information stored locally in their browser, including guest usage counts and local check history.

This browser storage is used to support guest limits and local history features. Clearing browser storage may remove locally stored TrustLens information.

6. Screenshot Analysis

Screenshot OCR runs in your browser.

TrustLens does not intentionally upload or store the original screenshot image as part of the standard screenshot checker.

Text extracted from a screenshot may be analyzed by TrustLens. If check history is saved, the extracted text and resulting analysis may be stored in your TrustLens history.

If a screenshot contains a URL, that extracted URL may be checked using TrustLens community intelligence and third-party threat intelligence services.

7. URL and Threat-Intelligence Checks

When you check a website or URL, TrustLens may compare it with local safety rules, confirmed TrustLens community intelligence and third-party threat-intelligence services such as PhishTank.

The URL being checked may therefore be transmitted to the relevant threat-intelligence provider so that the lookup can be performed.

Threat-intelligence providers may process request information under their own privacy practices.

8. Scam Reports

Scam reports submitted by users may be stored and reviewed by TrustLens administrators.

Reports may include information such as suspicious URLs, email addresses, phone numbers, messages, stores, payment requests or descriptions provided by the reporting user.

A user-submitted report is not automatically treated as a confirmed scam. Reports may be marked pending, reviewed, confirmed or rejected after moderation.

Confirmed reports may be used as community intelligence when another user checks the same or matching threat.

9. Daily Usage Information

TrustLens may store daily check counts and plan information so that usage limits can be applied to Guest, Free, Pro, Family or other account levels.

Usage records may include your account identifier, date, number of checks used, applicable plan and remaining allowance.

10. Paid Subscriptions

When you purchase a paid TrustLens subscription, information related to that subscription may be stored so we can activate and manage your plan.

This may include your TrustLens user identifier, subscription identifier, customer identifier, plan, variant, subscription status, renewal date, end date and whether the transaction is in test or live mode.

TrustLens does not need to receive your full payment-card number when payment is processed through the payment provider's hosted checkout.

11. Lemon Squeezy

TrustLens uses Lemon Squeezy for subscription checkout and payment-related services.

Lemon Squeezy may process payment details, billing information, transaction information, tax information and other information needed to complete or manage a purchase under its own terms and privacy practices.

TrustLens may receive subscription and payment-status events from Lemon Squeezy so that your TrustLens account can be given the correct plan access.

12. Family Plans and Invitations

If a Family plan owner invites another person, TrustLens may process the invited email address, Family owner identifier, invited member identifier where available, invitation status and timestamps related to that membership.

This information is used to send the invitation, connect the invited account to the Family plan and manage whether the membership is pending, active or removed.

Family plan owners should only provide email addresses they are authorized to use for invitation purposes.

13. Transactional Email

TrustLens may send service-related emails such as Family invitation messages and other transactional communications.

TrustLens currently uses Resend for transactional email delivery. Information needed to deliver an email, such as the recipient email address and message content, may therefore be processed by Resend.

14. Service Providers

TrustLens uses third-party infrastructure and service providers to operate the application. These currently include providers for hosting, authentication, databases, email delivery, payment processing and threat intelligence.

Examples include Supabase, Vercel, Resend, Lemon Squeezy and PhishTank.

These providers may process information as necessary to provide their respective services and may operate under their own privacy notices and terms.

15. Sensitive Information

Do not submit highly sensitive credentials.

Do not submit passwords, one-time passwords, full payment-card information, cryptocurrency private keys, recovery phrases or other highly sensitive credentials to TrustLens.

If suspicious content contains sensitive information, remove or redact that information before submitting it whenever possible.

16. How We Use Information

TrustLens may use processed information to provide safety checks, save history, authenticate accounts, enforce usage limits, manage subscriptions, deliver Family invitations, moderate scam reports, improve service reliability and protect the platform from abuse.

Information may also be used where reasonably necessary for security, fraud prevention, troubleshooting and legal compliance.

17. Data Sharing

TrustLens does not need to publicly expose your private account history in order to provide the service.

Information may be shared with service providers when necessary to operate TrustLens, process payments, send emails, perform threat lookups, maintain security or comply with applicable legal requirements.

Scam-report information that is confirmed and used as community intelligence may be used to warn other TrustLens users about a matching threat.

18. Security

We use reasonable technical and organizational measures designed to protect TrustLens information and restrict unauthorized access.

However, no internet service, database, transmission method or storage system can guarantee absolute security.

19. Data Retention

TrustLens may retain account information, check history, usage records, subscription records, Family membership information and submitted scam reports for as long as reasonably necessary to provide the service, maintain security, support billing and subscription records, resolve disputes and support scam intelligence.

Different categories of information may be retained for different periods depending on their purpose and applicable requirements.

20. History and Deletion Controls

Available TrustLens features may allow users to remove individual checks or clear stored check history.

Clearing local browser storage may remove locally stored guest history and usage information from that browser.

Removing check history does not necessarily remove separate records that must be retained for subscription, security, moderation, legal or operational purposes.

21. Account Deletion Requests

If account deletion functionality is available in TrustLens, you may use that feature to request removal of your account.

Where an in-app deletion option is not available, users may contact GeekyAce Digital Hub to request account or personal-data deletion, subject to information that may need to be retained for legal, security, fraud-prevention, billing or dispute-resolution purposes.

22. Your Privacy Rights

Depending on where you live, applicable privacy laws may provide rights regarding access, correction, deletion, restriction or other handling of personal information.

Requests may be subject to identity verification and to legal exceptions that apply in the relevant jurisdiction.

23. Accuracy of Safety Results

TrustLens provides risk guidance and warning signals. A Low Risk result does not guarantee that something is safe, and a high-risk result should be independently verified where appropriate.

Threat databases, community intelligence and detection methods may be incomplete, delayed or unavailable.

24. Changes to This Policy

We may update this Privacy Policy as TrustLens develops, new features or service providers are introduced, or legal and operational requirements change.

When appropriate, the effective date displayed above will be updated.

25. Developer and Contact

GeekyAce Digital Hub

TrustLens is developed and operated by GeekyAce Digital Hub.

Visit GeekyAce Digital Hub →
This Privacy Policy describes how TrustLens currently handles information based on the features available in the service. It does not replace legal advice, and privacy requirements may vary depending on a user's jurisdiction.