HERE TO HELP YOU LOOK CLOSER

A little help.
A clearer next step.

Beta access, source searches, and account or privacy requests. Contact the operator directly.

Your direct contact.

Sourceglow is an independent project, not a registered company. Operator and contact address:

Frans Naakka Heinäsuonraitti 65a A4 37830 Akaa Finland
TALK TO SOURCEGLOW

Let’s work through it.

Describe what happened and what you expected. Start without private documents or credentials.

sourceglow.support@gmail.com
Independent project.
No guaranteed response time.
01 / GETTING STARTED

One source. A focused question.

Sourceglow is a free Chrome extension, available from the Chrome Web Store. Add to Chrome — Free Beta

The free beta supports up to 10 active participants, each with 100 lifetime reserved search attempts across the beta. Once a search is accepted and reserved, failed, cancelled, and no-match results can count. The account panel displays your allowance; a new month does not reset it.

Beta eligibility: Free, first-come-first-served beta access for up to 10 eligible adults residing in the EEA or United States.

The website, extension, onboarding, legal documents and support use English. This beta is intended for testers comfortable reading and using English. Before Google sign-in, self-confirm age 18+, EEA or United States residence, English use and the permitted-source/Terms conditions. Do not send identification, a birth date or an address for onboarding. This acknowledgment does not verify your real age or country. Mandatory local rights remain unaffected.

You must be 18 or older. Use ordinary, publicly available, non-sensitive informational, research, educational, governmental and technical webpages and PDFs. Incidental ordinary personal information, such as a published author's name, may be present.

Do not submit sensitive personal information, private or confidential documents, or accidentally exposed personal documents. People profiling, personal-data dossiers and questions designed to investigate individuals are prohibited. Sourceglow does not automatically check age or detect prohibited content. It finds passages; you assess factual truth and source reliability.

Join through Google after acknowledging eligibility and Terms. The server enrolls accounts automatically, first-come, first-served, while fewer than 10 active seats are occupied. No invitation, manual approval or whitelist is needed. Returning members keep their seat and lifetime usage. Installation or sign-in alone does not guarantee enrollment; see beta access for distribution information.

Beta is full: if all 10 active seats are occupied, an unadmitted account cannot search. Existing members can still sign in. A Google sign-in may create an Auth/profile account even when no seat remains; there is no waitlist. You can request deletion through the contact below rather than creating repeated accounts.

  1. 1

    Open your source in Chrome.

    Choose a readable webpage or a supported text-based PDF. For a document on your computer, use Select PDF in the extension.

  2. 2

    Open Sourceglow and sign in.

    Read the beta eligibility and Terms, then check the separate acknowledgment before continuing with Google with your intended account. A valid pre-sign-in acknowledgment is bound to that account without a second acceptance step. A restored session may also require acknowledgment of the current version. This website has no sign-in form.

  3. 3

    Read the disclosure, then search.

    Enter a claim or question. Before the first search, review the data disclosure: your question and all extracted source text go to Railway; OpenAI processes text for source search and embeddings. Choosing Not now cancels that search.

  4. 4

    Read the original passage.

    Use Full passage to inspect the text, Show in page for a webpage, or Go to page for a PDF. Exact highlighting may be unavailable. Assess the source and context yourself.

Try the illustrative demo
02 / WHEN SOMETHING DOESN’T CLICK

Common questions.

Reviewing or resetting local acknowledgments
Privacy, Terms and Support links remain available in the extension. Signing out keeps this device’s account-scoped Terms and search-disclosure records. To reset local extension records, remove the extension and reinstall through the approved beta distribution when available, then sign in and review the prompts again. This does not erase the cloud account, revoke Google authorization or reset the lifetime search allowance. Your original PDFs and browser-managed history/downloads are separate.
No matching passages
Check that the intended source is selected and try a clearer question. Read any partial-coverage notice. The document may not discuss the claim, or extraction/retrieval may have missed relevant text. No match does not establish that a claim is false.
The passage won’t highlight
The source may have changed, or its layout may prevent exact navigation. Refresh and search again if appropriate. For a PDF, use the page location and read the passage manually. A PDF quote highlight can place a short quotation in the address-bar URL; consider this before copying a link.
The PDF has no readable text
Scanned/image-only PDFs have no OCR support in the current extension. Locked PDFs, unusual fonts, size limits, and processing deadlines can also prevent extraction. Use a legally accessible, public, non-sensitive text-based version. Do not bypass access restrictions or submit private documents.
Google sign-in, beta access, or recovery fails
Use your intended Google identity and check the extension’s error. You can cancel and retry sign-in; check the account before acknowledging Terms. Enrollment is automatic while capacity remains. If the beta is full, an unadmitted account cannot search. For an existing legacy email account, contact support from the relevant address for the available fallback; automatic email recovery is not guaranteed. Do not send your password or a token.
My allowance was used by a failed search
The beta counts reserved attempts, which can include failures, cancellations, and no-match results after acceptance. Requests refused before reservation are different. Logging out, reinstalling, or starting a new month does not reset the beta counter. Describe a suspected accounting error to support; do not attempt to bypass a limit or delete/recreate an account to obtain a reset.
The service is busy or unavailable
Authentication, concurrency, rate, and shared cost limits can temporarily prevent a search. Check the account/error message and avoid repeated immediate retries. The beta has no guaranteed uptime or automatic allowance restoration promise.
03 / YOUR ACCOUNT AND YOUR DATA

Account & privacy requests.

Email sourceglow.support@gmail.com to request account deletion, access/export, correction, or other privacy help. Preferably use the address associated with your account and state the request. A claimed email address alone is not sufficient proof of ownership; the operator may need a proportionate verification step.

There is no self-service cloud-account deletion button. Signing out removes this device’s session; uninstalling removes extension data according to Chrome’s behavior. Neither action deletes your backend account or guarantees removal of provider logs, backups, downloaded files, or browser history. Removing Google authorization is also a separate action.

You do not need an account to raise a privacy request about information about you in a public source. Give a minimal description and a safe public reference if available, rather than a copy of sensitive material. You may object to legitimate-interest processing, subject to the applicable legal conditions; see people mentioned in sources.

Verified deletion requires operator action covering Auth and linked profile, beta membership/lifetime usage, monthly usage, and request rows. Active searches and backend caches must also be addressed. Aggregate cost totals and justified provider log/backup retention can remain separately. The operator will explain any applicable exception instead of promising immediate deletion of every copy.

Frans Naakka handles requests manually. Verification should use an account-controlled channel and only the information needed to establish ownership. Do not send a password, token or identity-document copy as a routine first step. GDPR requests are handled without undue delay, normally within one month; any permitted extension must be explained during that initial month.

Email sourceglow.support@gmail.com for access, correction, export, deletion, restriction, objection or other privacy help, including if you have no Sourceglow account. The operator verifies identity proportionately and handles requests manually; passwords and working tokens are not requested. Cloud deletion, active work/caches and provider retention are separate checks. Applicable legal deadlines apply; there is no self-service cloud deletion button or guaranteed ordinary support response time. No guaranteed ordinary support-response time overrides legal deadlines.

Ordinary resolved support correspondence is reviewed for deletion 90 days after resolution; minimal rights-handling evidence is reviewed 90 days after completion, unless a specific legal need justifies keeping it. The operator reviews eligible cases weekly. Provider logs/backups and narrowly justified legal preservation are separate. You may complain to Finland’s Office of the Data Protection Ombudsman or another competent authority.

Read the Privacy Policy and Terms of Service. You can also request deletion if authentication created an account but beta admission was not granted.

Request account deletion
04 / A USEFUL BUG REPORT

Start with the minimum.

Send a short description with these details when available:

  • What you tried to do, what happened, and the visible error message.
  • Your extension and Chrome versions.
  • Whether the source was a webpage, online PDF, or selected local PDF.
  • A public source URL or a carefully redacted screenshot, only if appropriate.

Leave out passwords, API keys, session tokens, confidential documents, and sensitive personal information. Do not send a full private source file as a routine first step. Private documents remain outside the beta; start with a public URL or a redacted description.

Support email is handled through Gmail. The sender address, message, attachments, and mail metadata become part of that correspondence; do not include more than the operator needs to help.

Email a support request
05 / SECURITY CONCERNS

Report privately.

If you suspect account misuse, exposed credentials, or a privacy/security issue, email sourceglow.support@gmail.com with a minimal description. Do not post secrets or private source content in public issues or attach working tokens as proof. The operator can arrange an appropriate way to exchange further details if needed.

If you discover prohibited content, stop searching the affected material. Do not resend it to demonstrate the problem. If prohibited content is discovered, the operator will stop further affected processing where reasonably possible, assess necessary containment, deletion and applicable notification obligations, and handle relevant privacy or security requests. Repeated violations may lead to revocation of beta access, subject to applicable notice and statutory obligations. Instantaneous deletion from all providers, logs or backups is not promised.