arvumiUpdated November 3, 2026. Arvumi, Pennsylvania, United States, operates this beta. Email support@arvumi.com about privacy, access to your information, or deletion requests. This page describes service practices; it is not a certification of legal or regulatory compliance.
Account and access information
Arvumi records your GitHub user ID, login, available email address and verification status, account creation time, sessions, API-key records, team membership, and repository access grants. GitHub supplies sign-in and repository authorization. Arvumi uses this information to authenticate you, enforce permissions, connect repositories, and deliver service and billing notices.
The dashboard uses session cookies for sign-in. API keys authorize CLI and compatible client access. Protect these credentials and revoke access you no longer need.
Repositories and application content
To deploy your application, Arvumi processes repository identifiers, commits, authorized source checkouts, build configuration, dependencies, artifacts, domains, and environment variables. It stores and serves deployment output and processes function requests and responses. Managed databases contain the data you or your application put in them.
Environment-variable secrets and managed database passwords use encrypted storage in the control plane, and must be decrypted for authorized execution or access. This does not make all application data or logs encrypted secrets. Source files, build output, application logs, and customer-published content can expose information you include in them. Avoid logging credentials, tokens, or sensitive request bodies.
Usage, logs, and billing
Arvumi records deployment and build history, build and runtime output, request and response-delivery measurements, function timing and resource usage, operational and security events, and service errors. It uses these records to operate and troubleshoot the platform, enforce capacity and access, investigate abuse, and calculate charges. Request metadata can include hostnames, paths, timestamps, and network addresses. Data you put in application URLs or logs may therefore appear in operational records.
Billing records include team and provider identifiers, subscriptions, invoices, payment status, usage assessments, notices, and accounting history. Stripe processes payment-card information through its hosted payment flows; do not send payment-card information to Arvumi support.
Who processes information
Arvumi uses GitHub for identity and repository access, Stripe for payments, and infrastructure, storage, network, and email services to host and operate the platform and send service notices. These providers process the information needed for their functions. Authorized operators may access service data for support, recovery, security, billing, and abuse handling. Team membership and repository grants determine which dashboard and project operations other team members can perform.
Your deployed websites and endpoints may be public, including when their source repository is private. You control the information your application collects and shares and are responsible for informing its users. Arvumi’s own account controls do not add authentication to your application.
Retention and deletion
Retention depends on the record and operational need; Arvumi does not promise a fixed deletion schedule during beta. Removing a resource from the dashboard does not guarantee immediate erasure from backups, operational logs, billing history, or security records. Backups are used for recovery and may retain earlier copies.
Anti-abuse team-creation receipts retain the GitHub user ID, team UUID, and creation timestamp. These receipts survive team deletion and account recreation so creation limits cannot be reset. No automatic expiry or deletion period is promised for these receipts. The rolling 30-day allowance is a creation limit, not a retention period. Accounting and usage evidence may also remain after team closure.
Contact support to request access, correction, or deletion of information or closure of an account. Arvumi may verify your identity and team authority. Some records may need to remain for accounting, fraud prevention, security, dispute resolution, or recovery. Export the application data you need before deleting resources.
Your choices and questions
Manage team access and API keys in the dashboard, change or remove deployments and variables, and revoke the GitHub App’s repository access in GitHub. Revocation stops future authorized checkouts; it does not remove already deployed content. Use Stripe’s hosted portal from Billing to manage payment details and subscriptions. Contact support for requests the dashboard does not provide.