Permissions with boundaries
The private preview includes workspace/store access checks, roles, owner MFA and scoped invitations. The publishing model uses fingerprinted proposals, source versions and approval expiry. These implementations do not establish that all production controls are complete.
Customer control over changes
Manual publishing approval is the default. Sensitive changes require manual review. Approved automation must stay within explicit permissions and budgets; AI cannot expand its own authority.
USA storage at launch
USA-only application content storage is the accepted launch direction. EU workspace activation requires additional validation. Provider locations, backups, encryption, deletion and transfer safeguards need verification before a production assurance can be made.
Reliability and assurance
Availability and recovery figures in the specification are internal design targets, not contractual guarantees. No certification, external audit result or staffed response commitment is claimed here. The production security measures and incident procedures remain to be validated.
Report a concern
Email security@feedrevive.com with a description, affected area and safe reproduction steps. Avoid sending customer data or secrets in the initial report. Coordinated disclosure terms and response windows remain to be published.
For privacy enquiries, use privacy@feedrevive.com.
Know which boundary you are reviewing
This marketing site serves static pages and locally hosted images. Its contact form sends submitted details through a Vercel function and Resend to our enquiry mailbox. The endpoint validates input, limits payload size and uses a signed form token, honeypot and temporary request limits to reduce abuse. Its optional browser preference is separate from store authorization and application authentication.
The private application preview is a different surface with workspace/store access checks and catalog processing. A control demonstrated in a development environment is not a claim that every public production configuration, supplier contract or operational process has been accepted.
Questions before connecting a store
- Which store and workspace is the access for, and who is authorized to grant it?
- What data is read, where is it processed and which permissions are actually required?
- How are access changes, retention, deletion and supplier responsibilities handled?
- Does the proposed action only review data, or can it change a source?
The private preview’s read-only import must not be confused with planned source publishing. Ask for the scope and current evidence relevant to your evaluation. Read the privacy draft, supplier register draft and DPA draft alongside this overview; these documents still need completion before public launch.