In accordance with GDPR & TDDDG

Privacy Policy

1. Data Controller

Edem Devlet
Leopoldstraße 35, 10317 Berlin
Email: support@trustscope.app

2. Hosting (Vercel)

This website is hosted by Vercel Inc., 340 Pine Street, Suite 701, San Francisco, CA 94104, USA. Servers are located in the EU/EEA. When you visit the website, Vercel processes technically necessary connection data (IP address, timestamp, requested URL). Legal basis: Art. 6(1)(f) GDPR (legitimate interest in stable operation). More information: vercel.com/legal/privacy-policy.

3. Vercel Web Analytics

We use Vercel Web Analytics for anonymised analysis of website usage. This tool sets no cookies, collects no personal data, and creates no individual user profiles. Only aggregated, non-traceable usage statistics are recorded (e.g. pages visited, country of origin). Consent under Art. 6(1)(a) GDPR is therefore not required. More information: vercel.com/docs/analytics/privacy-policy.

4. Firebase Analytics (Google)

If you have given consent via our consent banner, we use Google Analytics for Firebase, an analytics service provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland ("Google"), to analyse how this website is used (e.g. views opened, cities selected). Identifiers are stored on your device, and device and usage data (including a truncated IP address, approximate location, browser information, and event data) are transmitted to Google.

  • →Purpose: Measuring reach and improving this website.
  • →Legal basis: Your consent under Art. 6(1)(a) GDPR and § 25(1) TDDDG. Without consent, the service is not loaded and no data is collected.
  • →Third-country transfer: Data may be transferred to Google LLC servers in the USA. Google LLC is certified under the EU-U.S. Data Privacy Framework (adequacy decision under Art. 45 GDPR); standard contractual clauses (Art. 46(2)(c) GDPR) apply in addition.
  • →Retention: Event data is deleted by Google in accordance with the retention period we have configured, at the latest after 14 months. When you withdraw your consent, the analytics identifiers stored on your device are removed and no further data is collected.
  • →Withdrawal: You can withdraw your consent at any time with effect for the future via “Cookie settings” in the footer of this website (Art. 7(3) GDPR).

Google processes this data as a data processor under Art. 28 GDPR. More information: policies.google.com/privacy and firebase.google.com/support/privacy.

5. Venue Map (Google Maps)

On a venue's page we can show its location on a map embedded via the Google Maps Embed API, a service provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland ("Google"). The map is loaded only if you have enabled "Venue map (Google Maps)" in our consent banner. Until then the card shows the venue's address and a link you can follow yourself, and no connection to Google is made. Once the map is loaded, your browser connects directly to Google and transmits your IP address, browser information (user agent) and the address of the page you are on; Google may store and read identifiers (cookies or local-storage entries) on your device.

  • →Purpose: Showing where a venue is located.
  • →Legal basis: Your consent under Art. 6(1)(a) GDPR and § 25(1) TDDDG. The map is not required in order to use this website, so it rests on your consent alone.
  • →Recipient and role: Google receives this data as an independent controller and processes it for its own purposes. We have neither influence over nor access to that processing.
  • →Third-country transfer: Data may be transferred to Google LLC servers in the USA. Google LLC is certified under the EU-U.S. Data Privacy Framework (adequacy decision under Art. 45 GDPR); standard contractual clauses (Art. 46(2)(c) GDPR) apply in addition.
  • →Withdrawal: You can withdraw your consent at any time with effect for the future via “Cookie settings” in the footer (Art. 7(3) GDPR). The map is removed immediately and no further connection to Google is made. Identifiers Google has already stored under its own domain are outside our reach; you can remove them through your browser settings or Google’s own controls.

More information: policies.google.com/privacy and google.com/help/terms_maps.

6. Map View (OpenFreeMap) and Venue Pictures

For the interactive map view, map tiles from OpenFreeMap (openfreemap.org) are loaded. Your browser establishes a direct connection to OpenFreeMap's servers, transmitting technically necessary connection data (including your IP address). OpenFreeMap is an open-source project; map data is based on OpenStreetMap contributions (© OpenStreetMap contributors, ODbL). Legal basis: Art. 6(1)(f) GDPR (legitimate interest in providing the map function). No user profiles are created and no cookies are set.

Venue pictures. Independently of the map tiles, a venue's picture — in its card on the map, in venue lists and on the venue's page — is loaded directly from where the venue's own website publishes it. Your browser connects to that server, which receives the technically necessary connection data (in particular your IP address and browser type). No referrer is sent, so that server does not learn which of our pages you are on. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in showing what a venue looks like). We have no influence on how the operator of that server processes this data.

7. Location (Geolocation)

On the map, you can optionally have your location determined to center the map on your area. The request is made exclusively at your own initiative (clicking/tapping the locate button) via your browser's Geolocation API. The legal basis is your consent under Art. 6(1)(a) GDPR, given through your browser's permission prompt. Your position is used only locally in your browser to center the map. Only the visible map area is sent to our API, as map tile coordinates, to load the venues in that area; a search on the map additionally sends the center of the visible area, rounded to about a kilometer, to list nearby results first. Your exact location coordinates are never stored or shared by us, and no movement profile is created. You can revoke the permission at any time in your browser settings.

Country detection. Independently of the above, the site opens on the country you are in, so that the rankings and search results shown are the ones that concern you. This does not use the Geolocation API and asks you for nothing: the country is derived from the IP address that our hosting provider (Vercel) already receives with your request, and nothing finer than the country is read — no city, no coordinates. The IP address is not logged by us, is not passed to any third-party geolocation service, and leaves no record. Nothing is written to your device in the process. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in showing you the relevant part of the site); § 25 TDDDG does not apply, because the IP address is transmitted with your request rather than read from your device. You can override the detected country at any time using the country selector in the footer. Only a country you select yourself is stored on your device (local storage, until you change or clear it) — a merely detected country never is.

8. Emails to Account Holders (Mailjet) and Partnership Enquiries (Brevo)

We - Edem Devlet, who runs TrustScope (section 1) - send two kinds of email to your account's email address (section 11). There is no newsletter that can be subscribed to without an account.

  • →Notices about your account and contract, such as the contract confirmation after you buy a plan, the confirmation of a cancellation or a withdrawal (section 12), or a request for your consent to changed terms or prices. Purpose: performance of the contract; legal basis: Art. 6(1)(b) GDPR, and Art. 6(1)(c) GDPR for the confirmations the law requires. They contain no advertising, which is why you cannot unsubscribe from them.
  • →TrustScope news - new features, improvements and offers for our plans, at most 10 times per month - but only if you have consented: when signing in, or under “Email settings” in the account menu. The box for it is never pre-ticked, and without consent you can use everything just the same. Legal basis: your consent, Art. 6(1)(a) GDPR and § 7(2) no. 2 UWG. After you consent, we send a confirmation to your address.
  • →Withdrawal: You can withdraw your consent at any time with effect for the future (Art. 7(3) GDPR) - under “Email settings” in the account menu, with the unsubscribe link every such email contains (no sign-in needed), with your email program’s unsubscribe function, or by emailing support@trustscope.app. This does not affect the lawfulness of processing before the withdrawal.

No tracking. Our emails contain no tracking pixels and no redirected links; we do not analyse whether or when you open an email or click a link in it. The unsubscribe link carries only a random key of your account, nothing about you. If you open it, our server handles the request like any other (section 16) without logging the key; only the unsubscription itself is stored. You do not agree to changed terms through a link in the email but signed in on the website - the email takes you there.

What we keep as proof. Which version of our terms you accepted and when; when you consented to news emails or withdrew that consent, and under which version of the consent text; in each case by which route (such as the website, the extension or an unsubscribe link) and for which email address; and when we sent you a notice of changed terms. No IP address, no device data. We also keep a record of which news we sent and when (content and time, no list of recipients).

  • →Purpose: to be able to show that you consented (Art. 7(1) GDPR), that a contract was concluded or changed on particular terms, and that we notified you of a change in time.
  • →Legal basis: Art. 6(1)(c) GDPR in conjunction with Art. 7(1) GDPR for the proof of consent; otherwise Art. 6(1)(f) GDPR - our legitimate interest in being able to prove the contract and the notices, and to defend against claims.
  • →Retention: for as long as your account exists. If it is deleted, we keep this proof - and only this - until the end of the regular limitation period (three years from the end of the year in which the account was deleted, §§ 195, 199 BGB; Art. 17(3)(e) GDPR); it is then deleted automatically.
  • →Language: so that notices reach you in a language you read, we store whether you last used the website or the extension in German or in English.

Sending. We send the emails through Mailjet SAS, Paris, France, which acts for us as a processor under Art. 28 GDPR and receives your email address and the email's content for that purpose. Mailjet processes the data in data centres in the EU and keeps sending logs (recipient, time, delivery status) for a limited time under its terms. Where Mailjet's sub-processors process data outside the EU/EEA, this relies on the EU standard contractual clauses (Art. 46(2)(c) GDPR). More information: mailjet.com/legal/privacy-policy.

Enquiries through the partnership form. If you write to us through the form on the “Partnerships” page, we send your name, your company (optional), your email address and your message through Brevo (Sendinblue SAS, 106 boulevard Haussmann, 75008 Paris, France; a processor under Art. 28 GDPR, processing in the EU) as an email to our mailbox, in order to answer your enquiry. Legal basis: Art. 6(1)(b) GDPR where it concerns steps towards a contract, otherwise Art. 6(1)(f) GDPR (our legitimate interest in answering enquiries). We delete the enquiry once it is dealt with, unless a statutory retention duty applies (for example for business letters, § 257 HGB). More information: brevo.com/legal/privacypolicy.

9. Support the Project (Buy Me a Coffee) and What People Say About TrustScope

This website contains a button linking to buymeacoffee.com. When you click the button, you are redirected to the external platform. Their privacy policy can be found at buymeacoffee.com/privacy-policy. We do not receive any personal data from the redirect itself.

Supporters. On the home page and in the browser extension we thank the people who have supported TrustScope through Buy Me a Coffee. To do so, our server reads the public supporter list of our page on buymeacoffee.com - the name, profile picture, amount and date of every support marked public there; anyone not shown publicly there is not shown here either - and we display the name, profile picture and amount. Where the name given is an email address, we display no name. Our server fetches the profile pictures from Buy Me a Coffee and serves them itself; your browser makes no connection to Buy Me a Coffee for them. We do not keep the list in a database; our hosting provider (section 2) caches it for up to a little over a day, and the profile pictures for up to two weeks. Legal basis: Art. 6(1)(f) GDPR - our legitimate interest in visibly acknowledging support; supporters chose to be shown publicly on Buy Me a Coffee themselves. If you would rather not appear here, set your support to private on Buy Me a Coffee or write to us (section 17).

What people say about TrustScope. On the “About” page we show what people have written about TrustScope - praise and criticism alike, verbatim and unedited: public comments on Reddit under the posts that introduced TrustScope, with the username, profile picture, subreddit and a link to the comment, and three messages that reached us directly via Telegram or Reddit, with the sender's name or username and, where there is one, profile picture. The legal basis is Art. 6(1)(f) GDPR for the public comments - our legitimate interest in showing feedback on our service in a way that can be checked; the comments were written in public - and the senders' consent for the direct messages (Art. 6(1)(a) GDPR), which they can withdraw at any time. The profile pictures are loaded directly from Reddit's servers, which gives Reddit, Inc. (USA) your IP address and browser information, but no referrer. The legal basis for that is also Art. 6(1)(f) GDPR (showing the posts as they appeared); by its own account, Reddit, Inc. is certified under the EU-U.S. Data Privacy Framework (Art. 45 GDPR). If you would like us to remove your post, write to us (section 17).

10. Booking Links for Accommodation (Stay22)

For hotels and other accommodation, the map and the venue's page show a "Book now" button marked as an ad. It is an affiliate link of our partner Stay22 Technologies Inc. (Québec, Canada; "Stay22"): only when you click it does your browser open a Stay22 page, which forwards you to a booking site such as Booking.com, Hotels.com or Expedia. The link carries only details of the accommodation (name and coordinates), the page language, where the link sits (map or venue page) and our partner ID — nothing about you; no referrer is sent. Until you click, nothing is loaded from Stay22 and nothing is stored on your device.

After the click, Stay22 and the booking site process your connection data (in particular IP address and browser information) and may set cookies to attribute a booking to our link. They do so under their own responsibility; we have no influence on this processing. If a booking is made, Stay22 pays us a commission; we receive no information about you in the process. If you have consented to Firebase Analytics (section 4), we record the click as an event. The commission has no influence on a venue's trust score. More information: stay22.com/privacy.

11. User Account (Sign in with Google)

Everything on this website can be used without an account. An account is needed only for the AI summary, which an AI writes from a venue's reviews and which is free, and for the AI aspect radar and Insights, which the paid plans include and the free plan reveals for one venue a day (see section 12). The only way to create an account is Sign in with Google, a service of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland ("Google").

Google's sign-in script (Google Identity Services, from accounts.google.com) is loaded only when you open the sign-in window; a visitor who never opens it makes no connection to Google for it. Once it is loaded, your browser connects directly to Google and transmits your IP address and browser information, and Google may read its own cookies in order to show you the Google accounts you are signed in to. This is part of the sign-in you asked for (§ 25(2) no. 2 TDDDG).

What we receive and store. When you confirm the sign-in, Google sends us a signed confirmation of your identity. From it we store: Google's permanent identifier for your account, your email address (Google must have verified it, or sign-in is refused), your name and the web address of your profile picture, plus when the account was created and when you last signed in. Name, email address and picture are refreshed from Google at every sign-in. We receive neither your Google password nor any access to your Google account or its contents. If you have no account yet, the confirmation is first only checked against our accounts: nothing from it is stored until you accept our terms in the next step, and if you decline, no account is created. In addition, for each AI summary you ask us to write - including one asked for with an AI aspect radar you request, because the venue's was missing or more than 21 days old - and each AI aspect radar you reveal or request, we store the venue, when, which of the two it was and whether it was delivered - for an AI aspect radar, whether it counted against your allowance. This is how the free plan's daily reveal and a paid plan's allowance are counted and the technical limits on writing summaries are applied, and how we know which AI aspect radars, and so which venues' Insights, you may see. We store the same - the venue, when and whether it was delivered - for each AI aspect radar that “Compare nearby” has prepared, free of charge, for one of the two venues nearest to a venue whose Insights you open: under your account, so that a technical limit on these radars can be applied; it counts against no plan and opens nothing to you. Reading an AI summary, or following one that someone else asked for, is not recorded against your account. By creating the account you accept our terms; which version you accepted and when, whether you consented to news emails, and what we send you by email is described in section 8.

Your session. After you sign in, our server issues a session token that is stored in your browser's local storage and is valid for 30 days; signing out deletes it. This storage is strictly necessary for the account you asked for (§ 25(2) no. 2 TDDDG). While you are signed in, your profile picture is shown in the header and is loaded directly from Google's servers; no referrer is sent.

  • →Purpose: Providing your account, the AI summary, the AI aspect radar and Insights, counting the free plan’s daily reveal and a paid plan’s allowance, applying the technical limits on writing AI summaries and on the AI aspect radars “Compare nearby” prepares, and notices about your account to your email address (section 8).
  • →Legal basis: Art. 6(1)(b) GDPR - performance of the contract for using the account (the free plan included). Providing these details is necessary to have an account; without one you can use everything on this website except the AI summary, the AI aspect radar and Insights.
  • →Where it is stored: on our own service at api.trustscope.app, on servers in Germany (see section 16). For the sign-in process itself, Google acts as an independent controller.
  • →Third-country transfer: When the sign-in script or your profile picture is loaded, data may be transferred to Google LLC servers in the USA. Google LLC is certified under the EU-U.S. Data Privacy Framework (adequacy decision under Art. 45 GDPR); standard contractual clauses (Art. 46(2)(c) GDPR) apply in addition.
  • →Retention: For as long as your account exists. You can have your account deleted at any time by emailing support@trustscope.app; we then delete the account data, and the record of the AI summaries and AI aspect radars you requested or revealed is kept only without any link to you. The proof of your acceptances and consents is kept for a limited time after that (section 8). Payment records we are legally required to keep are covered in section 12; cancellation and withdrawal statements are kept until their period runs out (also section 12).
  • →If you have consented to Firebase Analytics (section 4), we record a sign-in as an event - without your name, email address or account identifier - and, when you click the AI summary’s button, what it did (sign in, have a summary written or try again) and whether the venue had been analysed yet, nothing of the summary itself.

More information: policies.google.com/privacy.

12. Paid Plans and Payment (Link / Stripe)

The AI summary is free for every signed-in user, and the free plan reveals the AI aspect radar and Insights of one venue a day; the Pro and Max plans are paid subscriptions that open the AI aspect radar and Insights on every analysed venue (section 15), with a monthly allowance of new AI aspect radars and a daily maximum. You buy paid plans from us. Payment is handled by Link, a service of Stripe: Sold through Link, LLC ("Link") acts for us as merchant of record, and the payments are processed by companies of the Stripe group ("Stripe"). When you choose a plan, you are forwarded to a payment page operated by Stripe (Stripe Checkout); to change, update or cancel your plan, you are forwarded to Stripe's customer portal, or you can use your Link account at link.com. Link sends your receipts and invoices and answers questions about payments and refunds. No Stripe script is embedded in this website - nothing is loaded from Stripe until you choose a plan.

What we pass to Stripe: your email address, your name (if Google provided one) and our internal account number, so that the payment can be assigned to your account. Whatever you enter on Stripe's page - card or other payment details, billing address - goes directly to Stripe; we never see or store your full payment details. What we receive from Stripe and store: Stripe's identifiers for you as a customer and for your subscription, the plan, the billing interval, the subscription's start and status (e.g. active or cancelled), the date its billing periods count from, the end of the current billing period, and whether the subscription is set to end then. We also note when we sent you the contract confirmation. If a payment for your subscription is refunded in full or reversed through your bank or card issuer (a chargeback), Stripe reports that too, and we note on your subscription which of the two happened and when.

  • →Purpose: Processing payments, managing your subscription, and unlocking what your plan includes.
  • →Legal basis: Art. 6(1)(b) GDPR (performance of the contract); keeping accounting records under Art. 6(1)(c) GDPR in conjunction with § 147 AO and § 257 HGB; the note on refunds and chargebacks under Art. 6(1)(f) GDPR (see the next point).
  • →Refunds and chargebacks: When a payment for your subscription is refunded in full or charged back, your plan ends at once, and the AI aspect radars you started during the period that payment covered are no longer shown to you, nor are those venues’ Insights (section 6 of our Terms of Service); your AI summaries are not affected. We receive an internal notice of this by email - with your account number, the subscription’s identifier and start, the period concerned, the number of AI aspect radars voided, whether it was a refund or a chargeback and whether it fell within the withdrawal period - and review the case personally. Only if a payment was taken back without a legal ground may we decide not to sell your account a new plan for up to 12 months; we note that decision on your account with its end date and our reasons, and tell you about it. A refund or chargeback to which there was a legal right, for example after a withdrawal, never leads to this. No automated decision is made. Purpose: preventing a plan from being bought, its AI aspect radars used up and the payment then taken back without a legal ground - every AI aspect radar costs us money that a refund does not bring back. Legal basis: our legitimate interest in preventing this abuse (Art. 6(1)(f) GDPR). The note on the refund or chargeback, and any block, are kept with your account and subscription data and deleted with your account; a block lasts 12 months at most. You can object to this processing on grounds relating to your particular situation (Art. 21 GDPR).
  • →Role: Link as merchant of record and Stripe as payment provider are independent controllers for their processing when you buy. They process your purchase and payment data for their own purposes - payment, invoices, taxes, refunds, customer support, fraud prevention and their own legal obligations (e.g. anti-money-laundering checks) - under their own privacy policies. For those purposes Stripe also sets its own cookies on its payment pages, and Link may offer to save your payment details in a Link account. From them we receive only the information listed above.
  • →Third-country transfer: Data may be transferred to Stripe, Inc. and Sold through Link, LLC in the USA. Stripe, Inc. is certified under the EU-U.S. Data Privacy Framework (adequacy decision under Art. 45 GDPR); Stripe also uses standard contractual clauses (Art. 46(2)(c) GDPR). Details are in the privacy policies of Link and Stripe.
  • →Retention: Subscription data in our database is kept for as long as your account exists. Invoices to you are issued and kept by Link. Our own accounting records of the payouts and fees Stripe reports to us are kept for the periods required by German tax and commercial law (up to 10 years), even after the account is deleted.
  • →Cancellation: You can cancel at any time via “Cancel contracts here” (without signing in, see below), via “Manage subscription” in the account menu or in your Link account at link.com; the plan stays active until the end of the period already paid for. If you ask Link to delete your data, Link also cancels the subscriptions paid for through Link, and your TrustScope account returns to the free plan.
  • →If you have consented to Firebase Analytics (section 4), we record a click on a plan as an event - only the plan and the billing interval, nothing about you.
  • →If you have consented to Firebase Analytics (section 4), we also record when a venue page shows you Insights - whether they were locked or open for you, which shows whether you are on a paid plan or revealed the venue, and whether a current AI aspect radar of the venue was available - and which of their buttons and links, and of the AI aspect radar’s, you use, for instance that you revealed a venue, asked for its AI aspect radar or opened a nearby venue from the comparison.

Contract confirmation. After you buy a plan, we send a contract confirmation with our Terms of Service as a PDF and the withdrawal notice to your account's email address, and note when it was sent. Legal basis: Art. 6(1)(c) GDPR in conjunction with § 312f(2) BGB.

Cancellation and withdrawal on our website. When you cancel through “Cancel contracts here” or withdraw through “Withdraw from contract”, we store your statement: whether it is a cancellation or a withdrawal, the date and time we received it, your name, the email address you gave, the contract you named with any subscription or invoice number you added, for a cancellation its type, any reason you gave and the end date you asked for, whether you were signed in, which subscriptions and accounts we could match it to, what we then did (for instance set the plan to end with the billing period, or started the refund), the resulting end of the contract, when we sent you the confirmation, and when, if at all, we reported the statement to our own mailbox. You can cancel without signing in; we match the cancellation to your account by the email address you give, and the page answers the same whether or not an account exists for that address. We send the confirmation at once to the address you gave and to the address of every account whose plan the statement reached; if a withdrawal repeats one already refunded or still under review, it goes only to your account's address. Statements we have to handle by hand are forwarded by email to our own mailbox.

  • →Purpose: receiving and carrying out your cancellation or withdrawal, confirming its receipt to you, and being able to prove what you declared and when.
  • →Legal basis: Art. 6(1)(c) GDPR in conjunction with § 312k and § 356a BGB (the cancellation button, the withdrawal function and the confirmation of receipt); Art. 6(1)(b) GDPR for carrying it out in your contract; Art. 6(1)(f) GDPR for keeping it as proof - our legitimate interest in being able to show what was declared and in defending against claims.
  • →Recipients: Mailjet sends the confirmations (section 8); Stripe records the cancellation in your subscription, noted with your statement’s identifier, or carries out the refund.
  • →Retention: until the end of the third year after the year of receipt (the regular limitation period, §§ 195 and 199 BGB); the statement is then deleted automatically. If your account is deleted before then, the statement is kept until then, with the name and email address you gave; it then refers to the deleted account by its identifier at most.
  • →Protection against abuse: how often statements can be sent from one connection - or, when you are signed in, from your account - is limited; for that, the IP address or the account number is only counted briefly in memory and not stored. If more than five statements arrive for one email address within 24 hours, we send that address no further confirmations that change nothing about a contract (such as “no plan found”) or that repeat a statement about the same plan from the last 24 hours - the first confirmation about a plan already cancelled still goes out; spellings of the same address count together (upper and lower case, an addition after “+”, and for Gmail also dots). If more than 50 cancellations we could not match to a plan arrive within an hour, we send no confirmation of the further ones to addresses that hold no plan of their own. The confirmation of a cancellation we have entered, and that of a withdrawal that does not repeat an earlier one, always go out. Confirmations held back are reported to our mailbox so that we can check them by hand; if a confirmation could not be sent, we try again for up to seven days - but not its copy to an account’s address where that differs from the address you gave.

More information: link.com/privacy and stripe.com/privacy.

13. Cookies and Local Storage

The browser's local storage (localStorage / sessionStorage) is used for technical functions: your language selection, your consent decision, a country you chose (section 7), once you sign in your session token (section 11), whether you put off the request to accept changed terms for 14 days, until the tab is closed the wait before an AI summary or AI aspect radar that could not be made can be requested again, and for one day the totals the home page shows. Your browser also remembers, so you can pick up where you left off: the last five venue pages you opened (name, city, category, rating, trust score, image and when you viewed it) - for “Continue from where you stopped” on the home page -, your last three search terms, as suggestions in the search box, the two categories you looked at last, which the home page's rankings start with, and, for up to 100 venues you compare (Insights, section 15), the identifier and name of the venue you picked to compare each one with, whether you last viewed it or the venues nearby, and when you last changed this. These entries stay on your device and are never sent to us or to anyone else (except the identifier of the venue you picked, which reaches us only as part of your own requests for the comparison and for its AI aspect radar - read while the comparison shows the venue without one, and asked for when you click “Analyse”); you can delete them at any time by clearing the site data for trustscope.app in your browser. Consent under § 25(2) no. 2 TDDDG is not required for these storage operations, which the features of the site you use need. Only if you have given consent via the consent banner does Firebase Analytics additionally store identifiers (cookies or local-storage entries) to recognise your browser (see section 4), and the embedded Google map stores and reads identifiers under Google's own domain once you enable it (see section 5). Google's sign-in window and Stripe's payment pages use cookies under their own domains only once you open them (see sections 11 and 12). You can change your decision at any time via “Cookie settings” in the footer.

14. Review Analysis - Data from Google Maps (Art. 14 GDPR)

For the review analysis behind our trust scores, we process reviews published publicly on Google Maps. Because that data reaches us from Google rather than from the people who wrote the reviews, Art. 14 GDPR applies and this section is the notice it requires.

What is processed: for the review, its star rating, date, text, number of “helpful” votes, attached photos (count and links) and, where Google shows them, individual ratings (such as for food or service) and further details of the visit (such as order type or price per person), whether the owner replied to it (only yes or no, never the reply itself) and the language it is written in; for its author, their name, the link to their Google profile, their Local Guide level, their account's public review and photo totals, and the link to their profile picture, from which we tell whether they use an uploaded picture rather than the default avatar. Source: the publicly visible reviews Google Maps serves for a venue - never a private or purchased source. Scope: the reviews from the last 12 months, never fewer than the 500 most recent (or all of them, if the venue has fewer) and never more than 2,000 per venue, and only for venues with at least 50 reviews.

Retention: the collected reviews and the details of their authors are deleted once the analysis has been computed. What remains is Google's own review identifiers plus aggregate numbers (such as how many of the reviews the owner replied to, the share of each language, tallies of the visit details, and how the rating and each aspect changed over time) - no review text, no names, no profile links, no profile pictures - and texts that an AI model wrote in its own words: for an AI summary, the summary and the tips; for an AI aspect radar, short texts on the aspects (section 16). Those identifiers are pseudonymous rather than anonymous, since they can be resolved against the live Google Maps page, so we treat them as personal data.

Reviews collected for a venue that is not analysed - for instance because it stays below the 50-review threshold, or because its analysis fails - are deleted by a daily job once they are more than 7 days old, those of a failed analysis as soon as it is given up. An author record is removed once no collected review refers to it.

Legal basis: Art. 6(1)(f) GDPR - our legitimate interest, and that of consumers and of honest businesses, in making review manipulation visible. A documented balancing test underlies this; see also section 15. The data is not sold. It is passed on only when a signed-in user requests an AI summary or an AI aspect radar of a venue, or when “Compare nearby” needs an AI aspect radar for one of the two venues nearest to a venue whose Insights a signed-in user opens, and then to AI providers: for an AI summary, the star rating and text of up to 50 of that venue's reviews - the most credible of up to 500 of its latest reviews that contain text - go to OpenRouter in the USA, which passes them on to Crusoe; for an AI aspect radar, those of up to 100 of its reviews - the most credible of the same up to 500, chosen as section 16 describes - go to TypeSafe in the USA, and those of up to 50 of these to OpenRouter as well, and, when a signed-in user requests it for a venue whose AI summary is missing or more than 21 days old, also what an AI summary sends, if a new one is written with it - never the author's name, profile link, profile picture or any other detail about the author; see section 16.

Notifying the authors individually is impossible: Google Maps offers no way to write to them, and there are millions of reviews. We hold names and profile links only as long as described above - keeping them longer just to be able to notify someone would mean storing more personal data than the analysis needs. We therefore rely on the exemption in Art. 14(5)(b) GDPR, with this publicly accessible notice as the alternative measure that provision requires.

15. Venue Trust Scores (Profiling) and Venue Details

A trust score is computed for a venue. Where that venue is a company, no personal data is involved. Where the venue is a natural person - a sole trader, or an individual professional such as a doctor or a lawyer - the score constitutes profiling within the meaning of Art. 4(4) GDPR, and we treat it accordingly.

Legal basis: Art. 6(1)(f) GDPR. The balance is supported by the fact that the score summarises the venue's own publicly visible reviews and introduces no new fact about anyone, and that each of the score's metrics can be opened to show the reviews behind it.

No automated decision within the meaning of Art. 22 GDPR is made. Nothing is granted, refused or decided on the basis of a score - it is information shown to a reader who draws their own conclusion. The metric labelled “unusual patterns” reports a statistical property of a set of reviews; it is not a finding that any particular review is fake, nor a statement about its author.

AI aspect radar and Insights. To signed-in users on the Pro and Max plans, and on the free plan for a venue whose AI aspect radar they revealed (section 12), a venue's page also shows its AI aspect radar - a score for each of the aspects reviewers talk about, from an AI's reading of the reviews (section 16) - and its Insights: how often its owner replies to reviews, overall and to critical ones; how its rating and its aspects have changed over time; where it stands among the analysed venues nearest to it or beside an analysed venue you pick yourself; and short texts, written by an AI, on what reviewers praise and criticise (section 16). Where the venue is a natural person, this too is profiling, and the same applies as to the score. The legal basis is Art. 6(1)(f) GDPR: the radar and Insights are derived only from the venue's public Google Maps listing and reviews and, for the comparison, from the analyses of the venues nearby or of the venue you picked. The model is instructed to put what the reviews say in its own words, without quoting a review or naming anyone. No automated decision within the meaning of Art. 22 GDPR is made on their basis. An objection under Art. 21 GDPR (section 17) withdraws them, and the venue's AI summary, together with the venue's analysis, and the venue then no longer appears in other venues' comparisons either.

Venue details. On a venue's page (and partly on the map and in lists) we show its name, address and location, category, opening hours, phone number and website, its Google rating and review count and, where available, an email address, links to social media profiles, and the image and description of the venue's website. The sources are the venue's public Google Maps listing and its own publicly accessible website. The name, address, phone number and website are also included in the page in machine-readable form for search engines. Where the venue is a natural person, this is personal data. Legal basis: Art. 6(1)(f) GDPR - the venue published these details itself so that people can find and reach it, and anyone reading about a venue here has a legitimate interest in being able to reach it too. You can object to the publication of these details as well (Art. 21 GDPR); write to us as described in section 17.

Venue owners have an unconditional route to object - see section 17 and our .

16. Where the Analysis Service Runs, and for How Long

Sections 14 and 15 describe the review analysis. It is not produced by this website: it runs on our own service at api.trustscope.app, on servers rented from Hetzner Online GmbH in Nuremberg, Germany. Everything that service stores - including the account and subscription data described in sections 11 and 12 - is stored there. With the exception of the AI summary and the AI aspect radar, described below, no data is transferred outside the EU/EEA. (The website itself is hosted separately, on Vercel - see section 2; what the payment provider does with payment data is set out in section 12.)

Hetzner acts as a processor on our behalf, and a data processing agreement under Art. 28 GDPR is in place with them. They host the data; they do not use it for their own purposes. The standard analysis involves no further processor.

AI aspect radar (TypeSafe). When an AI aspect radar of a venue is made - at the request of a signed-in user on a paid plan, by the free plan's daily reveal of a venue that has no current one (section 11), or, free of charge, for “Compare nearby” when a venue without a current one is one of the two nearest to a venue whose Insights a signed-in user opens - up to 100 of that venue's reviews are additionally classified by the language model Jev of TypeSafe AI, Inc., San Francisco, USA ("TypeSafe"), which determines which aspects of a venue each review praises or criticises: the most credible, by the per-review score the trust score is built from, among up to 500 of its latest reviews that contain text, up to 50 from each of the two periods the trends of the aspects compare (as a rule the last 90 days and the months before them, up to a year back) and, where these hold fewer, the most credible of the rest. For this we send TypeSafe the venue's category and, for each of these reviews, its star rating and text - no author name, no profile picture, no review identifier and nothing about the person who requested the radar. A review's text can nonetheless itself contain personal details, for instance a name mentioned in it. Nothing is sent to TypeSafe for an AI summary, or for a venue whose AI aspect radar nobody has requested and no comparison has needed.

  • →Legal basis: Art. 6(1)(f) GDPR - the same legitimate interest as the review analysis itself (section 14); the AI aspect radar shows a reader, aspect by aspect, what the reviews praise and criticise.
  • →Role: TypeSafe processes this data on our behalf as a processor (Art. 28 GDPR), under its Data Processing Addendum (typesafe.ai/legal/data-processing), to return the classification. TypeSafe uses sub-processors for this, mainly cloud and data-centre providers; it publishes the list at trust.typesafe.ai/subprocessors.
  • →Third-country transfer: According to TypeSafe, it processes the data in the USA; some of its sub-processors operate worldwide. The European Commission’s adequacy decision for the USA covers only companies certified under the EU-U.S. Data Privacy Framework, and TypeSafe is not certified (as of October 2026). The transfer is therefore based on the EU standard contractual clauses (Implementing Decision (EU) 2021/914, Module 2: controller to processor), which TypeSafe’s Data Processing Addendum incorporates (Art. 46(2)(c) GDPR). You can obtain a copy of the clauses, with their annexes, from us free of charge on request (section 17).
  • →At TypeSafe: Under its Data Processing Addendum, TypeSafe keeps the data for as long as necessary in light of the purpose of the processing and in compliance with applicable law, including limitation periods; it does not state a fixed period. When the contract ends, the standard contractual clauses require TypeSafe to delete the data or return it to us. Under its terms, TypeSafe does not train or fine-tune any AI model on the data it is sent. Its customer agreement also allows it to process the data to calculate charges, to prevent fraud and abuse and to comply with the law, and to derive technical usage data from it (telemetry, such as logs, statistics and metrics), which it may also use to improve its services. According to its privacy policy, TypeSafe discloses the data only to its own service providers; it reserves disclosures required by law. More information: typesafe.ai/legal/data-processing and typesafe.ai/legal/privacy-policy.
  • →With us: the review texts are deleted after the analysis, as with every analysis (section 14). The AI aspect radar is kept with the venue’s analysis; after 21 days it is no longer shown, and it is deleted at the venue’s next analysis after that or replaced by a new AI aspect radar.

AI summary (gpt-oss-120b through OpenRouter and Crusoe). The AI summary is a short written summary of the venue - at most 100 words in English, plus a German translation written with it in the same request - with up to three practical tips for a visit; it is stored with the venue's analysis and shown, on this website and in the browser extension, to every signed-in user. It is written by the language model gpt-oss-120b, an openly available model published by OpenAI and run by Crusoe (Crusoe Technologies LLC, USA). Our requests go to OpenRouter, Inc., 169 Madison Avenue, New York, NY 10016, USA ("OpenRouter"), which passes them on to Crusoe and returns the reply to us. For this we send OpenRouter the venue's category, its star distribution and, for up to 50 of its reviews - the most credible, by the per-review score the trust score is built from, among up to 500 of its latest reviews that contain text - the star rating and the text, cut to 600 characters; no aspect scores, no author name, no profile picture and no review identifier. A review's text can nonetheless itself contain personal details, for instance a name mentioned in it. The model is instructed to write in its own words, without quoting the reviews or naming anyone. In a second request with the venue's category and the same reviews, under the same instructions, the model writes the tips, in English and in German. For an AI aspect radar (above), the model also writes, in English and in German, a short text per aspect on what reviewers praise and what they criticise, under the same instructions, from a request with the venue's category, the aspect figures (each aspect's score and how many reviews mention, praise and criticise it) and, for up to 50 of the reviews Jev read - for each aspect, the most credible ones that praise it and those that criticise it - the star rating and the text, cut to 600 characters; these texts are shown, as part of Insights, to signed-in users who may see the AI aspect radar (section 15). Nothing is sent to OpenRouter for a venue for which nobody has requested an AI summary or an AI aspect radar and no comparison has needed an AI aspect radar. OpenAI, which published the model, receives no data.

  • →Legal basis: Art. 6(1)(f) GDPR - the same legitimate interest as the review analysis itself (section 14); the summary, the tips and the texts on the aspects tell a reader in a few lines what the reviews say.
  • →Role: OpenRouter processes this data on our behalf as a processor (Art. 28 GDPR), under its Data Processing Agreement (openrouter.ai/data-processing-agreement), and only to pass it on to the model and return the summary, the tips and the texts on the aspects. Crusoe runs the model for OpenRouter. For its own operation OpenRouter uses further service providers, for instance for hosting and networking; it names some of them at trust.openrouter.ai.
  • →Third-country transfer: OpenRouter processes the data in the USA; Crusoe in its own data centres, which it does not name for this service (Crusoe is based in the USA). The transfer is based on the EU standard contractual clauses (Implementing Decision (EU) 2021/914, Module 2: controller to processor) incorporated in OpenRouter’s Data Processing Agreement (Art. 46(2)(c) GDPR); we do not rely on the EU-U.S. Data Privacy Framework for it. You can obtain a copy of the clauses with their annexes from us on request, free of charge (section 17).
  • →At OpenRouter: under its terms, OpenRouter does not store requests and replies as long as prompt logging is switched off for the account - it is by default, and we do not switch it on for ours; nor do we allow OpenRouter to use the requests to improve its products - and deletes them promptly after the reply has been generated; it keeps only details about a request without its content, such as the number of tokens processed and the duration. OpenRouter does not use the data to train AI models. More information: openrouter.ai/privacy and openrouter.ai/data-processing-agreement.
  • →At Crusoe: we have every request routed only to Crusoe’s endpoint, which by OpenRouter’s classification stores no data (zero data retention) and collects no data for training. According to Crusoe’s terms, it writes the requests and replies to no disk, keeps them only temporarily in memory (cache), and does not use them for training.
  • →With us: the review texts are deleted after the analysis, as with every analysis (section 14). The summary and the tips are kept with the venue’s analysis: they are shown for 21 days, and after that for as long as the venue has gained fewer than 50 Google reviews since they were written; then they are no longer shown. A new analysis of the venue does not remove them; a new summary replaces them, and they are deleted with the venue’s analysis. The texts on the aspects are kept and deleted with the AI aspect radar (above).

Requests to api.trustscope.app reach the service through Caddy, a reverse proxy we run ourselves on the same server. Caddy keeps no access log; the error log it writes when a request fails contains neither the IP address nor the request headers. The service itself logs, for each request, the method, the address requested with its parameters (coordinates, map tile numbers and the key in an unsubscribe link masked), the status and how long it took, but neither the IP address nor the browser user agent. With your account’s ID it also logs which AI summaries and AI aspect radars your account requests (a summary requested with an AI aspect radar included), reveals or has prepared for a comparison, the fresh analyses Insights ask for (on Pro and Max on their own when a venue’s Insights open), and your sign-ins, acceptances of the terms, consents to news emails and their withdrawal (also through an unsubscribe link), checkouts, plan changes and contract confirmations, refunds and chargebacks, cancellations and withdrawals. We use these logs to find errors and detect abuse (Art. 6(1)(f) GDPR: our legitimate interest in a secure, working service). In our log database the service’s logs are kept for 14 days and then deleted; its log file on the server itself holds at most 100 MB and is overwritten continuously by size, oldest entries first, so when there is little traffic it can keep entries for longer than 14 days. This applies toapi.trustscope.app only - the connection data processed for this website is described in section 2.

Retention of a venue analysis: a stored analysis is kept for as long as the venue is publicly listed on Google Maps and no objection or erasure request has been made - that is the retention criterion under Art. 5(1)(e) GDPR. An analysis older than 21 days is regenerated from fresh data the next time someone requests it, and the previous one is replaced. What the analysis retains of the underlying reviews is set out in section 14.

17. Your Rights

Under the GDPR, you have the following rights:

  • →Right of access to stored data (Art. 15 GDPR)
  • →Right to rectification of inaccurate data (Art. 16 GDPR)
  • →Right to erasure (Art. 17 GDPR)
  • →Right to restriction of processing (Art. 18 GDPR)
  • →Right to object to processing (Art. 21 GDPR)
  • →Right to data portability (Art. 20 GDPR)
  • →Right to withdraw a given consent (Art. 7(3) GDPR)
  • →Right to lodge a complaint with the supervisory authority (Art. 77 GDPR) - in Berlin: Berliner Beauftragte für Datenschutz und Informationsfreiheit, Friedrichstr. 219, 10969 Berlin

Please send requests to: support@trustscope.app

Objection by venue owners (Art. 21 GDPR)

If you own a venue and object to its analysis, write to the address above using the subject line:

GDPR: Objection (Art. 21) - <venue name>, <Google Maps URL>

Please include the venue's Google Maps link and your relationship to it. We answer within one month (Art. 12(3) GDPR). Where an objection is upheld, the stored analysis is deleted and the venue is excluded from any future analysis - the exclusion is enforced in our database, so a later re-scrape cannot undo it, and we also stop collecting that venue's reviews. Full instructions, including the subject lines for corrections and access requests, are on our .

Last updated: October 2026