LYRA

Privacy Policy

Refine your search

Last updated · August 13, 2026

1 · What Lyra is

Lyra is a privacy browser and shopping intelligence tool. Its job is to hide predatory commerce (fast fashion, dropshipping, betting, aggressive marketplaces), ads and trackers, and to give you calm, deliberate results. Lyra does not sell, recommend or process any merchandise; it only filters and surfaces information.

The official list of filtered domains is curated and served from our public endpoint at https://lyrasearch.com/v1/. You can also add your own domains to a personal local list and mark brands you respect as part of our "Clean" list (slow buy, sustainable, quality).

2 · The four ways Lyra works

Lyra is delivered in four ways, in this order. Each does the same job on a different surface, and each has its own privacy footprint.

• Apps (Android, iPhone, Mac, PC). The full Lyra browser as a native app, with filtering built in and nothing to configure. The app stores your lists and preferences locally and, when you are signed in, syncs them to your account. The mobile and desktop apps do not sell anything and do not process payments.
• DNS (Safe Mode / Private DNS). System wide filtering that cleans every app on the device, not just the browser. If you enable it, Lyra's DNS resolver processes your device's DNS lookups so it can block filtered domains. We keep only aggregate operational statistics (for example how many queries were blocked). We do not build a browsing profile from them and we do not sell or share them.
• Extension (Chrome, Safari, desktop only). Adds Lyra to a browser you already use. It hides filtered result entries on search engines and redirects direct navigation to filtered domains to a local block screen. The match happens entirely in your browser. Phone and tablet browsers do not support extensions.
• Web (lyrasearch.com). Use Lyra straight from the website, nothing to install. Search runs through Lyra and returns clean results.

3 · What data Lyra collects, and why

Most of what Lyra does happens entirely on your device. The filtering on Google, Bing, DuckDuckGo and Brave Search runs locally, so nothing about your search query or the results you saw is ever sent anywhere. The counters that show how many results were hidden or redirected are computed on your device and stay there.

Account email, to provide the service and sync across devices. When you sign in we receive your email address (and, where the provider supplies it, your display name) from the sign in provider you chose (Google, Apple, Microsoft, GitHub or Facebook). We use it to identify your account and to send you transactional email. Lyra has no email/password login.

CPF at signup (Brazil only), to bind the free trial. In Brazil, signup asks for your CPF. We use it only to make sure each person gets one free trial, and to comply with Brazilian tax rules on the web purchase. It is not used for advertising or shared for marketing.

Data you explicitly capture, to provide the service and sync across devices. Your personal block list, personal Clean list, and any purchases or shopping essentials you choose to record are stored to your account so they sync across your devices. Purchase data is only what you enter yourself (for example an item name, quantity, price, and how often you rebuy it). Lyra does not import order history from any store or read your receipts.

Anonymous crash and error telemetry, to fix bugs and outages. When Lyra hits an error, it may send an anonymous report containing a short error message, the app version, and the platform (for example android, ios, web, chrome). Before sending, we scrub the message so URLs and email addresses are removed. The report does not include your identity, IP address (beyond what our host logs for any request), browsing history, search queries, or the contents of your lists. This telemetry is on by default but you can turn it off in settings (see "Error reporting" below).

Subscription state, to give you access to what you paid for. We receive your subscription status (trial, active, expired, cancelled) and a transaction ID from the payment provider on the web. We do not store your payment card details.

What we do NOT collect, ever:

• Your browsing history or the list of sites you visit (blocking statistics are computed on your device)
• Your search queries
• The URLs of pages you visit
• Identifiable analytics or behavioral tracking
• Device fingerprinting data

Community contribution (sharing your personal block/clean lists with the Lyra community) is opt in and off by default. It has its own section below.

4 · What stays on your device

In the Apps and the Extension, Lyra stores the following only in on device storage (the app's local storage, or chrome.storage.local in the extension), never sent anywhere except as described elsewhere in this policy:

• The official block list (synced from our public endpoint)
• Your personal list of blocks and Clean validations (also synced to your account when you are signed in)
• A list version number and timestamp of last sync
• A session counter showing how many redirects and hidden results you have seen
• Pause state if you have temporarily paused Lyra
• Your chosen interface language
• Ad blocking and tracker blocking toggle preferences
• Cached display name and email of the signed in user (so the account pill renders immediately without a network request)
• A connection token (your account's license key) after you sign the extension in, so it can load the paid curated lists on your behalf; you can remove it by disconnecting in the popup

You can clear all of this at any time by removing the app or extension, or clearing its storage.

5 · What is fetched from our servers

Every few hours, and on demand when you tap Sync now, Lyra makes a standard HTTP GET request to version.json and, if a newer list exists, to domains.json and clean.json. These are static JSON files served from Cloudflare's CDN.

When you are signed in, Lyra also makes authenticated requests to /api/v1/personal to sync your block/clean lists. The request uses a session cookie (HTTP only, secure) issued by Better Auth to identify you.

Cloudflare may retain standard HTTP logs as part of its CDN operation, governed by Cloudflare's privacy policy.

6 · Permissions explained

The native Apps request only the permissions the operating system requires for the features you turn on (for example VPN/Private DNS configuration for Safe Mode). Each is requested with an explanation at the point of use.

The Chrome/Safari Extension declares the permissions below:

• declarativeNetRequest, to redirect direct navigation to filtered domains to the local block screen, and optionally to block ad and tracker requests via bundled rulesets you can toggle. The browser enforces these declaratively; the extension does not see the individual requests.
• storage, to keep the lists (official, personal, Clean) and your local preferences on your device.
• alarms, to schedule the periodic background sync of the list and the auto resume from the "pause for an hour" feature.
• tabs, to open the sign in page, to open the welcome tab on fresh install, and to read the current tab's URL so the popup can offer quick actions ("Block this site" / "Mark as Clean").
• host_permissions: <all_urls>, required so the redirect rules and ad/tracker blocking can apply to any site. Lyra does not read or modify page content beyond hiding result entries on supported search engines (Google, Bing, DuckDuckGo, Brave Search).
• webNavigation, to detect when you navigate directly to a filtered domain so Lyra can show the local block screen (Safe Mode). Lyra does not record, store, or transmit the pages you visit.
• identity, to let you connect the extension to your own paid account with one click. When you choose "Sign in" in the popup, Chrome opens the standard sign in flow for your Lyra account (via chrome.identity.launchWebAuthFlow); on success the extension receives a one time code, which it exchanges for your account's license key. That key is stored on your device (chrome.storage.local) and sent as an authorization header to lyrasearch.com so the paid, curated lists load. Lyra uses this only to authenticate your own account. It does not access any other account, and it receives no identity data beyond the email your sign in provider returns for the account you are signing into. You can disconnect at any time from the popup.

7 · Paid plan (purchased on the web)

Lyra starts with a 7 day free trial, with no card required up front. After the trial, Lyra requires a paid subscription for the filter to stay active. A days left countdown is shown on the website and in the app.

• International: US$ 5/year or US$ 25 one time (Permanent Access)
• Brazil: R$ 25/year or R$ 125 one time (Permanent Access)

Purchases are made only on the Lyra website (lyrasearch.com). The mobile apps and the browser extension do not sell anything and do not process payments; after you subscribe on the web, signing in unlocks the subscription on every surface. Payment on the web is processed by external providers:

• Paddle for international customers (USD; acts as Merchant of Record and handles global tax/VAT). Methods include card, PayPal, Apple Pay, Google Pay and others depending on your country.
• Mercado Pago for Brazilian customers (BRL via PIX, boleto or card).

The payment provider receives the data necessary to process your payment (name, email, billing address, payment method) under its own privacy policy. Lyra receives only your email, the subscription status, and a transaction ID. We do not store payment details. 14 day worldwide refund. Cancel anytime from your account page (/billing).

8 · AI assistant channel (MCP)

Lyra exposes an optional channel that lets an AI assistant use Lyra on your behalf, through the Model Context Protocol server at /mcp and the public REST API at /api/v1/*. This channel is governed by a strict two tier consent model:

• Reads (navigate, read a page, look up your own filtered lists) run under a session level consent and never prompt each time.
• Actions that reach the outside world (communicating, buying, sending a message, submitting a form, signing, routing a document) always require your express, per action authorization on screen. These are locked by design and cannot happen silently.

The channel never exposes your vault, your saved passwords, or any signing capability. It cannot read your receipts or order history. Reads never prompt; anything that could spend money or speak for you always does.

9 · Community contribution (optional)

If you enable "Contribute to the community", we send to the server only the following items, with no link to your identifier:

• Domains you added to your personal block list
• Brands you marked positively as Clean

When enough users submit the same domain, it enters a queue for human review and may be added to the official list. The same applies to Clean brands. This is a collective process that helps the Lyra community refine curation without anyone having to identify themselves. Contribution is off by default. You can enable and disable it at any time.

10 · Error reporting (anonymous, opt out)

When Lyra hits an error, it may send a small anonymous report to /api/v1/errors so we can monitor service health and fix crashes. The payload contains:

• An error type (for example pull_5xx), max 64 characters
• A short error message (for example GET /personal 500), with URLs and email addresses scrubbed before sending, max 500 characters
• The app version (for example 0.4.4), max 32 characters
• The platform (for example android, ios, web, chrome)

The error report does NOT include your email, identity, session cookie, IP address (beyond what our host logs as part of any HTTP request), browsing history, search queries, or the contents of your personal lists. This is operational telemetry only, not analytics. We cannot link an error report to a specific user. You can turn error reporting off in settings.

11 · Third parties who process data for us

We keep the list of processors short and name every one. We do not sell your personal data, and we do not share it for cross context behavioral advertising.

• Cloudflare, hosting, CDN, and our database (Cloudflare D1). Your account data (email, your lists, the purchases you capture) is stored here. Governed by Cloudflare's privacy policy.
• Resend, sends our transactional email (sign in and account notices). Receives your email address for the purpose of delivering that mail. See Resend's privacy policy.
• Paddle, payments for international customers on the web; acts as Merchant of Record and handles global tax/VAT. Receives the data needed to process your payment. See Paddle's privacy policy.
• Mercado Pago, payments for Brazilian customers on the web (PIX, boleto, card). Receives the data needed to process your payment. See Mercado Pago's privacy policy.
• TikTok pixel, a marketing pixel used only on our public marketing website (lyrasearch.com) to measure ad campaigns. It is not present in the Android app, the iOS app, the Mac or PC apps, or the browser extension, and it never sees your account data or your lists. See TikTok's privacy policy.

Your sign in provider (Google, Apple, Microsoft, GitHub or Facebook) also processes the sign in itself under its own privacy policy.

12 · Where your data is stored, and international transfers

Your account data is stored in Cloudflare's infrastructure. The block list and this site are served from Cloudflare's global CDN, which means responses to your device may originate from a Cloudflare edge node anywhere in the world. Payment and email processors named above may process the limited data they receive in their own regions. Where data crosses borders, our processors rely on standard contractual safeguards.

13 · Data retention

We keep your account data (email, your lists, and the purchases you capture) for as long as your account exists. When you delete your account, that data is removed from our servers. Anonymous error reports are retained only as long as needed for operational monitoring and are not tied to you. Aggregate DNS statistics are retained only in aggregate form. Payment and email processors retain the limited data they hold under their own policies and legal obligations (for example, tax records).

14 · Children

Lyra is not directed at children. It is intended for adults and is not directed to children under 13 (or under 16 where a higher age of digital consent applies). We do not knowingly collect information from children. If you believe a child has provided us personal data, contact us and we will delete it.

15 · Your rights and account deletion

Under data protection laws including GDPR (EU), LGPD (Brazil), CCPA (California), PIPL (China) and equivalents, you have the right to access, correct, or delete personal data we hold about you.

The personal data Lyra holds about you, if you have signed in, is:

• Email and name (collected at sign in)
• CPF, in Brazil only (collected at signup to bind the free trial)
• Your personal block list, personal Clean list and channel blocks (synced to your account)
• The purchases and shopping essentials you chose to capture (synced to your account)
• Subscription state from the payment provider

You can delete your account and all of the above at any time, from the website under Profile, Delete account. Deletion removes your data from our servers. You can also email [email protected] to exercise any right, and we will respond within 30 days.

If you enabled community contribution, you can request the removal of the domains and Clean validations you submitted, provided they have not yet been aggregated into the public consensus (after aggregation they become anonymous and inseparable).

16 · Changes to this policy

If we change this policy, the "Last updated" date at the top will change. Material changes will be announced in the app before they take effect.

17 · Who we are and contact

Lyra is operated by Icivitas Ltda (CNPJ 59.206.635/0001-92), headquartered in Brazil. Icivitas Ltda is the data controller responsible for the processing described in this policy.

Questions, complaints, or requests to access, correct or delete your data: [email protected]. We respond to privacy requests within 30 days.

18 · Affiliate links & disclosure

Lyra is associated with VT CASA LTDA (CNPJ 53.990.615/0001-79). Some shopping results in Lyra contain affiliate links: if you click and buy, we may earn a commission from the retailer, at no additional cost to you and without changing the price. This helps keep Lyra running. We participate in the Amazon Associates Program (as an Amazon Associate, we earn from qualifying purchases), Awin and Rakuten Advertising. Affiliate links do not influence our curation or the ordering of results.

When you click an affiliate link, the retailer or its affiliate network may set a cookie to attribute a possible purchase to Lyra. The commission is always paid by the retailer, never by you.