This policy applies to the public website and the Backup Manager application. The actual information processed depends on how an administrator configures and uses a deployment.
1. Information that may be involved
Depending on the features you use, information may include account identifiers such as names and email addresses; role and permission information; database profile and backup-target configuration; credentials entered to enable those operations; backup run status and history; schedule details; project records and task information; and technical or security logs generated by the application.
When you submit a contact form, the information you provide may include your name, email address, organization, inquiry category, subject, message, and an optional non-sensitive record reference. Do not send passwords, encryption passphrases, API tokens, private keys, payment credentials, or other secrets through the public forms.
2. How information may be used
Information may be used to authenticate users, apply access permissions, configure and run requested backup operations, maintain operational history, organize project work, protect the service against misuse, troubleshoot problems, and respond to contact or support inquiries.
3. Destinations and service providers
Backup operations may transmit data to the destinations configured by an authorized administrator. The application includes backup-target management and a Hostinger integration flow. Which other systems receive data depends on the deployment and the destinations selected for a particular operation.
Access to information should be limited to authorized people and systems that need it for the stated operational purpose. Depending on the deployment, information may also be handled by the infrastructure, email-delivery, or storage services selected to operate the application. Those services may have their own privacy terms and safeguards.
The public pages reference external resources for typography and styling, including Google Fonts and the Tailwind CSS CDN on the home page. A visitor's browser may request these resources directly from their providers, which can involve connection details such as IP address, browser information, and request metadata. Review the current provider terms and any disclosure or consent obligations that apply to your deployment.
4. Retention
Information should be retained only as long as needed for the relevant operational, security, support, and legal purposes. Retention for backup archives, run history, application records, logs, and contact messages varies by deployment and applicable agreement; one fixed period does not apply to every data category.
5. Security
The application provides account access controls and its database-profile interface states that stored database passwords are encrypted. The security of a deployment also depends on configuration, credentials, host and storage security, access management, key handling, updates, and operating procedures. No website can guarantee that a system or transmission is risk-free.
Use appropriately restricted accounts, protect backup-encryption passwords, and test recovery procedures. Do not include secrets in contact requests.
6. Your choices and requests
Access to account and operational records is managed through the applicable application permissions. For questions about personal information or a request relating to it, use the General Contact form. The response and any applicable rights depend on the circumstances and laws that apply to the relevant operator and user.
7. Changes to this policy
This policy may be updated when the website, application, or applicable information practices change. Review this page periodically for the current published wording.
8. Contact
Use the General Contact form for privacy questions. Do not include sensitive account credentials in your request.