Privacy

01The short version

• Loep stores what it needs to run an account and its meter: an email address, a display name, a TradingView username if you give one, the addresses and tickers you look up and when, the surveys you save, your watchlist, and, on a paid plan, the identifiers Stripe uses for your customer record and subscription.
• Card details never touch Loep. Checkout and the billing portal are pages on Stripe's own site.
• No advertising cookies, no third-party analytics, no pixels. Three items of browser storage, all first-party, are listed under Browser storage and cookies.
• Nothing is sold and nothing is shared for advertising. The companies that do receive data are listed under Who else receives it, and why, each with the one thing it receives.
• Email laskowskidanny@gmail.com to see what is held about you, or to have it deleted. The details are under Deletion and data requests.

02Who we are

Loep is operated by ADJL Capital LLC, a company in the United States. For everything on this page the operator is the party responsible for the information described (the controller, in the language of data protection law). The operator is named here and in the other three legal documents, and nowhere else on the site: everywhere else the product speaks as Loep.

Write to laskowskidanny@gmail.com.

03What is collected, and when

Nothing on the public sheets asks you to identify yourself. Information reaches Loep at these points, and only these.

When you open an account. Your email address and a password. The password is handled by the sign-in service and is never seen by Loep's own code. A display name, if you type one. Whether you want product updates by email, which is a switch on the account page.

If you give a TradingView username. The indicators are TradingView scripts, and access is granted to a TradingView username by hand. The username you send from the indicators sheet is saved to your profile so you need not type it twice, and each request is kept with its status (pending, granted or declined) and a short note from the person who decided it.

Every metered lookup. Each lookup you run writes one line: the kind (a property survey, an area scan, a written note, a ticker report, a pulse refresh or an address lookup), the target (the address, ticker or search text, cut to 200 characters), which provider answered, whether the answer came from a cache, whether it succeeded, and the time. That line is the meter: it is how the quotas on the pricing page are counted, and how one account is stopped from running up an unbounded bill against the providers Loep pays. Ticker searches are also counted, without the search text, in a second table that feeds the trending strip; the function that reads it returns counts and never who.

What you save. A saved survey holds the address, city, state and ZIP, its coordinates, the price you confirmed, the verdict, the coverage ratio, every input you set, the figures that were retrieved for it, the results, and any notes you type. A watchlist entry is a ticker.

If you pay. Stripe sends back a customer identifier, a subscription identifier, the subscription's status and the end of the current period, and Loep stores those four things on your profile. Every event Stripe sends is recorded by its event identifier so a repeated delivery is applied once. Loep holds no card number, no expiry and no billing address: those are entered on Stripe's pages and stay with Stripe.

If you join the waitlist. Your email address, a name if you give one, which sheet you were interested in, the page the form was on, the consent sentence the form showed you (stored verbatim), and a salted one-way hash of your network address. The hash lets the form recognize a repeat submission from the same connection, so it cannot be used to send mail to somebody else's inbox over and over; it does not identify you and it cannot be reversed.

If you email. Whatever you put in the email.

Loep does not ask for, and has no field for, a date of birth, a telephone number, a postal address, a brokerage login or a financial account number.

04Where it lives

The sign-in directory is shared with another product of the operator, so your email address sits in one directory that both products use. Nothing else is shared: Loep's tables are Loep's, an account on Loep gives no access to the other product, and the reverse.

05Browser storage and cookies

Loep sets no advertising cookie, no analytics cookie and no tracking pixel, and loads no third-party script. The map tiles are the one thing your browser fetches from somebody else's server; see Who else receives it, and why.

What Loep does use is your browser's own storage, for three things. Every one is first-party, none identifies you to anybody else, and none follows you to another site.

You can clear all three at any time from your browser's settings for this site. Nothing breaks: you are signed out, the theme follows your system, and the next sign-in lands on the account page.

Checkout and the billing portal are pages on stripe.com. What Stripe stores in your browser there is governed by Stripe's own policy, and none of it is read by Loep.

There is no consent banner, and that is deliberate. Consent is required for storage that is not necessary for something you asked for. All three items above hold a session you opened, a choice you made, or the page you were on. Asking you to agree to that would be theatre, and it would train you to dismiss a banner that one day mattered. If Loep ever adds anything that genuinely needs consent, the banner arrives with it.

06Who else receives it, and why

Nothing is sold, and nothing is shared for anybody's advertising. Loep has no advertising.

These are the companies that receive data in the course of a lookup or a payment, and what each one gets. The list is complete. Every one except the map tile host is contacted from Loep's server, never from your browser: it receives no cookie of yours and no network address of yours, and it has no way to connect a request to you.

Each provider is named, with what it supplies and what its license requires, on the disclosures page under Data sources. The names appear there and nowhere else on the site, by design.

The written note is worth a second sentence: its brief includes the property's address, because that is what the note is about. It is not your address, but it is a specific property, and you should know it leaves Loep's systems.

Loep will also disclose information if the law requires it.

07How long it is kept

Nothing is deleted on a schedule yet. This section says what that means item by item, rather than promising a schedule that does not run.

• The account and what you save are kept for as long as the account exists. Saved surveys and watchlist entries are yours to remove one at a time from the sheets themselves, without asking.
• The lookup log is kept while the account exists. The meter reads only the last hour or the last day of it, and older lines are read by nobody in the ordinary course. Loep does not yet delete old lines on a schedule; when it does, this page says so.
• The ticker counts are kept as counts. They carry no search text.
• Cached provider answers are replaced on their own clocks: a parcel record after seven days, a listing's status after twenty-four hours, a geocoding answer after thirty days. They are keyed by address or query, not by account.
• Billing identifiers and Stripe's events are kept as the record of what was paid for and when. Stripe keeps the invoices for as long as tax and card-network rules require, under its own policy.
• Waitlist entries are kept until the analyst sheet opens and for a reasonable period afterwards, or until you ask to be removed. The network-address hash stays with the entry until then.
• Indicator requests are kept with their outcome while the account exists, so the sheet can show the status without asking again.

When an account is deleted, the profile, the saved surveys, the watchlist and the indicator requests go with it. The lookup log and the ticker counts keep their lines with the account reference removed, so the meter's history and the trending counts stay whole without pointing at anyone.

08Deletion and data requests

Whoever and wherever you are, you can ask Loep to:

• tell you what it holds about you, and give you a copy;
• correct anything that is wrong;
• delete it, which closes the account;
• stop emailing you, which you can also do yourself with the updates switch on the account page (email about the account itself, such as a confirmation, a reset link or a receipt, still arrives, because the account cannot run without it);
• give you your information in a portable form, if you want to take it elsewhere;
• object to or restrict what is done with it.

Write to laskowskidanny@gmail.com from the address on the account, or with enough detail to find you. You may be asked to confirm who you are before anything is handed over, because giving somebody's information to the wrong person is the failure that matters most here. There is no charge, and the answer comes within one month.

Deleting an account removes what How long it is kept says it removes. Stripe keeps what tax and card-network rules require it to keep, under its own policy, and you can ask Stripe for it directly.

Nothing is sold, and nothing is shared for cross-context behavioral advertising, under any definition, including California's. There is no "do not sell" switch on this site because there is nothing for it to switch off. If you are unhappy with how a request is handled, you can complain to your local data protection authority.

09How it is protected

The measures below are specific, because a paragraph promising "industry-standard security" says nothing.

• Every page is served over HTTPS, and the site sends a Content-Security-Policy that permits scripts only from its own origin. That is what stops a compromised third-party script from reading a signed-in session token, and it is why the site loads no third-party script at all.
• What one account can read is decided by the database, not by the code that asks: row-level security lets the owner of a row see it and nobody else. The lookup log, saved surveys, the watchlist and indicator requests are all protected this way.
• The waitlist, the caches, Stripe's events and the ticker counts carry no browser access at all. Only Loep's own server code touches them, and the key it uses never reaches a browser; the build fails if it would.
• Passwords are handled by the sign-in service and are never seen by Loep's code. Confirmation and password reset go through links sent to your email.
• Events from Stripe are accepted only when their signature verifies, and each is applied once.
• The network-address hash behind the waitlist is computed with a secret, so the stored value cannot be turned back into an address.

No system is perfect, and Loep does not claim this one is. A security problem can be reported to the address in security.txt.

10Where it goes

Loep is operated from the United States and its providers are principally in the United States. If you are in the United Kingdom or the European Economic Area, what you give Loep is transferred to the United States, and the providers rely on standard contractual clauses for those transfers.

11Children

Loep is for adults. Nobody under 18 may open an account, and Loep does not knowingly collect information from anybody under 18. If it learns that it has, it deletes it.

12Changes

If this page changes, the effective date at the top changes with it. If a change is significant for people who already hold an account, they are emailed rather than left to notice.

13Contact

Effective 2026-09-17. Questions, requests and complaints about privacy go to laskowskidanny@gmail.com. A domain mailbox may replace that address later, and this page changes when it does.