Privacy
Privacy Notice
How RequestFlow handles early-access interest, website analytics, and follow-up information during beta.
Last updated: June 9, 2026
Plain-language scope
This notice covers the public RequestFlow website and early-access form. The public site is not a place to upload sensitive client documents. A production customer privacy agreement or data processing addendum may be added before paid customer use.
Information we collect
When you request early access, we collect the information you choose to submit, such as your name, work email, firm name, website, role, firm type, active-client range, current document collection method, likely plan fit, beta priority, and description of your document collection pain.
- The form also captures basic attribution fields such as page URL, referrer, UTM values, timezone, screen size, and lightweight engagement events.
- We use Google Analytics to understand aggregate website traffic and conversion behavior.
- Do not submit sensitive client documents, tax records, payroll files, bank statements, or regulated client data through the early-access form.
How we use information
We use early-access information to understand firm fit, reply to beta requests, prioritize product work, and measure which pages and campaigns are creating useful interest.
- We may contact you about RequestFlow beta availability, founder pricing, product updates, or questions about your submitted workflow.
- We may use aggregate analytics to improve site pages, SEO/GEO positioning, and conversion paths.
- We do not sell early-access submissions.
Storage and protection
Current beta-interest submissions are stored in a Supabase project in us-west-2, with a server-side JSONL fallback audit trail for successful submissions. Browser traffic to request-flow.com uses HTTPS.
- Secrets such as API keys are not embedded in public pages.
- Public Data API access is limited to insert behavior for the beta-interest table; public visitors are not granted table read access.
- Signup notifications may be sent through Resend when notification configuration is active.
Service providers
RequestFlow uses a small set of providers to operate the public site, receive beta-interest submissions, send signup alerts, and measure aggregate traffic.
- Supabase stores beta-interest submissions.
- Resend may send signup notification emails to RequestFlow.
- Google Analytics measures aggregate website and conversion behavior.
- Website hosting and server infrastructure serve public pages and the capture endpoint.
Retention and deletion
We keep beta-interest records while evaluating and following up with potential beta users. You can ask us to delete your early-access submission.
- Deletion requests can be sent to cal6542@gmail.com.
- Some server logs or backup records may persist for a limited operational period.
- Customer data retention for live product use should be documented separately before paid customer use.
Changes to this notice
RequestFlow is in beta, so privacy and data-handling details may change as the product moves toward customer use.
- Material changes should be reflected on this page.
- A separate customer agreement, data processing addendum, or security packet may apply before live client-document use.
Questions before joining the beta?
Send your privacy, terms, or security requirements through the early-access flow so we can route the right follow-up.