Kredible
New case

Kredibleprivacy policy

It needs to know which business you mean, and nothing about you.

Effective 9 October 2026

No accountNo trackingHistory stays in your browser

Kredible reads the public reviews of a business on Google Maps and tells you whether its rating looks earned. Here is everything it handles, and what happens to each piece.

  1. What you send us

    The link you paste and the depth you pick. That is all. There is no account, so there is no name, email or password to give.

    The link is cleaned in your browser before it is sent: a Google Maps link carries the map position you were looking at and tracking parameters beside the place itself, and only the place is kept. The server cleans it again, in case anything else sends it.

  2. Your case history

    The list of reports you have run or opened lives only in this browser’s storage. The server has no list of who looked at what.

    To show the list, your browser sends the reports’ ids in the body of a request, never in the address, so they do not end up in anyone’s access logs. It gets back their summaries. The log notes only that a lookup happened. Clear the list any time under Case files; it never follows you to another device.

  3. Reports belong to places, not people

    There is one report per business, shared by everyone who asks about it within a day. A report records which place it is about and when it was made, and never who asked for it.

    • Unlisted. A report is reachable only by its link, which is 96 random bits. There is no public list or search, and every report tells search engines not to index it.
    • Shareable. Anyone you send a link to sees the same report you do, and nothing about you.
    • Upkeep. Whoever runs the service can list every report to maintain it. A report holds nothing about who asked for it, so there is nothing about you in that list either.
  4. What we keep about reviews

    Reviews are public, but the people who write them did not ask to be in a report, so we keep as little about them as the method needs.

    • Never stored: reviewer names, profile links and Google account ids. The reviewer crawl does not read names at all; reviewers appear in a report as numbers (“Reviewer 3”), with only the businesses they reviewed.
    • Kept for 30 days: what scoring reads: each review’s stars, time and text, the reviewer’s review count and Local Guide badge, and whether it has photos or an owner reply. This lets a report be re-scored when the method improves, and a later look at the same place fetch only newer reviews. Then it is deleted.
    • Kept with the report: the business’s name, address and rating, the findings, and a sample of review texts (the low-star ones are quoted in “In their own words”), so a shared link keeps working.
  5. Your IP address

    It is used for one thing: rate limits, so one address cannot start hundreds of investigations. Before it is counted, the address is turned into a keyed hash. The key is made when the server starts and lives only in its memory, so what the limiter holds cannot be turned back into an address. Nothing about it is written to disk, and a restart forgets it.

    The server’s log records the kind of request and whether it worked, like “GET /api/analyses/:id 200”, and not your address, the reports you open or the link you paste.

  6. Who else is involved

    • No analytics, ads, trackers or cookies. The fonts are served with the app; your browser loads nothing from anyone else.
    • Google. Our server reads the listing from Google, so Google sees our server, not you. If you follow a report’s link to Google Maps, you are on Google under its own privacy policy, and the link tells it nothing about where you came from.
    • Hosting. The service runs on a hosting provider whose network may keep standard connection logs to protect against abuse. We do not use them to follow anyone.
  7. Changes and contact

    If this policy changes, the date at the top changes with it. Questions, or a report you think should not exist: [email protected].