Privacy policy
How OpenInsider processes personal data about visitors, account holders and people named in public regulatory records.
Who is responsible
Pablo Reyes Almagro is the controller of personal data processed for OpenInsider. Contact: contact@openinsider.eu. Postal address: C/ Montebiarritz 45, Casa 16, 29688 Estepona, Málaga, Spain. OpenInsider is a project operated in his own name, not a separate incorporated company.
Accounts and saved research
When you create or use an account, we process your email address, profile information you provide, authentication identifier, account status, preferences, saved research and service-use records. Clerk handles authentication, credentials and sessions. If you choose Google sign-in, the flow supplies basic account details, such as your email address, name and profile image, according to the permissions shown. Passwords are handled by Clerk and are not stored in OpenInsider’s application account records.
Subscriptions and payments
OpenInsider uses account status and service entitlements to control access. A payment provider has not yet been selected and paid checkout is not yet available. Before accepting payments, we will identify the contracting seller and payment provider and explain the billing data they and OpenInsider process. No payment provider is appointed by this policy.
Support and service messages
If you contact us, we process your contact details, message and any information needed to answer it. We send messages needed to operate your account, such as security notices and important service updates, and billing messages when paid subscriptions become available. These messages are not a newsletter or promotional mailing. We do not sell personal contact data or use the service for advertising profiles.
People named in public regulatory records
We obtain names, publicly disclosed professional roles or relationships, issuer links and transaction details from official regulatory publications, including CNMV and AMF for the markets shown as available. These people need not have an OpenInsider account. We use the data to make filings searchable, normalize records, link evidence, explain activity and correct errors. Permitted fields are disclosed to website visitors and authorized API users. Public pages may be indexed by search engines. Private support correspondence and identity evidence submitted with rights requests are not public.
Profiles and derived analysis
We organize disclosures into profiles, relationships, activity measures and rankings using the published methodology. Some automated analysis may constitute profiling. Results depend on available records, matching rules, observation periods and data quality. A matching name does not prove identity, and a score or recommendation does not establish intent, wrongdoing or future performance. This research is not intended for contact prospecting or sensitive-trait inference.
Purposes and legal bases
Requested account features and pre-contract steps rely on performance of a contract or steps you request before entering one (GDPR Article 6(1)(b)). Necessary security and abuse prevention rely on legitimate interests in protecting the service and its users (Article 6(1)(f)). Public-record research and derived analysis rely on legitimate interests in making official market disclosures searchable, verifiable and understandable, subject to necessity, proportionality and the rights of the people concerned. General correspondence relies on the interest in answering inquiries or, where appropriate, requested pre-contract steps. Records required by applicable law are processed on that basis (Article 6(1)(c)). Optional analytics relies on consent (Article 6(1)(a)).
Analytics and device information
With your consent, Google Analytics 4 measures use of the public website. Analytics can involve connection and device information, cookie identifiers, page paths, titles and interaction events. OpenInsider’s own event helpers exclude query strings, fragments, referrers and raw search terms. This does not mean that every field sent to Google is anonymous: public entity paths and page titles can identify people. Account and authentication pages are excluded from application analytics. See the Cookie policy for your choices.
Recipients and external resources
Providers support authentication (Clerk), hosting (Railway), consented analytics (Google) and email handling (our email provider). Google also handles Google sign-in when you choose it. Providers have different roles: some process data on our instructions and some have independent privacy responsibilities. Loading issuer logos from logo.dev can send connection metadata, including your IP address, to that provider. Public regulatory fields are available to visitors and permitted service users. Billing recipients will be identified before paid checkout becomes available.
International transfers
Some providers are based in the United States or may process data outside the European Economic Area. International transfers are subject to the GDPR’s transfer requirements, which may involve an applicable adequacy decision or appropriate safeguards such as standard contractual clauses. Contact contact@openinsider.eu for information about the recipients, relevant destinations and applicable safeguards, including how to obtain a copy where available. Analytics consent is not a general substitute for transfer safeguards.
Retention of account, support and backup data
Our approved retention policy sets these targets: delete account data and saved research within 30 days of a valid erasure request; keep support correspondence for no more than 24 months after the inquiry closes; remove launch-waitlist entries when their purpose ends; and rotate backup copies within 35 days. These are policy targets, not a guarantee that every deletion is automatic. Specific records may be retained where required by law or necessary for a justified legal claim, with restricted access and review when that justification ends. Contact us to request account closure or erasure.
Regulatory history, logs and corrections
Public regulatory history is retained while needed for the stated research and verification purposes, subject to periodic review and individual rights. Closing an account does not by itself erase separate regulatory records. Internal evidence retention does not require every version to remain public. Corrections preserve provenance rather than silently replacing earlier evidence. Our technical-log policy sets a 90-day baseline, except for justified incident investigation or required retention; this is not a guarantee of automatic deletion.
Your rights and choices
Depending on the processing, you may request access, rectification, erasure, restriction or portability, and object to processing based on legitimate interests. Withdraw analytics consent through Cookie settings; withdrawal does not affect earlier lawful processing. Write to contact@openinsider.eu with the affected data or record URL and the outcome you request. We normally respond within one month. If a legally permitted extension is needed, we explain it within that period. Public-source data is not an automatic reason to refuse a request.
Requests and identity verification
Privacy requests and supporting evidence are handled privately. We ask only for identity information necessary to handle the request; do not send identity documents unless specifically requested. Errors in an official filing may require correction by the authority. We separately examine extraction, classification, identity-linking and other errors introduced by OpenInsider, including requests to restrict or erase an affected public projection.
Children
Public research can be read at any age. Account holders under 18 need authorization from a parent or legal representative. An adult must enter into and manage a paid subscription. Contact contact@openinsider.eu before setting up a minor’s account or for requests involving a child’s data. Identity-document copies are not a routine condition of public access.
Changes to this policy
We update this policy when our processing changes and show the editorial revision date. We obtain new consent where a change requires it; publication of an update or continued browsing does not itself create consent.
Complaints
You may complain to the Agencia Española de Protección de Datos (AEPD) or another competent supervisory authority, including in the EEA country where you habitually live or work or where an alleged infringement occurred.