Data we use

Startup records use public or authorized sources such as company websites, investor announcements, public registries, and public product pages.

Founder information is limited to public professional background when it is relevant to understanding the company record.

Alynt stores source summaries, review decisions, weekly release records, correction requests, deletion requests, and operational audit records needed to maintain the product.

Controls

Correction and deletion requests enter editor review before public records are changed. Admin access is session-gated and production admin actions require audit logging.

Production accounts, analytics, email, and third-party services must stay covered by the approved launch configuration and the public request paths.

Accounts

Registered-user features can use Google sign-in through Clerk when production keys are configured. Alynt uses the authenticated session to operate watchlists, saved searches, and weekly subscriptions.

Alynt does not ask users to submit private personal data inside company corrections, deletion requests, saved searches, or watchlist notes.

Requests

Public correction and deletion requests are routed to editor review. Requests should identify the public record at issue and avoid including sensitive personal data.

Use corrections for factual updates and deletion requests for removal or suppression review.