Security
Last updated: November 5, 2026
Zapfeed is the feedback, roadmap, and help-center platform operated by Applifyer, LLC, 131 Continental Dr, Suite 305, Newark, DE 19713, United States. This page covers how we protect the boards, posts, votes, attachments, and integration credentials you put on the Service.
Found a vulnerability? Contact us. Include the URL, the affected board or endpoint, and what you observed. Please send sensitive details privately rather than opening a public issue.
Sign-in and sessions
You can sign in with Google, a one-time email code, or an email address and password. Passwords are stored as salted scrypt hashes. Email sign-in codes expire after ten minutes and can be redeemed once. Password registration does not mark an email address as verified; features that depend on a verified address check that separately.
Sessions are stored in the database and revoked on sign-out. Session cookies use HttpOnly and SameSite=Lax, with Secure enabled on HTTPS. On a verified custom domain, sign-in uses a single-use handoff token bound to that hostname.
Tenant and content isolation
Every board belongs to exactly one organization. Queries on the public integration surface are built from a scope clause derived from the authenticated credential rather than from caller input, so a key issued for one organization cannot read or write another’s posts, and extra filters cannot widen that scope. A key created with a board restriction reaches only that board.
Visibility is enforced per board and per post. Private boards are visible to members of the owning organization. Private posts are visible to organization staff and to signed-in users whose verified email sits on one of the organization’s internal domains. Paid organizations can also run a members-only roadmap and help center, and can restrict signed-in members to their own posts.
API keys and integrations
API keys authorize both the REST surface and the MCP server. Each is generated from 24 cryptographically random bytes; only the SHA-256 hash is stored, the plaintext is shown once at creation, and a short non-secret prefix is kept so you can recognize a key without exposing it.
- Revocation is immediate. Authentication rejects any key carrying a revocation timestamp. Only an organization admin can revoke, and only a key belonging to an organization they administer.
- Entitlements are re-checked on every call, so API and MCP access ends as soon as the organization’s plan no longer includes it, without waiting for keys to be cleaned up.
- Each key has its own rate limit (300 requests per hour by default, adjustable), with a temporary block after repeated violations.
Browser calls to the integration endpoints are answered for a configured allowlist: Zapfeed’s own hosts, verified customer domains, and domains we explicitly configure for cross-origin access. That allowlist decides only which browser may make the call; the API key is what decides what the caller can see.
Uploads
Attachments are checked against allowed file types and size limits, with content signatures checked for supported binary formats. Text formats such as TXT and CSV have no reliable signature, so for those the allowlist and size cap are what we enforce. Files are stored under generated filenames whose extension comes from our own type map rather than the uploaded name. Files land in Cloudflare R2; anything that is not an image or video is stored with a download disposition so it cannot render inline.
Data in transit and hosting
The Service is served over HTTPS. The application’s connection to its PostgreSQL database requires TLS with strict server-certificate validation and presents a client certificate as well, so both sides authenticate each other. Production and staging run on separate databases with separate passwords and separate client certificates, and schema migrations are applied over verified mutual TLS.
The application runs on Cloudflare Containers constrained to the European jurisdiction and the WEUR region. The PostgreSQL 16 database runs on Google Cloud in Belgium, as do our self-hosted analytics and error tracking. The analytics we run is cookie-free, honors Do Not Track, and records page paths without query strings or URL fragments.
Backups
A scheduled job takes private recovery copies of the database and stored objects daily. Those copies are not write-only: we verify them with readbacks, and we have restored a database dump and exported object archives onto separate infrastructure to prove the recovery path works. Releases are published blue/green, with the new release validated before traffic moves to it.
Sub-processors
We keep the dependency surface small and name it plainly: Resend delivers transactional email including sign-in codes, Cloudflare provides Containers, R2 storage, DNS and the edge, Stripe processes card payments, and Google Cloud hosts the database plus our self-hosted analytics and error tracking. The Privacy Policy records what each of them receives.
Procurement requirements
If your purchase needs specific controls — data residency, contractual terms, a security questionnaire, or a review of our subprocessors — send the requirement list and we will answer against what is implemented today.
Talk to us about security questions, questionnaires, and data-handling requests. For the legal side of the same relationship, see the Privacy Policy and the Terms & Conditions.