COMMUNITY ALLIANCE AI · RICHMOND

Privacy

Community Alliance AI separates public community identity from private account information and limits access to what is needed to operate the service.

Public community profile

Your display name, community, and information you choose to publish—such as posts, help offers, resources, business listings, events, or organization details—may be visible to other users according to each item’s visibility settings.

Private identity information

Email, phone, legal name, postal code, address, and similar account or verification data are not part of the public profile. Authorized access to private identity data is restricted by policy and recorded in the audit log with a reason.

Payments and credits

Credit purchases are processed through Stripe or PayPal. The application stores payment order, provider reference, amount, currency, status, and credit-ledger records needed to reconcile a purchase; it is not designed to store full payment-card details.

AI features

When you use AI-assisted features, the minimum content needed for that request may be sent to the configured AI provider. Do not place passwords, payment secrets, or unnecessary private identity information in AI prompts. Failed paid AI operations must not deduct credits.

Safety, moderation and audit

Reports, moderation decisions, privileged credit changes, private-identity access, and other sensitive administrative actions may be recorded in audit logs for accountability and abuse prevention. Audit logs must not contain passwords or provider secrets.

Your controls

Use your profile and account-management pages to review or update available account information and security settings. Visibility controls on community content determine what you intentionally share. Account actions remain subject to safety, audit, and record-retention requirements.

Security practices

The service uses account confirmation, anti-forgery protection, authorization policies, secure cookies, HTTPS, rate limiting, and audit controls. Administrative access to sensitive functions requires the appropriate role and multi-factor authentication where configured by policy.

V1.0 privacy summary · Updated September 2026