Account and security

Authentication and account identity

TrendRise uses an authentication provider for sign-in and account identity. The app maps that authenticated identity to an internal user record, default workspace, membership role, billing state, credit balance, saved opportunities, and workflow history.

• Use the same email when signing in, applying for partner access, or contacting support.
• Avoid shared credentials; invite team members or use workspace roles when those controls are available.
• If account identity or workspace ownership looks wrong, contact support before changing billing or deleting data.

Workspaces and roles

Workspaces are the boundary for most customer product data. Workspace records can include saved opportunities, product profiles, launch batches, creator prospects, deal records, analytics context, subscription state, and credit balance.

• Owners and admins should manage billing and sensitive workspace settings.
• Members may have limited access depending on the feature and role implementation.
• User-private connectors and uploads should remain scoped to the workspace or account that authorized them.

Provider-managed sensitive data

TrendRise should avoid storing sensitive provider data it does not need. Payment methods are handled by Stripe. Authentication credentials are handled by the auth provider. Partner payout identity, tax, and bank details are handled by Stripe Connect when that flow is used.

• TrendRise stores provider references and status where needed, such as customer ids, subscription ids, connected account ids, and readiness state.
• Do not send passwords, API keys, bank details, identity documents, SSNs, private keys, or webhook secrets through support email or public channels.
• If a secret is accidentally exposed, rotate it with the provider and contact security support.

Connected accounts and exports

Future and optional connectors can include Stripe, Shopify, Gumroad-like revenue exports, Google/Meta Ads, YouTube, Etsy, or uploaded CSV files. These should be connected only through authorized flows or user-provided exports.

• User-private revenue or ad data should not be reused as another customer's public source signal.
• Revoking access may require disconnecting through TrendRise and the provider account.
• Uploaded or connected data can still be retained where needed for billing, legal, security, fraud-prevention, or operational records.

Account changes and deletion

Some profile and settings changes may route to provider-managed account screens or support while the account system matures. Account deletion and privacy requests should be handled carefully because billing records, security logs, and legal records may have retention requirements.

Security reports

Send security-sensitive issues to security@trendrise.io with enough detail to reproduce or assess the issue. Do not include secrets in public channels.

• Useful reports include the affected URL, workspace context, steps to reproduce, expected behavior, actual behavior, and screenshots without secrets.
• Avoid testing against accounts, workspaces, or data you do not own or have permission to access.
• If a report involves customer-sensitive data, summarize the exposure without copying unnecessary personal information.

Support escalation

Use support@trendrise.io for product support, billing@trendrise.io for invoices, plans, payment issues, refunds, or credits, privacy@trendrise.io for privacy requests, legal@trendrise.io for legal notices, and security@trendrise.io for vulnerabilities or account-security concerns.

Privacy requests

Privacy requests should go to privacy@trendrise.io. Some records may need to be retained for billing, security, legal, fraud-prevention, partner attribution, dispute review, tax, or operational reasons.