Echo

Competitor and market intelligence for the outward-opening aluminium window industry. The phone app gathers the news. This is the web half: you read what it found, decide what holds up, and turn the verified stories into a report.

Use it at attano26.github.io/Echo/window.html

What it does

Sign in with Google and it reads the backup your phone wrote to your own Drive. You get everything the phone holds: alerts, saved stories, liked and disliked, published reports, and the competitors, markets and norms you have onboarded.

Tick the stories that stand up to a fact-check, then generate a report as PDF or Word. Published stories move out of Alerts and into Published, exactly as they do on the phone.

What it deliberately does not do

It never fetches news. Fetching costs money and only the phone does it. This page reads what has already been gathered, so opening it costs nothing and it holds no API key of any kind.

How syncing works

Two files in your Drive, each with one writer:

File	Written by	Read by
echo-data.json	the phone	this page
echo-web-actions.json	this page	the phone

Because no field is written by both sides, neither can overwrite the other. This page can never destroy a news fetch your phone made while you were reading. Everything it writes is additive.

To see your data here, open the phone app, go to Settings → Storage, and press Back up. To pull your web decisions back to the phone, press Sync on that same screen.

Sign-in

You are asked for one permission: drive.file. That lets this page touch only the files it creates in your Drive and nothing else you keep there.

The consent screen appears once. After that, signing in is silent, because Google remembers the grant. Sign out forgets the token in this browser only — nothing in your Drive is deleted, and signing back in needs no prompts.

Two people using this share nothing. Each signs in as themselves, and each file lives in its owner's own Drive.

Your data

There is no server in this. Nothing passes through anyone else. Your data is in your Drive and in this browser, and nowhere else.

Clearing site data clears this browser's copy only. Your Drive file and your phone are untouched.

Reports

PDF uses your browser's own print dialogue, so choose Save as PDF in the destination list. The output matches what you see rather than a re-drawing of it.

Word downloads a document that Word and Google Docs both open normally.

Past reports stay under Reports and can be downloaded again at any time.

What it is not

It reports what was published elsewhere. It does not verify claims for you, and a story appearing here is not evidence that it is true. That is what the verify step is for. Check anything before it informs a commercial decision.

A note on this repository

It is public, and has to be: GitHub Pages serves the site from it on the free tier.

What that means in practice:

• No secrets live here. The page holds no Gemini API key — only the phone fetches news, and it pays for it. Nothing in the history has ever carried a key, a token or a password.
• No data lives here either. Your competitors, news, reports and counts are in your Google Drive. This repo is the shell that reads them after you sign in.
• The OAuth client ID in window.html is public by design. Browser OAuth client IDs are not credentials. The scope is drive.file, so the app can only ever see files it created itself — copying the ID gets someone a consent screen and nothing else.
• Commits are authored as <id>[email protected]. Commits made before 2026-09-08 carry a real address, because git records whatever identity was configured at the time.