Privacy Policy

Sentinel is the controller of the personal data described in this policy. Sentinel is operated independently and is not currently incorporated as a company; the operator is the individual who provides the service.

For any privacy question or request, including the rights set out in §8, contact privacy@sentineltrade.net.

Account data. Your email address and an account identifier. If you sign in with Google we receive your email address and basic profile information from Google; we do not receive your Google password.

Credentials you supply. API keys for market-data providers, an AI key if you enable the Advisor, and broker API keys if you connect a portfolio. These are stored encrypted (see §5) and used only to read data.

Portfolio data. Holdings you add by hand or sync from a connected broker: symbols, share counts and average cost. They power the portfolio view and the sell-signal emails.

Preferences. Halal mode and your Shari'ah screening defaults, focus sectors, theme, watchlist, price alerts, and your email choices.

Emails we send. Sell-signal alerts when a holding turns Sell (on unless you switch them off) and the daily market highlights (off unless you switch them on). Every email has an unsubscribe link, and both can be changed in Settings.

Activity generated by the product. Rating snapshots: what the engine said about a company and when. This exists so its past calls can be scored against what actually happened, and so the engine can be held to account for its own output.

Technical data. Standard server logs, including IP address and request paths, retained for security and abuse prevention.

What we do not collect. No analytics, no advertising identifiers, no behavioural tracking, and no third-party tracking scripts.

Cookies and browser storage. Nothing on Sentinel is used for tracking or advertising. The app keeps you signed in with a session token stored in your browser, and remembers local preferences such as theme. Cloudflare, which protects this site, may set one security cookie (__cf_bm) to tell people apart from automated traffic; it expires after 30 minutes of inactivity, is not linked to your account and is not used to track you between sites. All of these are strictly necessary for the service to work and be secure, so they do not need your consent.

Performance of a contract. Providing the account and running the ratings, screens, portfolio and alerts you ask for.

Legitimate interests. Keeping the service secure, preventing abuse, and diagnosing faults, balanced against your interests, which is why logging is limited to what is needed.

Consent. The daily market highlights email, which you can withdraw at any time.

Legal obligation. Where we are required to retain or disclose data by law.

The application runs on a server operated by Sentinel in the United Kingdom. We use the following processors and services:

• Supabase: authentication and account storage.
• Google: sign-in if you use Google, delivery of the emails we send, and the AI Advisor if you enable it. When you use the Advisor, your question and the engine context relevant to it are sent to the AI provider.
• Cloudflare: hosting of this website, and the secure connection that carries traffic to the application server.
• Your broker, if you connect one: Sentinel calls its API with your key to read your positions.
• Data providers, including SEC EDGAR, FINRA and commercial market-data providers. These receive ticker symbols, not your identity.

Company logos are fetched by our server and cached, never loaded directly by your browser, so the logo provider never learns which companies you are looking at.

We do not sell your data, and we do not share it for advertising.

Keys are encrypted at rest (broker keys with AES-256-GCM), and each account can only read its own data. Keys are never returned to the browser: the settings screen shows a masked preview and a configured flag, never the value.

This is server-side encryption, not end-to-end encryption. The encryption key is held by the server, which is what allows your credentials to follow you between devices. It also means an operator with both database access and key access could decrypt them. We state this plainly rather than implying a guarantee we cannot make.

If that trade-off is unacceptable to you, use read-only broker keys, or do not connect a broker.

Some processors listed above operate outside the UK and EEA. Where data is transferred internationally it is done under an adequacy decision or Standard Contractual Clauses, as applicable to that provider.

Account, credentials, holdings and settings: for as long as your account exists, and deleted when you delete it.

Rating snapshots and decision logs: retained because they are what makes the engine auditable. They record what the engine said about companies, not about you. You can ask us to delete anything linked to your account.

Server logs: a rolling window, typically no more than 90 days.

Under UK GDPR you have the right to access your data, to have it corrected, to have it erased, to restrict or object to processing, and to receive it in a portable format. You can withdraw consent where consent is the basis for processing.

Write to privacy@sentineltrade.net and we will respond within one month. If you are not satisfied with how we handle a request, you can complain to the Information Commissioner's Office at ico.org.uk.

Sentinel can be used by anyone aged 13 or over. Young users get exactly the same protections as everyone else: no advertising, no analytics, no profiling and no tracking, and we collect only what is needed to run the account.

We do not knowingly allow anyone under 13 to create an account. If we learn that one has, we will close the account and delete its data. A parent or guardian who believes this has happened can write to privacy@sentineltrade.net.

If a breach occurs that is likely to result in a risk to your rights and freedoms, we will notify the relevant supervisory authority within 72 hours and tell you without undue delay where the risk is high.

We will post any update here with a revised date, and give notice by email where the change is material.

See also our Terms of Service and Disclaimers.