Privacy Policy

DeepSearch is operated by RELOAD TECHNOLOGIES - FZCO ("DeepSearch," "we," "us," or "our"). This Privacy Policy applies to our websites, mobile applications, APIs, search and research products, Data Cleanup service, customer support, and other services that link to it (collectively, the "Service").

We generally act as the controller or business for account, transaction, product-usage, support, and marketing data. This means we determine why and how that information is processed. Search subjects, customers, and visitors are different groups of people.

The sections below distinguish data received directly from a customer from public or licensed information about a search subject. That person may never have used the Service.

This Policy does not govern a third-party website, app store, payment provider, source site, public authority, or data supplier. Those parties process information under their own notices. If another organization gives you access to the Service, that organization may separately control the information it submits and its users' activity.

We may process information relating to:

• Visitors and account holders, including people who use a free, trial, paid, mobile, developer, or business account.
• Search subjects, whose public or licensed information may appear in a candidate match, profile, phone page, company result, public record, image result, or research response.
• Data Cleanup customers, who authorize us to use identity details to locate and submit opt-out or deletion requests to participating data brokers.
• Support contacts, business representatives, writers, partners, and job applicants who communicate with us.

Information may remain personal data even if it is public, professionally oriented, or obtained from a licensed source. We apply this Policy according to the context, our role, and the law that applies to the individual.

Depending on how you use the Service, we may collect:

• Identity and account data: name, email address, authentication identifiers, account status, language, profile image, organization or workspace details, and security settings.
• Usage data: searches, prompts, filters, candidate choices, reports opened, saved items, watchlists, chat threads, feedback, API and connected-assistant usage, feature interactions, and timestamps. Anonymous chats stay out of normal chat history and the profile dashboard; this is not a promise that no operational or security record is processed.
• Device and log data: IP address, browser and device type, operating system, app version, referral page, approximate location derived from IP, diagnostic events, crash data, security signals, and cookie or device identifiers.
• Transaction data: plan, credits, trial or introductory offer, price, currency, billing status, payment-provider identifiers, invoices, refunds, disputes, and subscription events. Stripe, PayPal, Apple, Google, or another payment provider receives payment credentials; we do not store full card numbers.
• Communications: support messages, attachments, survey answers, refund or rights requests, and records needed to resolve them.

You may submit a name, username, phone number, email address, company, vehicle identification number, URL, image, document, audio, video, or free-form prompt. We process that material to perform the request, find and rank possible matches, generate a response, prevent misuse, and maintain the requested history or workspace feature.

Inputs can relate to you or another person. Do not submit private, unlawfully obtained, or highly sensitive information that is unnecessary for the task. You are responsible for having a lawful reason to submit information about someone else. Uploaded files may contain hidden metadata, faces, voices, location details, or third-party personal data. Review them before upload.

Some uploads are stored in private object storage long enough to provide the feature, create a signed access link, maintain your history, or investigate a security issue. Other content may be processed in the browser or sent directly to a contracted search or AI provider. We do not promise that every feature uses the same storage path or retention period.

You can use DeepSearch from an AI assistant or developer tool, such as ChatGPT, Claude, Meta's Muse, or your own application, through our API and MCP servers. You authorize each connection by signing in and approving the permissions it asks for, or by creating an API key. You can disconnect an assistant at any time under Developers → Integrations, and revoke a key under Developers → API keys. Disconnecting stops further access, including background lookups that are still running.

A connected assistant sends us the request it was asked to run, such as a name, phone number, email address, username, company, vehicle identification number, or a question about a person, and we return the result to that assistant. The assistant's provider processes your conversation and those results under its own terms and privacy policy, which we do not control.

For each request we record usage metadata: the account, the key or connected app, the operation, the client application, the status, the duration, and the usage charged. Requests that run as background jobs, or that are sent with an idempotency key so a retry is safe, keep their inputs or results so they can be retrieved; we delete those records 30 days after the request finishes, or sooner if you delete your account. We do not use these requests or results for advertising.

A connection cannot start a purchase. If you have turned on automatic extra usage, a request that runs out of usage can trigger the refill you set up, as it would in the app; requests through the Muse connector never do.

The Muse connector runs every lookup in a restricted research mode. It does not use content from Meta platforms or match faces, leaves out dating, relationship, adult, data-breach, and account-registration information, returns contact details only for the identifier you searched, and reports approximate locations only. The Muse connector documentation describes it in full.

The core Service finds, organizes, ranks, and summarizes information from public websites, public social profiles, public records, public business sources, news, licensed search indexes, licensed numbering or carrier data, and other data suppliers. This may include names, aliases, age range, contact details, general location, professional history, business affiliations, usernames, profile URLs, public posts, images, vehicle or company information, and links to the source.

We may generate candidate matches, confidence indicators, entity links, summaries, or inferred associations from those sources. A candidate match is not a verified identity. Common names, stale sources, recycled phone numbers, parody accounts, and conflicting records can produce an incorrect or incomplete result.

We do not access private accounts, private messages, passwords, leaked credentials, live location, or private carrier subscriber records as part of the consumer Service.

A person can ask us to suppress a DeepSearch page or result through Remove my info. Suppression affects our output; it does not erase the source record or another service's copy.

When we complete a person, company, or vehicle report, we store it in a shared cache keyed to the report's subject, such as a person identifier, a company, or a vehicle identification number, rather than to the customer who asked for it. A report generated for one customer, including through a connected assistant, can therefore be shown to another customer who later looks up the same subject. A cached report contains the public and licensed information described above and its sources. It does not record who requested it.

The standard caches have no fixed expiry: a report is reused until it is refreshed, replaced, or suppressed. Person and company reports produced by the Muse connector are kept in a separate cache, deleted 30 days after they are built, and never mixed with the full service's reports. Vehicle reports are built the same way for both and share the standard cache.

Deleting your account does not remove cached reports about other people, because they are not part of your account. A person can ask us to suppress reports about them through Remove my info, and we then withhold that person from cached and new results.

Data Cleanup is a separate, user-authorized removal campaign. To locate your records and reduce false matches, we may collect the name and aliases, email addresses, phone numbers, current and previous addresses, and birth year you choose to provide. The service is for an adult requesting work for themselves.

We encrypt the removal profile in storage. We use it to scan participating data-broker sources and create a provider-side member or case. We also use it to submit and track opt-out or deletion requests, and to request your action when a broker requires it.

The profile also helps us measure campaign progress, prevent mismatches, and handle support or disputes.

We disclose the minimum information reasonably needed to our contracted removal provider and to the data brokers receiving the authorized requests.

A broker may require verification, reject a request, retain information under an exception, or republish information obtained from a public or upstream source. Data Cleanup therefore does not guarantee universal or permanent removal.

Closing your DeepSearch account does not automatically retract a request already sent to a broker. See the Terms of Service and Delete Account page for the separate service and deletion rules.

We obtain information:

• directly from you, your device, or your authorized workspace;
• from public websites, public records, and public social or business profiles;
• from contracted search, enrichment, data-broker, telecom metadata, public record, fraud-prevention, and identity-resolution providers;
• from authentication, hosting, analytics, communications, payment, app-store, and customer-support providers; and
• from inferences we create, such as candidate rankings, possible associations, approximate location, usage segments, or abuse-risk signals.

Source availability changes. A listed or linked source is not necessarily controlled by us, and the source remains responsible for its own publication and accuracy obligations.

We process information to:

• create and secure accounts, provide searches, AI responses, APIs, and purchases;
• find, rank, deduplicate, and explain possible matches and source links;
• perform an authorized Data Cleanup campaign;
• operate billing, credits, subscriptions, receipts, refunds, and tax records;
• provide support and communicate service, security, and policy notices;
• measure performance, understand product use, and improve reliability and design;
• detect fraud, scraping, prohibited use, security incidents, and legal violations;
• establish, exercise, or defend legal claims and comply with lawful requests; and
• protect users, search subjects, the public, our rights, and the integrity of the Service.

Where a law requires a legal basis, we rely on the following bases as applicable: performance of a contract, steps requested before a contract, compliance with legal obligations, consent when specifically requested, and our legitimate interests or those of others.

Those interests include providing a useful public-information research tool, preventing misuse, improving the Service, and protecting legal rights.

We balance those interests against the nature of the data, the source, the likely impact, user expectations, access controls, removal paths, and other safeguards. You may object to processing based on legitimate interests as described below.

AI and statistical systems may interpret a prompt or attachment, generate search variants, rank possible matches, extract facts, summarize sources, translate text, or draft an answer. To provide those features, relevant prompts, files, retrieved material, and limited technical context may be sent to contracted AI gateways and model providers. Provider and model selection can change based on the feature, availability, quality, safety, and cost.

AI output can be inaccurate, incomplete, outdated, or attributed to the wrong person. It must not be treated as verified fact or used for a legally significant decision. We do not use DeepSearch candidate ranking to make decisions on your behalf about credit, employment, housing, insurance, education, government benefits, or another person's eligibility. The Terms of Service prohibit users from doing so.

We may disclose information to:

• Infrastructure and product providers that support hosting, storage, authentication, search, AI, analytics, communications, fraud prevention, support, and software operations.
• Payment providers and app stores that process purchases, subscriptions, refunds, chargebacks, tax, and entitlement status.
• Data Cleanup providers and receiving brokers when you expressly authorize a removal campaign.
• Assistants and apps you connect, which receive the requests and results you exchange through them.
• Other users or the public when a product is designed to publish a public page, shared report, source link, or public-information result.
• Professional advisers, auditors, insurers, authorities, or litigants when reasonably necessary for compliance, safety, a legal claim, or a valid legal process.
• A transaction counterparty in a financing, reorganization, merger, acquisition, sale, insolvency, or transfer of all or part of our business, subject to appropriate confidentiality and legal safeguards.

Service providers are authorized to process information for contracted purposes. A source site, independent app store, payment company, or data broker may instead act as an independent controller under its own terms.

We do not sell the payment credentials, private account content, or Data Cleanup profile that you provide to us for money. We do, however, operate a paid service whose core function is to find, organize, and provide access to public and licensed information about search subjects.

Some privacy laws define "sale" or "sharing" broadly. Paid access to search-subject information may fall within those terms. So may certain advertising and measurement disclosures. This can apply even when no account data is sold for money.

An eligible person may request that DeepSearch stop displaying information about them or opt out of covered sale or sharing through Remove my info or by emailing support@deepsearch.app. We do not discriminate against a person for exercising an applicable privacy right.

We and our providers use cookies, pixels, SDKs, browser storage, and similar technologies for authentication, security, preferences, payments, product analytics, communications, and, when configured, advertising measurement. These technologies can collect device, network, interaction, referral, and campaign data over time.

Strictly necessary technologies support login, security, and checkout. Other technologies may be optional or require a choice under applicable law. The Cookie Policy identifies the principal categories, providers, controls, and consequences of blocking them.

We are based in the United Arab Emirates and use providers that may process information in the United States, European Economic Area, United Kingdom, and other countries. Those countries may have privacy laws different from the place where you live.

Where required, we use an approved transfer mechanism or another lawful basis, such as standard contractual clauses, an adequacy decision, contractual and technical safeguards, or your explicit request for a cross-border service. No transfer mechanism can eliminate every risk, and authorities may have lawful access under the destination country's laws.

For Protection, campaign identity details are cleared 30 days after a campaign ends without a renewal. Scan records and their steps are kept for 180 days. Findings are cleared 12 months after the last scan or campaign, whichever is later. Payment records are kept separately. Signed-in customers can export their Protection data or delete it in Protection settings.

We retain information for no longer than reasonably necessary for the purposes described here. We consider account status, feature settings, source freshness, contractual commitments, and limitation periods. We also consider tax and accounting duties, fraud and security risk, disputes, and legal holds. Different categories therefore have different periods.

• Account content is generally retained while the account is active and then deleted or anonymized through the account-deletion process, subject to exceptions.
• Billing, refund, authorization, security, abuse, and legal records may be retained after account closure when needed for compliance or a claim.
• Search-subject information is refreshed, replaced, or suppressed based on source changes, product needs, removal requests, and applicable law.
• Background job records created through the API or a connected assistant, including their inputs and results, are deleted 30 days after the job finishes.
• Shared report caches have no fixed expiry. Reports produced by the Muse connector are deleted 30 days after they are built. See Shared report caches.
• A suppression record may be retained after removal so the same page or subject is not automatically republished and so we can demonstrate the request was honored.
• Backup copies may persist for a limited disaster-recovery cycle and are not restored into ordinary use unless recovery is required.

See Delete Account for the operational account-closure process. Deleting an account and suppressing a public result are separate actions because they concern different people and records.

We use administrative, technical, and organizational safeguards designed for the nature and risk of the information, including access controls, encrypted transport, encryption for selected high-risk stored data, private storage, signed access links, monitoring, provider review, and deletion procedures. Access is limited according to role and operational need.

No online service, transmission, or storage system is completely secure. You are responsible for using a unique password, protecting login codes and API keys, limiting shared links, reviewing files before upload, and telling us promptly at support@deepsearch.app if you suspect unauthorized access. Where law requires, we will investigate and give affected people or authorities an incident notice.

Depending on your location and our role, you may have rights to know or access, receive a portable copy, correct, delete, restrict or object to processing, withdraw consent, opt out of covered sale, sharing, targeted advertising or profiling, and complain to a regulator. Withdrawing consent does not invalidate processing already completed. Some rights are subject to identity verification, legal exceptions, and the rights of others.

Submit an account request through your account controls or email support@deepsearch.app. To suppress a public DeepSearch page or search result, use Remove my info. Describe the right, the information or page involved, your country or state, and an email where we can respond. We may ask only for information reasonably needed to verify the request, prevent fraud, locate the record, and confirm an authorized agent's authority.

We will respond within the period required by applicable law and explain any extension or denial. You may appeal a denial by replying with "Privacy appeal" and the reason you believe the decision should change. You may also complain to the data protection or consumer authority where you live. We will not retaliate or provide unlawfully different service because you exercised a privacy right.

In the preceding 12 months, the categories we may have collected include identifiers; customer records; commercial information; internet or electronic activity; approximate geolocation; audio, visual, or similar information; professional or employment information; user content; and inferences. The sources, business purposes, and recipient categories are described above.

Depending on the feature, some Data Cleanup identifiers or account credentials may be treated as sensitive personal information. We use sensitive information only as reasonably necessary for the requested service, security, legal duties, and other purposes permitted by law; we do not use a Data Cleanup profile to infer characteristics for advertising.

We do not knowingly sell or share the personal information of people under 16. California and other eligible residents may submit requests to know, correct, delete, or opt out, and may use an authorized agent.

Because paid access to public or licensed search-subject information can fall within broad state-law definitions, the removal channel also serves as our direct opt-out path for covered DeepSearch publication and access.

We may retain or continue processing information when an exception applies, including security, legal compliance, exercising rights, completing a requested transaction, or maintaining a suppression record.

The Service is not directed to children and account holders must be at least 18. We do not knowingly collect account data from a child. Public-source material may sometimes mention a minor; users must not search for, compile, expose, or use information about a minor for harmful, exploitative, or unlawful purposes.

Tell us at support@deepsearch.app if you believe a child has submitted account data or a DeepSearch result creates a safety risk involving a minor so we can prioritize review.

We may update this Policy when the Service, providers, or law changes. We will post the revised version with a new date and provide additional notice when a change materially affects your rights or our use of information. Earlier processing remains governed by the version and law applicable at that time.

Translations are provided for convenience. If a translation conflicts with the English version, the English version controls to the extent permitted by mandatory law. Questions and privacy requests can be sent to support@deepsearch.app. General support is available at support@deepsearch.app.

DeepSearch is operated by RELOAD TECHNOLOGIES - FZCO.