Banyan Tree Design

Privacy Policy

How Banyan Tree Design handles information submitted through the public site, client portal, requests, attachments, notifications, and payment request workflow.

Last updated

May 25, 2026.

This policy describes the current MVP. It is intended to explain what information is collected and why, in practical terms.

Information Collected

Banyan Tree Design may collect information you provide through the public site or portal, including your name, email address, business name, business type, request details, comments, and uploaded request attachments.

The API may also store operational metadata such as timestamps, request status, payment request status, audit events, and basic request metadata used for security and troubleshooting.

How Information Is Used

Information is used to respond to leads, review signups, manage client accounts, handle project and support workflows, process payment requests, send transactional notifications, maintain audit history, and operate the application securely.

Accounts And Sessions

The portal uses account login and secure session cookies. Password handling and session behavior are managed by the authentication system. Banyan Tree Design does not store client passwords in plain text.

Payments

Payments are handled through Stripe Checkout. Banyan Tree Design does not collect or store full payment card numbers. The application stores payment request records and Stripe-related payment status references needed to track payment state.

Attachments And Sensitive Information

Request attachments are stored outside the database, with database records storing metadata and file references. Do not upload passwords, API keys, tokens, private keys, recovery codes, payment card details, or private service credentials.

Service Providers

The application may use service providers for hosting, database storage, authentication support, email notifications, payment processing, source control, backups, logging, or related operations. These providers process information only as needed for the service workflow.

Retention

Business records, audit events, request history, payment request history, and support records may be retained as operational history. Records are generally archived or disabled instead of hard-deleted when they are part of client, payment, or support history.

Your Choices

You can request correction of basic account or intake details through the portal when available, or by contacting Banyan Tree Design. Some records may need to be retained for business, payment, security, or audit reasons.

Contact

Questions about this privacy policy can be sent through the public contact form on the Banyan Tree Design website.