Your research. Your choice.

Who we are

OLWIF is a UK-based, not-for-profit unincorporated community/voluntary group, available worldwide. We use OLWIF as the group name in this notice; the members who decide why and how personal information is used are responsible for those decisions. Charity registration is planned but has not been completed. We are not a registered charity.

Contact hello@olwif.org for privacy questions, corrections, removal requests or enquiries about earlier test-account data. This address is the group’s contact, not a separate legal entity.

Free research, without an account

The public research release does not ask you to register, connect a wallet or provide holdings. Personal accounts and account monitoring are disabled. We never request a seed phrase, private key or spending approval. Disabling test features does not delete previously stored test records.

What a check sends

The token address and chain are sent from this site’s server to enabled public-data providers. Creator-history, wallet-watch and investigation requests also send relevant public wallet addresses and transaction signatures to supported blockchain providers. Optional web search sends the exact public token address to Tavily. A normal report can send up to four public-page URLs to Jina Reader; a separate social-research request can send up to six. Directly linked public repository identifiers may be sent to GitHub.

We do not forward your browser history, browser cookies, wallet credentials or private account sessions to these providers. Each provider processes requests under its own policies. Opening an external link takes you to that third party. Do not submit personal documents or secret information. A public blockchain address or social profile can sometimes be linked to a person.

Public profiles and people

Social research organises limited public-page observations, linked profiles, dated activity and explicitly stated project roles. A claimed role or linked account is not verified identity, ownership, endorsement or proof of wrongdoing. This feature does not access private groups or signed-in feeds. It does not establish a complete social history or an authentic audience.

Additional social research stays in the current page’s memory unless you download it. It does not rewrite the saved report. Downloads are stored wherever your browser saves files.

Wallet research sessions

Opening a visible creator-wallet section requests a current snapshot. Further minute-by-minute updates begin only when you select Start watching, for up to 20 minutes. Stopping, hiding or leaving the page stops those updates. The separate investigation page lets you request bounded earlier history and connected-wallet checks.

Session results use browser memory and short-lived server caches. They are not a permanent, complete wallet index. These features do not send email, desktop or closed-browser alerts. Matches to earlier warnings use existing visible reports, not a verified personal blacklist.

What is stored and who can see it

The database stores evidence reports, timestamps, source links and visibility settings. New reports store selected factual observations, retrieval status and links, not copied page excerpts, project descriptions or full trade feeds. Buyer behaviour and time windows are derived from transient trade samples. Older saved reports are served through the same narrow evidence view; their stored originals remain subject to retention review. Reports save the exact token address rather than the original pasted URL.

Visible reports are accessible to anyone who can access the application, including anonymous visitors when the application is public. During owner-only testing, the hosting access restriction also applies. Hiding a report removes it from public display but retains it for owner restoration.

Retention and removal

We review saved reports at 90 days from creation, or earlier if an accuracy, privacy or source-rights concern arises. We remove reports when their information is no longer needed, cannot be supported, or must be removed under an applicable obligation. A report may be retained longer only where it remains necessary for dated research comparisons, a documented dispute or a legal obligation; the reason and next review are recorded privately and reviewed monthly. These are review criteria, not a guarantee that a report expires on day 90.

Review and deletion are manual. There is no automatic report-deletion schedule. Hidden reports remain stored and follow the same review criteria. Permanent removal clears the active report and linked legacy account references; it cannot be undone through the website. Nothing is automatically deleted to create storage space.

Social and watch results held only in the page last for that page/session; short-lived server caches expire separately. Downloaded copies remain with whoever saved them. Minimal request correspondence and the outcome are normally kept for 12 months after closure, then reviewed and removed unless a documented dispute or legal duty requires longer retention.

Removing information from OLWIF cannot change a blockchain or another website. Hosting-provider logs and backups are managed separately under the hosting agreement and applicable legal obligations. Their retention depends on service operation, security, recovery and legal needs; we do not claim a fixed deletion deadline for those systems. Requests concerning hosting copies are passed to the provider when appropriate. Removed information must be kept out of use and removals reapplied before any older backup is restored.

Ask for a correction, removal or review

Email hello@olwif.org with the report link, the information concerned, your concern and any supporting source links. You do not need an account or a particular form of words. Do not send keys, seed phrases or identity documents unless we specifically request proportionate information needed to confirm your identity.

We respond without undue delay, normally within one calendar month. If a permitted extension is needed because requests are complex or numerous, we explain the reason within that first month. We may hide a disputed report while reviewing it. Rights to access, correction, erasure, restriction or objection depend on the circumstances; if we cannot fulfil a request, we explain the reason and your complaint options. You can complain to the Information Commissioner’s Office.

Owner access and service operation

The protected owner area uses ChatGPT sign-in through the hosting service. OLWIF stores a stable owner identifier and uses a configured owner email for initial authorisation; it does not receive your ChatGPT password. API credentials stay on the server, outside public reports.

OLWIF does not use advertising trackers. Optional, consent-based usage statistics are explained in the visitor-statistics section below. Hosting and owner authentication can use necessary cookies and infrastructure logs. Shared request counters limit provider use. The public research routes do not build an IP-based visitor profile. Research is on demand, not a continuous background service.

Why we use this information

We rely on legitimate interests to operate and protect OLWIF, organise proportionate public-source token research, and handle enquiries, corrections and complaints, where those interests are not overridden by people’s rights. We minimise copied material, distinguish observations from allegations, and offer correction and removal review. Public availability does not remove privacy obligations. You can object to this processing using the contact above.

We rely on legal obligation where processing is needed to meet an applicable legal duty, including data-rights requirements. Optional visitor statistics rely on your consent. You can refuse or withdraw consent without losing access to research; see visitor statistics and controls. We do not use research findings to make decisions about anyone’s eligibility for services.

Hosting, recipients and international processing

OpenAI provides the site’s hosting and owner sign-in; Cloudflare infrastructure supports delivery and storage. OpenAI processes site-hosted data on our behalf under the applicable Sites data-processing agreement, using its listed subprocessors. Hosting is not restricted to the UK. The Sites agreement describes transfer safeguards, including standard contractual clauses and the UK Addendum where applicable; these documents explain how to obtain information about the safeguards.

Public-data providers receive the query information described above. Our email provider, Proton, processes correspondence sent to hello@olwif.org. Providers may process information internationally under their applicable privacy and transfer arrangements. Provider disclosures are linked in the research-provider section of our terms; see also Proton’s privacy policy. We may disclose limited information where legally required or necessary to address abuse or a rights request.

Manual recovery copies

The owner can download saved report evidence, the latest website drafts, controls for reference and a removal register. Recovery copies exclude sign-in records, account records and server credentials, but can contain public wallet addresses, named roles and hidden reports. Keep them in restricted storage and replace or delete them within 30 days. This is a manual policy, not automatic deletion of files on the owner’s device.

Restoration adds eligible missing reports hidden and website content as unpublished drafts. It does not replace existing content, apply controls or restore owner identities. Imported removals hide matching reports and block republication and must be checked against the private removal log. Recovery needs a functioning site, database and owner access; it is separate from hosting disaster recovery.

Website editing and corrections

The owner can save website drafts, publish changes and restore previous content as a new draft. Drafts and version history are restricted to the owner; published wording and editorial corrections are visible to people who can access the relevant page. Up to 30 saved versions are retained per page, with bounded storage. Website wording is reviewed when it becomes inaccurate or unnecessary; it is separate from the 90-day review of research reports.

Published corrections are labelled and dated separately from collected evidence. Hiding a report hides its correction; permanently removing a report also removes its editorial drafts and history from the active database. Private request correspondence should not be entered into public notes. The owner may choose externally hosted images: your browser then requests those images from that host, without a referrer header from OLWIF. External links and image hosts have their own policies.