Skip to content

Privacy Policy

How notolens collects, handles, and protects information when you use our monitoring service.

Last updated:

1. Overview and Scope

Sebastian Graef LLC, a Florida limited liability company operating as notolens (“notolens,” “we,” “us,” or “our”), provides brand monitoring software that detects potential brand conflicts across domain registrations, trademark registers, mobile app stores, and search engine ads. This Privacy Policy explains how we collect, use, disclose, and safeguard personal information when you visit our website, use our free tools, register for an account, or subscribe to our monitoring service.

notolens is a business-to-business service operated from the United States. It is offered to businesses and other organizations for business purposes, not to consumers for personal, family, or household use.

This Privacy Policy applies to personal information collected through our website, application interfaces, customer dashboards, MCP server, browser extension, and related services (collectively, the “Service”). It does not apply to third-party websites or services that may be referenced, linked, or surfaced within match records and action guides.

2. Information We Collect

We collect information in three ways: information you provide directly, information collected automatically when you use the Service, and information gathered from public sources to deliver monitoring results.

A. Information You Provide Directly

  • Account and profile details: When you create an account, we collect your name, email address, and authentication credentials. We also store account settings such as your time zone, and the IP address and browser user agent of your sign-in sessions. If you set a password, we store a salted cryptographic hash of your password. If you sign in with a code we email to you, we store a keyed hash of the code until it is used or expires. If you register or authenticate through Google or Microsoft, we receive your name, email address, and provider account identifier as permitted by your provider settings.
  • Connected AI clients: If you connect an AI client through the notolens MCP server, we issue and process authentication tokens to verify its access. We receive only the requests it makes on your behalf, such as the tools it calls and the values it passes; we do not receive your conversations with the agent or other content from the AI application.
  • Monitor configurations: When you configure a monitor, you submit the brand names, marks, domains, app listings, and other assets you designate for monitoring, any reference images, and any brand context you choose to provide, such as a description of the brand and the companies, sites and partners it works with.
  • Free tool queries: Domains, brand names, and IP addresses entered into our free tools are processed to return results, may be cached briefly, and are counted per IP address to limit abuse.
  • Billing information: When you subscribe to a paid plan, our payment processor, Stripe, collects and handles payment details such as card information, billing address, and tax identifiers. notolens stores the billing identifiers and subscription details it receives from Stripe; card details are never stored on our servers.
  • Communications: If you contact us through the contact page, through the feedback tool on our MCP server, or by email, we collect your name, email address, the topic and content of your message, and any attachments you provide by email. Messages from the contact page and the MCP feedback tool are delivered to our inbox by email. To limit abuse, we may check that the address you enter can receive mail and limit submissions per IP address or per account.
  • Takedown notes and workflow records: If you record notes, comments, or status updates within match records or takedown tracking tools, that information is stored as case history for your organization.

B. Information From Public Sources

To detect brand conflicts and suggest relevant reporting channels, our automated systems collect and analyze publicly accessible records:

  • Domains and websites: Records such as newly registered domain lists, public DNS data, certificate transparency logs, domain registration data published through RDAP (such as registrar, registration dates, and status), network and hosting information for the addresses a domain points to, published registrar and hosting abuse contacts, and the content and screenshots of publicly reachable websites that match a monitored brand.
  • Trademark registers: Public trademark filing records published by trademark offices, such as the mark, owner name and country, application and registration numbers, filing and publication dates, status, goods and services classifications, and mark images.
  • Mobile app stores: Public app listings, such as the title, description, icon, screenshots, developer name, and the developer contact details the store publishes (such as website, email address, and postal address).
  • Search engine ads: Public ads that search engines show for a monitored brand, such as the ad title and text, display URL, landing domain, the search engine’s link to the ad, and a screenshot of the search results page that showed the ad.

These records can include personal information about people who are not notolens customers. Section 5 explains how we handle it.

C. Information Collected Automatically

  • Device and network logs: IP addresses, browser user agent strings, referring URLs, request timestamps, and language preferences.
  • Operational telemetry: Diagnostic event logs, request latencies, error states, and session identifiers needed to keep the platform stable and detect malicious traffic.
  • How you found notolens: The campaign tags (UTM parameters) and referring website of your first visit, the page you first opened, and the AI client you were connecting when you arrived through one. notolens keeps these in its own cookie for up to 90 days and saves them with your account when you sign up.
  • Website analytics: notolens uses Google Analytics to count visits to its pages. Google Analytics receives the page address and title, the referring page, campaign tags, and the device, browser and approximate location it derives from your connection, and sets its own cookies on notolens.com to tell repeat visits apart. Before a page address is sent, notolens removes anything that could identify you or your data: query parameters other than page numbers and campaign tags, tokens in link paths, and in the dashboard the names of monitors and matches. Google signals and ad personalization are turned off.

3. How We Use Collected Information

We use the information we collect for the following business and operational purposes:

  • Operating, provisioning, and maintaining the monitoring platform.
  • Running scheduled scans against domain feeds, trademark registers, app store catalogs, and search engine results.
  • Evaluating potential brand conflicts, producing risk assessments and match records, and listing possible next steps with public reporting channels. Risk assessments are generated by an AI model operated by a third-party provider from the facts notolens observed and, when you have written one, the monitor’s brand context, which is sent to that provider as part of each assessment request.
  • Authenticating user sessions and connected AI clients, and keeping each organization’s data separate from every other organization’s.
  • Sending match digests, service notifications, and billing notices.
  • Investigating and preventing fraud, security incidents, abuse, and violations of our Terms of Service.
  • Analyzing aggregate platform performance to improve reliability.
  • Learning which websites, campaigns, and AI clients bring new customers to notolens.
  • Measuring which pages are visited and how visitors move through the site and dashboard.

notolens does not use customer account details, monitor configurations, or match records to train machine learning models. Requests to the AI model provider are sent with the provider’s response storage disabled, through provider endpoints that do not retain the request or the response.

4. Information Sharing and Disclosure

We do not sell, rent, or trade personal information. We do not share personal information with third parties for cross-context behavioral advertising.

No reporting on your behalf: notolens does not submit reports, dispute filings, or communications to third parties (such as domain registrars, hosting providers, trademark offices, app stores, or search engines) on your behalf. Links and contact addresses surfaced in action guides are provided solely for your own use. Anything you send to an external party is subject to that party’s privacy policy and terms.

We disclose personal information only in the following circumstances:

  • Service providers: We use third-party providers to run the Service: cloud hosting and content delivery, managed database hosting, file storage, transactional email delivery, business email hosting for messages sent to our contact address, payment processing, an AI gateway and AI model provider used to generate risk assessments, trademark register, app store and search engine data providers, website rendering, website analytics (Google Analytics), and DNS, network, and abuse-contact lookup services. Each provider receives only the data needed to provide its service to notolens. The AI gateway keeps a log of assessment requests, including the website content, records and brand context sent for assessment, for operations and debugging, and removes them on a rolling basis. A list of our service providers is available on request through the contact page.
  • Authentication providers: If you sign in with Google or Microsoft, authentication requests and basic profile verification are handled with that provider.
  • Your organization and its AI clients: Match records, including any personal information they contain, are shown to members of the organization whose monitor detected them, and to AI clients that organization connects through the MCP server. Those AI clients process what they receive under the organization’s own agreement with their provider.
  • Legal process: We may disclose information if required by law, regulation, subpoena, court order, or governmental demand, or when we believe in good faith that disclosure is necessary to protect the rights, property, or safety of notolens, our customers, or the public.
  • Business transfers: In a merger, acquisition, reorganization, financing, or sale of assets, customer information may be transferred as a business asset, subject to standard confidentiality commitments.

5. People Who Appear in Match Records

Match records can contain personal information about people who are not notolens customers, such as trademark owners, app developers, advertisers, and individuals connected to websites that resemble a monitored brand. notolens collects this information only from public sources, and only where it relates to a potential conflict with a brand a customer monitors.

We use this information to detect and document potential brand conflicts, and we show it only to the organization whose monitor detected the match. Risk assessments are informational and are not used to make decisions with legal effect about any individual. Records are kept while the monitor that detected them exists.

If you believe a match record contains information about you, you can contact us through the contact page to ask what we hold, to request a correction, or to ask us to delete it.

6. Where Information Is Processed

notolens is operated from the United States. Our service providers process and store information in the United States and in other countries where they operate. If you use the Service from outside the United States, your information will be transferred to and processed in the United States and those other countries.

7. Data Security

We use technical and organizational measures designed to protect personal information against accidental or unlawful destruction, loss, alteration, unauthorized disclosure, or access:

  • All web traffic and API communications are encrypted in transit using Transport Layer Security (TLS).
  • Each organization’s data is logically separated, and every customer request is checked against the organization it belongs to.
  • Passwords are stored as salted cryptographic hashes.
  • Administrative access to production infrastructure (hosting, database and deployment consoles) is restricted to authorized personnel on a least-privilege basis and protected by multi-factor authentication.
  • Administrative access inside the application is limited to named accounts we designate individually.

No transmission over the Internet or method of electronic storage is completely secure, and we cannot guarantee absolute security.

8. Data Retention and Deletion

We keep personal information for as long as needed to provide the Service:

  • Account data: Kept for the lifetime of your account. Deleting your account from your account settings removes your account, organization, monitors, match records, and connected AI client authorizations from our database immediately. Database backups are overwritten on a rolling schedule. The payment processor keeps its own records.
  • Monitor configurations and match records: Kept while the monitor exists, whether active or paused. Deleting a monitor deletes its match records.
  • Stored files: Captured screenshots, uploaded reference images, and stored icons and mark images are kept while the match or monitored asset they belong to exists. When it is deleted, for example with its monitor or your account, its files are deleted from file storage within about a day.
  • Sign-in sessions: Session records, including their IP address and user agent, are kept with your account and deleted when your account is deleted.
  • Operational logs: Server, diagnostic, and AI assessment request logs are kept for a limited period on a rolling basis, unless needed longer for a security investigation. Abuse-prevention records keyed by IP address or account hold only what is needed to enforce limits.
  • Billing records: Invoices and transaction records are kept for the periods required by tax and accounting laws.

9. Your Choices and Rights

You can view and update your account details and email preferences in your account settings, unsubscribe from match digests using the link in each digest, disconnect AI clients, and delete your account at any time.

Depending on your state of residence, you may have additional rights under applicable United States privacy laws, such as the right to know what personal information we hold about you, to receive a copy of it, to correct it, and to have it deleted. notolens does not sell personal information or share it for cross-context behavioral advertising, and has not done so in the preceding twelve (12) months. We will not discriminate against you for exercising any of these rights.

To make a request, contact us through the contact page or at mail@notolens.com. We verify requests using your account credentials or email confirmation before acting on them.

10. Cookies and Tracking

notolens uses its own cookies, for example to keep you signed in, to protect sign-in through Google or Microsoft against forged requests, to remember how you last signed in, to remember where your first visit came from until you sign up, and to show one-time notices, such as after you return from checkout or open a link from one of our emails.

notolens also uses Google Analytics, which sets its own cookies on notolens.com (named _ga and _ga_ followed by an identifier) to count visits and tell repeat visitors apart, as described under Information Collected Automatically. notolens does not use advertising or cross-site tracking cookies, advertising pixels, or similar technologies, and does not track visitors across third-party websites. Because notolens does not track visitors across websites, it does not change its behavior in response to Do Not Track or Global Privacy Control signals. You may configure your browser to refuse cookies, though signing in to the dashboard requires them.

11. Browser Extension

The Abuse Contact Finder browser extension shows where to report a website. It runs entirely in your browser, and notolens receives nothing from it: no visited sites, no lookups, no identifiers and no usage data.

When you look up a site, the extension sends that site’s domain name and IP addresses only to the public services that answer the lookup, and only to show where to report the site:

  • A public DNS resolver, queried over HTTPS, receives the site’s host name (such as www.example.com) to find its IP addresses, and those IP addresses to read the abuse contacts published for them in DNS. As with any DNS lookup, the resolver asks the name servers that answer for these names.
  • The domain’s registry receives the registered domain name through RDAP, the public registration lookup protocol, as does any RDAP server the registry refers the request to. The list of registries comes from IANA, and that download carries nothing about the site.
  • A public abuse contact database receives the IP addresses.

These services also see your browser’s network address, as with any web request. A list of these services is available on request through the contact page. The extension stores only one setting in your browser: that you agreed to these lookups. It stays until you remove the extension, which deletes it. Report form links open only when you click them. The extension sends requests over HTTPS only and asks for no access to the sites you visit beyond the tab you choose to look up.

The use of information received from the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

12. Children’s Privacy

The Service is offered to businesses and is not directed at children. We do not knowingly collect personal information from anyone under eighteen (18). If we learn that we have collected personal information from a child, we will delete it.

13. Changes to This Privacy Policy

We may update this Privacy Policy to reflect changes to the Service, our practices, or legal requirements. When we do, we will revise the “Last updated” date at the top of this page.

If we make material changes, we will notify you through a notice in your account dashboard or by email before the changes take effect. The browser extension has no account, so for its users the revised date on this page is the notice.

14. Contact

If you have questions or requests regarding this Privacy Policy or our data handling practices, please contact Sebastian Graef LLC through the contact page or at mail@notolens.com.