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 responsible-use notice
Remote execution remains under your control
Policies control. This page is a transparency summary. The Privacy Policy and Terms of Service govern use of Agent Remote™.
Review before execution. AI-generated code and commands can be insecure, destructive, or incorrect. Review changes, maintain backups, and use least privilege.
Authorized access only. Connect only repositories, machines, accounts, and data you are authorized to administer.
No professional assurance. Output is not a security audit, legal opinion, compliance certification, or guarantee that software is production-ready.
Security and vendors. Safeguards reduce risk but cannot guarantee absolute security. Selected providers may process task context needed for your request.
Names and marks. Agent Remote™ 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.