Privacy baseline
Collect less. Explain more.
Public browsing requires no account. RaiseFeed Professional uses a minimal, organization-scoped identity. Candidate data is processed only when the separately gated candidate product is enabled and the candidate gives the required consent.
Founderr Pulse subscription
RaiseFeed does not run a parallel newsletter list. Newsletter signup, consent, and unsubscribe are handled through the existing Founderr Pulse subscription flow.
Public-source data
Job records and company events retain source URLs, timestamps, and confidence state. Publicly filed names are never automatically relabeled as founders, buyers, or sales contacts.
Product measurement
Analytics stores only an allowlisted event name, route category, and optional public evidence ID. It does not store a visitor ID, email, search text, CV data, or arbitrary event properties.
Professional workspace
RaiseFeed stores member identity, membership, consent versions, workspace decisions, and explicit access evidence. One-time sign-in tokens are stored only as hashes. Transactional email records contain recipient, purpose, delivery state, and provider identity, never rendered bodies. IP addresses and user agents are not stored in RaiseFeed product data.
Subscription billing
Stripe processes cards, billing addresses, supported tax IDs, subscriptions, invoices, refunds, and disputes. RaiseFeed stores only the provider identities and amounts needed to reconcile paid access and accounting evidence. Raw Stripe webhook bodies, card numbers, full billing addresses, and tax IDs are not retained by RaiseFeed.
Candidate product remains off
Candidate verification, profiles, documents, matching, alerts, exports, and retention workers are not provisioned. No local candidate account, match rating, document, vector, or session is included in the production seed. The implementation remains separately gated by privacy and usefulness review.