SENTINEL / TRUST CENTER
Privacy notice
A transparent summary of the application’s current data flow. Operator details require review before publication as a final legal notice.
Data submitted for verification
Company names, jurisdictions and identifiers entered in the workspace are processed by the server and may be sent to the applicable official provider. Do not submit unnecessary personal data.
Verification history
Normalized verification records, including submitted company identifiers and returned evidence fields, are stored in the configured application database with a rolling limit of 50 records. Browser-session scoping prevents one visitor from listing or retrieving another visitor’s records and reports. Generated PDF files are created on demand rather than permanently stored as files.
Technical data
Render and the application layers may process standard connection and security logs, including IP address, request path, timestamp and user agent. Loading Google Tag Manager also creates a request to Google’s tag-management service; optional analytics and marketing storage remain denied unless the visitor grants the relevant consent.
Analytics and verification privacy
SENTINEL analytics must not receive company names, VAT or registry identifiers, company-search terms, report contents, email addresses or other verification inputs. The prepared event layer accepts only bounded product metadata such as page type, jurisdiction code and non-sensitive result category after analytics consent.
Cookies and consent preferences
Necessary functionality is always active. Analytics and Advertising / Marketing are optional, unselected by default and can be accepted, rejected or changed later. The choice is stored locally in the browser so SENTINEL can apply it on later pages.
Questions about this page
Contact contact@sentinelentity.com with questions about this document or the current product behavior.