How TenderScope handles your data.

Clerk manages account registration, authentication, sessions and the associated account information. TenderScope receives the Clerk user identifier and authentication state needed to recognize a signed-in user. TenderScope does not intentionally copy authentication credentials or session tokens into its application database.

For signed-in users, TenderScope stores the Clerk user identifier, saved tender identifiers, saved-search names and filter criteria. For each saved search, it may also store whether daily alerts are enabled and the time they were enabled.

Older browser-local saves are imported only after confirmation. A successful import removes only TenderScope’s two legacy save keys; choosing Not now or encountering an error leaves them unchanged.

Daily alerts are opt-in for each saved search. To prepare a requested digest, TenderScope matches the saved criteria against newly added tenders and stores operational digest, claim, attempt, failure and delivery metadata. This can include identifiers, synchronization and status information, request hashes, provider acceptance identifiers, error codes and timestamps used for deduplication, retries and safe delivery handling.

When an alert needs to be sent, TenderScope asks Clerk for the account's verified primary email address and uses that address to deliver the message through Resend. Resend receives the recipient address and digest content needed to provide that delivery. TenderScope does not intentionally persist the resolved recipient email in its own application database. Clerk and Resend nevertheless process the address as service providers. Daily alerts are scheduled notifications, and delivery is not guaranteed.

This information is processed to authenticate users, synchronize saved preferences across signed-in devices, match saved searches to newly added tenders, send requested daily digests, prevent duplicate delivery, manage retries and failures, protect against abuse, and maintain operational reliability.

Ordinary server and hosting logs may process an IP address, user agent, request URL, timestamp and diagnostic information to deliver, secure and troubleshoot the service. TenderScope also uses limited aggregate usage and performance measurements through Vercel Web Analytics and Speed Insights. Retention depends on the relevant service and infrastructure configuration; this notice does not assign a fixed retention period.

No advertising trackers are intentionally installed. No payment information is currently processed because TenderScope does not offer paid subscriptions or checkout.

TenderScope uses Clerk for authentication and verified-email lookup, Resend for alert delivery, Neon/PostgreSQL for application data, and Vercel for hosting and operational measurements. GitHub Actions is used to initiate scheduled TED synchronization and alert processing. These providers process information under their own terms and privacy practices.

Tender information is transformed from official TED procurement data. Links to official TED notices and other external destinations are governed by the destination service's policies.

Alerts can be enabled or disabled separately for each saved search. Deleting a saved search removes its name, criteria and alert setting, together with the associated alert claim and delivery rows linked to that search. User-and-run-level operational digest records may remain after those linked rows are removed.

Saved tenders and saved searches can be removed through their respective pages. Account and sign-in options supported by Clerk are available on the TenderScope Account page. For other access, deletion or privacy requests concerning TenderScope application data, use the Feedback link in the site footer. Account deletion through Clerk should not be assumed to automatically remove separately stored TenderScope saved data.

This notice will be updated when product behavior or infrastructure changes. The effective date will change when a revised notice is published.