Deplomo Cloud privacy policy

• Account and identity: Name, phone number, email, national identity number or company registration details, and verification results, only as needed to create accounts, provide services and meet legal requirements.
• Payment and billing: Transactions, invoices, wallet balance, usage and information needed for refunds. Payment gateways process full card details; Deplomo does not store them.
• Usage and security: IP address, request time, browser and device, login events, administrative activity, resource usage, errors and traffic data needed for security, billing and troubleshooting.
• Projects and services: Project names, environment settings, domains, service and volume specifications, variables, build and runtime logs, releases, backups and add-on connection details.
• Source code and development integrations: When deploying from Git or CLI, the platform receives code, Dockerfiles, dependency manifests and files needed for the build. Git connections also process repository IDs and the access tokens needed for the selected operation.
• Communications with Deplomo: Tickets, messages, attachments, support calls, abuse reports and notification preferences.

Deplomo does not sell personal data or project content. Information is shared only to the extent necessary with the following groups:

• Infrastructure, data center, payment, SMS, email, identity verification, Git and support providers needed to deliver the selected feature.
• Project members based on roles and access levels defined by the project owner or manager.
• Competent judicial or legal authority, when a valid and enforceable request is received, or to the extent necessary to defend the rights and security of users and the infrastructure.
• During a merger, business transfer or change of ownership, subject to confidentiality and appropriate notice before changes affect user rights.

Workloads and their data are hosted in the selected execution location. Some account, billing, support and operational control data may be processed separately at essential providers' locations.

• We retain data as long as needed for service delivery, security, financial settlement, disputes or legal obligations. Retention periods vary by data and service type.
• After a service or account is deleted, data is removed from active systems or normal access. Backups and legally required records remain in restricted, nonpublic storage until their retention period ends, then are deleted.
• Hosting and computer crime laws may require the retention of certain user data after subscription termination and certain traffic data or content changes for a specified period. During this time, their use is limited to the same legal purpose.
• Deleting a resource may be immediate and irreversible. Export or back up what you need before deleting a service, volume, add-on or environment.

• Dashboard and API connections use TLS. Passwords are stored as one-way hashes; cryptographic controls and restricted access protect tokens and secrets.
• User services are isolated, and staff access to operational systems is restricted by role, job requirements and activity logging.
• No system is completely secure. Deplomo maintains appropriate technical and organizational controls and notifies users of incidents affecting their information according to legal requirements and the incident's severity.

The site and dashboard use cookies or local storage for sign-in, security, language, theme and essential preferences. Google Tag Manager loads automatically and may process visit data according to its container configuration. Consent controls are not currently enabled.

• View your profile and project members in the dashboard and update editable information.
• Revoke a Git connection, token, SSH key, domain, or member access that is no longer needed.
• Manage optional notifications. Security, billing and essential account messages cannot be disabled.
• In Settings → Privacy, download your account data as JSON or submit a trackable request for access, transfer, correction, deletion, restriction or objection. Our operational target is to respond within one month. If we need more time, we will explain why through the ticket. Requests remain subject to identity verification and the existing retention conditions described here.

If your application collects other people's data, you determine its purpose and processing method. You are responsible for notices, necessary consent, data-subject requests and access controls. Deplomo processes it only to provide infrastructure according to your settings and requests, unless the law requires otherwise.