1. Who is responsible for your data
Bricklayers, MB, a Lithuanian small partnership (mažoji bendrija), legal entity code 308133831, registered office: Laisvės al. 85E-5, LT-44297 Kaunas, Lithuania. Registered in the Register of Legal Entities of the Republic of Lithuania. Contact: help@bricklayersapps.com.
We are the controller of personal data processed to operate CloserLook. This notice covers website visitors, account holders, people who contact us, and people whose information is submitted to or appears in a search, report or coach conversation. You do not need a CloserLook account to exercise your data-protection rights.
We apply the EU General Data Protection Regulation (GDPR) and applicable Lithuanian data-protection law. Contact help@bricklayersapps.com for privacy questions, a copy of your information, a correction, deletion or an objection to processing.
2. Information we handle and where it comes from
- Account and support information: your email, account identifier, sign-in and account status, preferences, and the messages and attachments you send to support.
- Guided-experience and search inputs: your quiz answers and relationship concerns, the name, username, age, approximate location, phone number, profile links and photo you choose to supply, and any email or preference submitted in the flow. Available fields vary by feature; many are optional.
- Public-source information: public profile names, handles, biographies, photos, counts, follower samples, posts, professional or education details, web-search results and source links. Sources may include Instagram, Facebook, LinkedIn and publicly accessible websites, obtained directly or through search and data-retrieval providers. Someone requesting a search may provide the initial identifying details.
- Reports and AI inferences: collected evidence, possible profile matches, summaries, assessments, source references and generated reports. These can concern someone who has never used CloserLook and can be inaccurate.
- Coach content: messages, conversation history, uploaded screenshots or images, AI replies and associated timestamps. Your uploads may contain other people’s information.
- Technical and usage information: browser and request information, which may include IP addresses in infrastructure logs, session identifiers, language, requested URLs, error records, security events and records of feature use and generation.
- Order and payment information: the offer you select, the amount and currency, payment and subscription status, related confirmations, and the Stripe customer and subscription identifiers linked to your account. A one-time add-on you buy after checkout, such as an ebook, is charged to the card or wallet saved with Stripe when you paid, and is recorded in the same way. Card and wallet details, such as Apple Pay or Google Pay, are entered directly into Stripe’s secure payment form and are processed and stored by Stripe. We never receive or store your full card number or security code. For each payment, Stripe tells us the card brand, the last four digits and issuing country of the card, the wallet used, Stripe’s card fingerprint (a code that recognises the same card without revealing its number), the results of the security-code and 3-D Secure checks, Stripe’s assessment of the fraud risk, and any refund or dispute.
- Checkout and sign-in records: the purchase details and terms shown to you when you continue to payment (the offer, the amount charged today, the renewal amount and date, and the versions of the policies linked there) and the time zone your browser reported; your return from the payment page; each sign-in link you request and each sign-in, with the method used; and records that your order email, each email telling you that a report is ready and your ebook delivery emails were sent, the address each was sent to, and whether they were delivered.
- Device check: a one-way code that your browser calculates from its technical settings (platform, type of operating system, screen size and pixel density, colour depth, time zone, language, number of processor cores and touch support). The type of operating system, such as Windows or Android, is worked out from the platform and your browser’s identification string, without any version number. The code is sent when you continue to payment and once at the start of each browser tab session in your account, and helps show whether a payment and later use of the account came from the same device.
- Records of use: when a report is ready; when you open or download a report or an ebook; when you start a new search, but not the search itself; when you send a coach message or upload images (which coach, how many images and their total size, never the content); when you open settings; and whether you accepted or declined each one-time offer after checkout.
Each of these records notes when it was made. Records made from your browser also contain your IP address, the approximate location derived from it (country, region and city), your browser’s identification string and its language, a reference to your sign-in session when you are signed in and, where one was sent, the device check. Together with the payment details from Stripe described above, they are our payment-security records, kept to prevent payment fraud and to answer payment disputes (see sections 3 and 9). They never include anything about the person you searched for, report content, search details, quiz answers, the content of coach conversations or page addresses, and they identify a report only by a random reference number.
A photo selected in the quiz stays in your browser. It is not uploaded to or stored on our servers and is used only for the on-screen matching step. Some guided-flow answers and contact details are passed in page URLs, which can appear in browser history and server logs. Avoid sharing a full personalised flow URL.
Quiz statistics: as you go through the quiz, we receive a random reference for that run of the quiz, your market, the furthest screen you reached and the answers you tapped, so that we can see where people stop. Nothing you type is included: a name, username or age counts only as given or not, and an email address or photo is left out. These statistics are not linked to your account or email address.
3. Why we use information and our legal bases
- Providing a service you request: account creation, authentication, saving your work, providing reports and coach replies, and handling service-related support. For your own data that is necessary for these activities, the basis is performance of a contract or steps you request before a contract (GDPR Article 6(1)(b)).
- Public-information research about other people: our and our users’ legitimate interests in organising relevant public information and assessing possible profile matches (Article 6(1)(f)), only where the processing is necessary and those interests are not overridden by the person’s rights and freedoms. Your contract with us does not itself provide a contractual legal basis for processing someone else’s data.
- Other people’s information in coach submissions: our and our users’ legitimate interests in providing contextual assistance with a conversation the user chooses to discuss (Article 6(1)(f)), only where necessary, proportionate and not overridden by the other person’s rights. Submit only relevant information and remove unnecessary identifying details. A user’s contract or consent does not automatically cover another person.
- Security, reliability and resolving disputes: our legitimate interests in preventing misuse, diagnosing problems, protecting accounts and defending legal claims (Article 6(1)(f)). We limit this processing to what is necessary for those purposes.
- Preventing payment fraud and answering payment disputes: we use the payment-security records described in section 2 to prevent payment fraud, including false claims that a purchase was unauthorised, not recognised or cancelled; to respond to payment disputes and to questions about a charge from the bank that issued your card; and to pause access to your account while one of your own payments is disputed with your bank, or after the bank has reversed it. Access is paused automatically when Stripe tells us about a dispute, but only for the account whose own purchase is disputed. The pause ends when the dispute is closed in our favour (as happens when it is withdrawn), when you pay again, or when we lift it after a review; you can ask us to review it at any time. The legal basis is our legitimate interests in preventing fraud and in establishing, exercising or defending legal claims (Article 6(1)(f)). We do not use these records for analytics, advertising, pricing or emails.
- Legal obligations: responding to valid legal requests, exercising data-protection duties and, when applicable, keeping required accounting records (Article 6(1)(c)).
- Emails: emails about your order and account, such as the purchase confirmation with your sign-in link, are part of providing the service you request (Article 6(1)(b)). Reminders and offers after you leave your email in the quiz are sent only if you agreed to email updates on that step, on the basis of your consent (Article 6(1)(a)). You can withdraw it at any time with the unsubscribe link in every such email or by writing to help@bricklayersapps.com. This stops further reminders and offers, but not emails about an order you place.
- Optional consent-based activities: where consent is required for promotional messages or non-essential tracking, Article 6(1)(a). Creating an account, receiving a report or accepting terms is not, by itself, marketing consent. You may withdraw consent without affecting earlier lawful processing.
Required information is identified by the relevant form. Without an email we cannot provide email-based account access; without useful search details we may be unable to find relevant public information. You can leave optional fields blank. Refusing optional marketing consent does not prevent use of the Service.
4. People mentioned in searches and sensitive information
CloserLook is not a data broker and does not maintain a database of people. We do not keep a searchable index of individuals, and we do not sell, rent or trade lists or databases of personal data. Each report is compiled on request for the customer who ordered it, only from publicly accessible sources and the details that customer provides, and is deleted automatically 31 days after it is created. Our payment-security records about customers refer to a report only by a random reference number and contain nothing about the person searched. We do not access private accounts or messages, and we do not use leaked or purchased databases.
Publicly accessible information is still personal data. Its availability is not blanket consent to collection, profiling or redistribution. The context, necessity, reasonable expectations and possible effects on a person matter when assessing legitimate interests. Information and generated inferences can be shown to the user who requested the relevant report or conversation.
If your information appears in CloserLook, email help@bricklayersapps.com to ask about its source, access it, correct a mistaken identity, request erasure or restriction, or object to our use of it. Include only enough detail to help us locate the relevant profile or report. We may ask for proportionate verification before disclosing data or making a change. Removing data from our systems does not remove the original information from an unrelated website.
When we obtain information indirectly, GDPR Article 14 may require us to notify the person individually, generally within one month or earlier on the first relevant communication or disclosure. Making this policy public does not automatically replace that duty. An exception can apply only where its specific legal conditions are met.
Do not submit unnecessary health information, intimate content, political or religious beliefs, criminal-record information or other particularly sensitive data. Public-source material and conversations can nevertheless contain such information. A legitimate interest alone is not sufficient to process GDPR special-category data: a separate Article 9 condition is required. Information is not “manifestly made public” by the person merely because another person published it or an AI inferred it.
5. AI processing and automated assessments
To create a report, we send relevant subject details and collected evidence to an AI provider. For a coach reply, we send relevant conversation history and, where the feature supports images, recent uploaded images. Earlier images may remain in your saved conversation even when they are not included in a later AI request.
AI analysis may constitute profiling, for example when it proposes identity matches or summarises interests or behaviour from public activity. The output is probabilistic and may be wrong. We do not use these reports or coach replies to make decisions about you with legal or similarly significant effects, and our terms prohibit users from using them for eligibility decisions such as employment, credit or housing.
A coach conversation is not a confidential professional consultation. Avoid including information that is unnecessary for your question, and redact third-party details from screenshots where possible. You may challenge inaccurate information through the contact above.
6. Who receives information
Access is limited by the purpose of processing. Our current technical integrations include the following providers; which AI route is used depends on the feature and service configuration:
- Supabase: account authentication, application database and storage for reports, conversations and uploaded media.
- Apify and relevant actor providers: retrieving public profiles and web information using submitted identifiers, profile URLs and search queries.
- Anthropic: processing relevant report inputs, public-source evidence and coach content to generate AI responses.
- Stripe: payment processing, subscriptions, fraud prevention and payment disputes. Stripe receives the card or wallet details you enter in its payment form, your email address and the order amount, collects device and connection information on its payment form to detect fraud, and acts as an independent controller for some of its own legal and fraud-prevention purposes. When a payment is disputed, or the bank that issued your card asks about a charge, we send Stripe the payment-security records needed to respond: records of the order and of your earlier payments, the terms shown at checkout, your IP address, approximate location and device information, your sign-ins and use of the Service, and the records that your order email, the emails telling you that a report is ready and your ebook delivery emails were sent and delivered, with the address each was sent to. We never send Stripe anything about the person you searched for, report content or search details.
- Card networks and your card issuer: when a payment is disputed or queried, Stripe passes our response to the card network (such as Visa or Mastercard) and the bank that issued your card, which handle it as independent controllers. They may be located outside the European Economic Area; passing our response to them is necessary to establish, exercise or defend the claim.
- Vercel: website infrastructure and, where configured, its AI Gateway routing requests to the AI provider.
- Resend: email delivery. Resend sends our account, sign-in and order emails and, where you agreed, reminders and offers. It receives your email address and the content of each message, and tells us whether a message was delivered, bounced or reported as spam. Our emails never include details of the person you searched for.
- Microsoft: Microsoft Clarity, which records how the website, the quiz and the offer pages are used, so that we can improve them (see section 8).
- Meta: the Meta Pixel, which measures our advertising on the website, the quiz and the offer pages (see section 8).
Information may also be available to authorised staff, hosting and email-delivery providers, and professional advisers where necessary for their work. The requesting user receives the relevant report or coach response and can retain a downloaded copy. We may disclose information to authorities when legally required, to establish or defend legal claims, or as necessary for a business reorganisation subject to appropriate confidentiality and data-protection duties.
Providers processing data on our behalf are subject to applicable data-processing obligations. Some providers also act as independent controllers for their own legal or security purposes. Third-party platforms and sites that you visit through a link apply their own privacy notices. Contact us for details of the recipients relevant to your data.
7. International processing
Providers and their subprocessors may process information outside Lithuania or the European Economic Area, including in the United States. We do not represent that all data stays in the EU. Locations depend on the relevant provider, hosting arrangement and processing route.
A transfer outside the EEA must have a valid GDPR transfer mechanism, such as an applicable European Commission adequacy decision or appropriate safeguards, including standard contractual clauses and any necessary supplementary measures. You may contact help@bricklayersapps.com to ask where your data is processed and obtain information about, or a copy of, the safeguards applicable to a particular transfer, with confidential details protected where necessary.
9. How long information is kept
We retain personal data for the purpose for which it is needed, taking account of the type of information, ongoing account access, deletion requests, legal obligations and unresolved disputes. The criteria differ by category:
- Reports and search details: each report, together with the public-source evidence, photos and search details collected for it, is deleted automatically 31 days after the report is created. Order and payment records, and payment-security records such as the record that you opened or downloaded a report, are kept separately, as described below. Those records identify a report only by a random reference number and contain nothing collected for it.
- Quiz lookups: the public-profile check and follower preview run during the quiz are kept only as a short cache and are deleted automatically within two days.
- Reminder list: if you agreed to email updates when you left your address in the quiz, we keep your email address, your language and a record of your consent (the wording you agreed to, when, your browser’s identification string and a one-way code derived from your IP address) and send reminders until you unsubscribe, buy, or ask us to delete your entry. After you unsubscribe or buy, or an email to you bounces or is reported as spam, we keep the entry only as a record that stops further reminders to that address, until you ask us to delete it. The search details saved with it so that a reminder can reopen the same offer (name, username and age) are deleted automatically 31 days after you left them. The record of each email we send you (its type, when it was sent and whether it was delivered) is deleted automatically 31 days later; only the records that your order email, the emails telling you that a report is ready and your ebook delivery emails were sent and delivered, with the address each was sent to, are kept longer, with the payment-security records below.
- Accounts and coach conversations: for the period needed to provide your account and saved features. There is currently no fixed automatic expiry for coach history or the images uploaded to it. You can ask us to close your account or delete particular information; we assess what must be removed and whether a lawful retention exception applies.
- Support and security records: for the time needed to handle the issue, investigate misuse and deal with related claims, taking account of applicable limitation periods.
- Payment-security records: each payment-security record described in section 2 is kept for 18 months after it is made, so that we can answer a payment dispute within the time limits the card networks allow. The record of the purchase details and terms shown to you at checkout is kept for as long as your subscription runs and for 18 months after it ends. We keep these records longer only while a dispute about one of your payments is open and for 4 months after it closes.
- Accounting and legal records: where applicable, for the period required by the relevant tax, accounting or other legal obligation. Such a requirement does not justify keeping all report or conversation content for the same period.
- Browser storage: as described in section 8. Browser-only expiry does not determine server-side retention.
Deletion from active systems may precede expiry of restricted backup copies or provider records retained under a separate lawful obligation. We can explain the retention applicable to your request. Where we must keep particular information, we will explain the reason rather than treating account closure as immediate deletion of every record.
10. Protecting information
We use access controls, authenticated account access and restricted storage for customer reports and uploaded media. Access to private files is limited through authorisation checks and time-limited file links. We take proportionate technical and organisational measures to protect information, but no internet service can guarantee absolute security.
Protect your email and sign-in links, avoid sharing private report links, and sign out on shared devices. Report a suspected security problem to help@bricklayersapps.com.
11. Your rights and how to use them
Subject to the conditions in applicable law, you can request access to your personal data and a copy, correction, erasure, restriction of processing, and portability of data you provided where processing is automated and based on consent or contract. You may withdraw consent at any time without affecting the lawfulness of earlier processing. If you ask us to erase your data, we keep payment-security records until their period in section 9 ends, because they may be needed to establish, exercise or defend a legal claim about your payments (GDPR Article 17(3)(e)), and we use them only for that; the rest is deleted unless another exception described in section 9 applies.
You may object to processing based on legitimate interests because of your particular situation. We must stop that processing unless we demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or need the information for legal claims. This means we may continue to use payment-security records to answer a dispute about your payments until their retention period ends. An objection to direct marketing must be honoured without this balancing exercise.
Email help@bricklayersapps.com and describe your request. You do not need to purchase a report or create an account. We will respond without undue delay and normally within one month. For complex or numerous requests, we may extend by up to two further months, explaining the reason within the first month. We may ask for additional information where reasonably needed to verify identity. Requests are normally free; any lawful exception will be explained.
You can complain to the Lithuanian State Data Protection Inspectorate (VDAI), or to the competent supervisory authority where you live, work or believe an infringement occurred. You do not have to contact us before making a complaint. Judicial remedies remain available.
12. Children’s information
CloserLook is intended for adults aged 18 and over. Our terms prohibit using it to investigate children. Public material or user submissions may nevertheless include a child’s information. If you believe we hold such information, contact help@bricklayersapps.com so we can investigate, restrict use where appropriate, and remove information where required.
13. Changes to this policy
We will update this notice when our practices or legal requirements change. The date above shows when this notice was last changed. We keep every earlier version and can tell you which one applied at a given time. For significant changes we will provide an appropriate notice, and obtain new consent where required before beginning a new consent-based use. Contact help@bricklayersapps.com if you need clarification about this English version or the handling of your information.