AI usage
Use AI for drafts, summaries, recommendations, exports, and workflow automation where it helps the user.
AI Trust Center
Make trust part of every SaaS you launch.
This starter includes a reusable Trust Center pattern for AI-powered SaaS products. It gives customers a clear explanation of privacy, data handling, model usage, billing, and the human review process.
Data handling
Use Supabase behind server-side routes for customer records, saved projects, and admin reporting.
Payments
Use Stripe for checkout and subscriptions; store access state, not raw payment credentials.
User inputs
Prompts, form fields, project details, files or text intentionally submitted by the user.
Generated output
Draft copy, recommendations, exports, saved projects, and workflow summaries.
Account records
Login identity, subscription access, saved settings, projects, and support context.
Billing records
Stripe customer IDs, subscription state, invoice status, and webhook event references.
Legal and marketing notice
You control the claims and audiences in your funnels
Policies control. This page is a transparency summary. The Privacy Policy and Terms of Service govern use of FunnelFlow™.
AI requires review. Generated copy, offers, targeting suggestions, and forecasts may be inaccurate and do not guarantee traffic, conversion, or revenue.
Marketing compliance. You are responsible for substantiating claims, material disclosures, opt-outs, consent, and advertising and communications rules.
Content rights. Use only content, testimonials, images, lists, and brand assets you are authorized to use.
Security and vendors. Safeguards reduce risk but cannot guarantee absolute security. Connected processors may receive limited data required for requested features.
Names and marks. FunnelFlow™ and DVGProOS™ are claimed trademarks. Third-party marks belong to their respective owners.
Production standard
Replace placeholders with product-specific policy before launch.
Every cloned SaaS should update this page with exact data fields, retention rules, subprocessors, deletion workflows, model providers, and support contact details before collecting live customer data.