Security & Data Handling Statement

1. Overview

This statement describes the security and data handling measures Arehté has implemented. We do not claim "bank-level security," "100% secure," or that our systems "never fail." No system is perfectly secure. We take reasonable measures to protect your data and are transparent about what those measures are.

2. Authentication and Access Control

• Authentication: User authentication is managed by the Arehté platform, including email/password and Google OAuth. Passwords are not stored in plaintext.
• Session management: Sessions are managed with secure tokens that expire.
• Role-based access: Users have roles (admin, user) that determine what they can access. Admin-only features are restricted to admin-role users.
• Account isolation: User-scoped entities use database row-level security (RLS), while administrative and shared operational entities use role-based policies.

3. Row-Level Security (RLS)

Arehté applies row-level security policies to user-scoped data and role-based restrictions to administrative data. This means:

• Each user can only read, create, update, and delete their own records (keyed by client_id or created_by_id).
• Admin users can access all records for platform management.
• Customer data is not shared between accounts - one user cannot see another user's business profiles, leads, deliverables, or content.
• Entity policies define allowed create, read, update, and delete operations according to ownership and role.

4. OAuth Credentials and API Keys

• OAuth credentials: Third-party credentials are managed through Base44's connector infrastructure and provider OAuth flows. Arehté does not ask users to provide social-media passwords.
• API keys and secrets: All API keys and secrets are stored as environment variables on the server and are never exposed to the frontend or included in client-side code.
• Service-role operations: Sensitive operations that require elevated access (such as payment processing and webhook handling) run as backend functions with service-role access, not as frontend code.

5. Data Encryption

• In transit: The hosted application and supported service connections use HTTPS/TLS where provided by the platform and integration provider.
• At rest: Application data is stored in Base44-managed services and is protected according to the platform provider's security controls.
• File storage: Uploaded files are stored in managed cloud storage with access controls. Before upload, Arehté enforces a 25 MB limit, a safe-format allowlist, matching file extension and MIME type, and file-signature validation. Active content and executable formats are blocked.

6. Webhooks and Browser Output Safety

• Payment events: Arehté currently uses Base44 Payments powered by Wix, not Stripe. Payment events are processed only after RS256 JWT signature verification with the server-held Wix webhook public key. Invalid or malformed signatures are rejected.
• Meta callbacks: Meta deauthorization and deletion callbacks require a valid HMAC-SHA256 signed request before processing.
• Displayed input: React escapes ordinary text output by default. The website-preview generator separately escapes dynamic text before rendering HTML. Uploaded HTML, SVG, and script files are blocked.

7. Audit Logging

Arehté maintains audit logs of significant events, including:

• Terms acceptance and legal acknowledgment events.
• Content approvals, bulk approvals, and rejections.
• Content publishing, outreach sending, and scheduling events.
• Integration connections and disconnections.
• Automation authorization, modification, and revocation.
• Admin actions on client data.
• Agent/system operational events.

Audit logs do not store unnecessary sensitive data. They are retained for security and legal evidence purposes.

8. Admin Privileges

Admin users have elevated access for platform management. Admin-only features include:

• The Owner Command Center and internal studio.
• Client management and catalog management.
• The legal dashboard, integration compliance registry, and risk matrix.
• Audit log access.
• User management and invitations.

Admin access is restricted to users with the admin role. Admin actions are recorded in the audit log.

9. Error Handling and Logging

Arehté logs errors for debugging and improvement purposes. Error messages shown to users are designed to be honest and informative without exposing sensitive system details. Backend functions log errors for debugging without exposing secrets or sensitive data in logs.

10. Data Retention and Deletion

See our Privacy Policy for details on data retention and deletion. You can request account deletion through Privacy & Security in your dashboard or the in-app support assistant. Certain records - including audit logs, legal acceptance records, and billing records - may be retained after deletion for security, accounting, fraud prevention, or legal purposes.

11. Security Limitations

While we take reasonable measures to protect your data, no system is perfectly secure. We cannot guarantee absolute security. You should take appropriate precautions to protect your account, including using strong passwords and not sharing credentials.

12. Incident Response

If we become aware of a security incident, we will investigate and take appropriate action, which may include notifying affected users where required by law or where we believe it is appropriate to do so.

13. Contact

If you have questions about security or data handling, or if you believe you have identified a security vulnerability, please contact us through the in-app support assistant.