Security & Compliance Statement
This is usually the document that decides whether BackupLens can be deployed. It describes what access we hold, what we can and cannot do with it, and where your data lives.
The single most important fact: BackupLens holds read-only access to your AWS environment. It cannot create, modify or delete a backup, a plan, a vault or a recovery point. That is enforced by the IAM policy you create, not by a promise in our code.
What access BackupLens holds
You create an IAM user in your own AWS account and grant it a read-only policy covering AWS Backup and, optionally, Cost Explorer. We publish the exact list of actions used, and the product includes a permission checker that probes each one and reports which are missing. Nothing is requested that isn't used.
- Describe and list operations against AWS Backup — jobs, plans, vaults, recovery points, protected resources
- Cost Explorer read access, only if you enable cost monitoring
- No write, delete, or modify permissions of any kind
- No access to the contents of your backups — BackupLens reads metadata about jobs, never the data inside them
Credential handling
- AWS access keys are encrypted at rest with AES-256 before being written to the database
- Encryption keys are held in server environment configuration, not in the database or the application repository
- Keys are never returned to the browser, never logged, and never included in reports or alerts
- You can rotate or revoke the IAM user at any time from your own AWS console; BackupLens degrades to "no data" rather than failing unsafely
Where data is stored
| Item | Location |
|---|---|
| Application & database | Oracle Cloud Infrastructure, Frankfurt, Germany (EU) |
| Backup job metadata | PostgreSQL, same region |
| Your backup data itself | Never leaves your AWS account — BackupLens does not copy, move or store it |
| Application pages | Static files served from our web host |
For customers with data-residency requirements, note that all processing occurs within the EU. If your policy requires a specific jurisdiction, contact us before signing.
Authentication & access control
- Two-factor authentication on every account — authenticator app (TOTP) or emailed code, with single-use recovery codes
- Sessions are held in browser session storage and expire; closing all tabs ends the session
- Automatic sign-out after 30 minutes of inactivity, with a warning before it happens
- Role separation between customer users, billing administrators and global administrators
- One AWS account and one email domain per organisation, preventing accidental cross-tenant access
Monitoring & change visibility
Configuration changes — to backup plans, vault policies or AWS credentials — generate an alert and an entry in the audit log. This exists specifically so that a change made outside a change-control window is visible rather than silent.
What we do not claim
We state this plainly rather than let you assume it: BackupLens does not currently hold SOC 2, ISO 27001 or PCI DSS certification. We are a small vendor and we would rather tell you that up front than have it surface during your review. If a certification is a hard requirement for your institution, tell us — we would rather know early than waste your time.
Reporting a vulnerability
Email security@backuplens.com. We will acknowledge within two business days. Please give us reasonable time to remediate before public disclosure.
Privacy Policy
This policy explains what personal data BackupLens collects, why, and what rights you have over it. BackupLens is an operational monitoring tool sold to organisations, so the personal data involved is limited and work-related.
Who we are
BackupLens provides AWS Backup monitoring software. For questions about this policy or about data we hold, contact privacy@backuplens.com.
What we collect
| Category | What it includes | Why |
|---|---|---|
| Account data | Name, work email address, organisation name, hashed password, MFA settings | To create and secure your account |
| Usage data | Sign-in timestamps, pages accessed, last-seen time | Security monitoring and support |
| AWS credentials | Read-only access key and secret, encrypted at rest | To poll AWS Backup on your behalf |
| Backup metadata | Job outcomes, resource names, vault names, plan names, error messages, sizes, timings | The core function of the product |
| Cost data | Spend figures from AWS Cost Explorer, if enabled | Cost monitoring and budget alerts |
| Notification settings | Recipient addresses, Telegram chat identifiers | To deliver the alerts you configure |
What we do not collect: we do not read the contents of your backups. BackupLens sees that a backup of a resource succeeded or failed; it does not see what is inside it. We do not use tracking cookies, we do not run advertising, and we do not sell or share personal data with anyone for marketing.
Legal basis
Where GDPR applies, we process account and usage data on the basis of contract (delivering the service you have subscribed to) and legitimate interest (securing the service and preventing abuse). Backup metadata and AWS credentials are processed on your instruction as a processor — see the Data Processing Agreement below.
How long we keep it
- Backup job records: retained while your subscription is active, so historical and compliance reporting works
- Account data: retained while the account exists
- Server logs: 14 days
- After termination: data is deleted within 30 days of a written deletion request, or 90 days after subscription end if no request is made
Who else is involved
We use a small number of sub-processors. They are listed in the DPA below. We do not add a sub-processor that has access to customer data without notice.
Your rights
Where GDPR or similar law applies, you may request access to, correction of, or deletion of your personal data, request a portable copy, or object to processing. Write to privacy@backuplens.com and we will respond within 30 days. If you are an employee of a customer organisation, we may need to direct your request to that organisation, since they control the account.
Changes
Material changes will be notified by email to account owners at least 30 days before they take effect.
Terms of Service
Please have counsel review this. This is a working draft written to be clear and fair, not a document produced by a law firm. Jurisdiction, governing law and liability caps in particular should be set by your lawyer and ours before signature.
1. The service
BackupLens monitors AWS Backup activity in the AWS account you connect, and provides dashboards, reports, cost analysis and alerts based on what it observes. It is a monitoring and reporting tool.
BackupLens does not perform backups. It does not create, run, modify or restore them, and it is not a substitute for a backup strategy. If your backups are misconfigured, BackupLens can tell you — it cannot fix them, and it cannot recover data that was never backed up.
2. Your account
- You are responsible for the accuracy of the information you provide and for keeping credentials secure
- You are responsible for the IAM user you create and the permissions you grant it
- Accounts are for a single organisation; one AWS account and one email domain per subscription
- You must tell us promptly if you believe an account has been compromised
3. Subscription, trials and payment
- Trials run for the period stated at sign-up, with no payment required and no automatic conversion to a paid plan
- Paid subscriptions are annual and quoted according to the size of the environment monitored
- Fees are payable in advance; invoices are due within the period stated on the invoice
- On expiry the account enters a 30-day grace period during which alerts continue and sign-in is progressively restricted
4. Acceptable use
You agree not to attempt to breach or test the security of the service without written permission, to resell or provide access to third parties without agreement, to connect an AWS account you are not authorised to monitor, or to use the service to breach any law.
5. Availability
We aim for continuous availability but do not offer a contractual uptime guarantee under these standard terms. Monitoring runs on a schedule; interruptions may delay detection of a backup failure. If your institution requires a formal SLA, contact us and we will negotiate one separately.
6. Intellectual property
BackupLens and its software remain our property. Your data — including backup metadata collected on your behalf — remains yours. You may export it at any time.
7. Liability
To the maximum extent permitted by law, neither party is liable for indirect or consequential loss. Our aggregate liability is limited to the fees paid in the twelve months preceding the claim. Nothing limits liability for death, personal injury, or fraud.
Worth stating explicitly: BackupLens reports on backups; it does not guarantee they succeeded, and it cannot be liable for data loss arising from backup failures it did not detect or from a failure to act on an alert it sent.
8. Termination
Either party may terminate at the end of a subscription period on 30 days' written notice. We may suspend an account immediately for non-payment after notice, or for a serious breach of the acceptable-use terms. On termination we will delete your data in accordance with the Privacy Policy.
9. Changes to these terms
We may update these terms. Material changes will be notified at least 30 days in advance, and continued use after that constitutes acceptance.
10. Governing law
To be completed — jurisdiction and governing law to be set by agreement between the parties and confirmed by counsel.
Data Processing Agreement
This DPA applies where BackupLens processes personal data on your behalf and GDPR or equivalent legislation applies. You are the controller; BackupLens is the processor.
Subject matter and duration
BackupLens processes personal data for the purpose of providing AWS Backup monitoring, for the duration of the subscription and any agreed retention period thereafter.
Nature and purpose of processing
Collection, storage, organisation and display of AWS Backup metadata and account information, in order to present dashboards, generate reports, and deliver alerts.
Categories of data subject
- Employees and contractors of the customer who hold BackupLens accounts
- Recipients of alerts nominated by the customer
Categories of personal data
- Name, work email address, organisation
- Authentication data — hashed password, MFA configuration
- Usage data — sign-in times, activity timestamps
- Alert recipient addresses and messaging identifiers
No special-category data under Article 9 is intentionally processed. Resource names in AWS may incidentally contain personal data if the customer has named resources that way; we treat all such metadata as customer data.
Our obligations as processor
- Process personal data only on your documented instructions
- Ensure personnel with access are bound by confidentiality
- Implement appropriate technical and organisational measures, as described in the Security & Compliance statement above
- Assist you in responding to data subject requests
- Notify you without undue delay, and in any case within 72 hours, on becoming aware of a personal data breach
- Delete or return personal data at the end of the engagement, at your choice
- Make available the information needed to demonstrate compliance
Sub-processors
| Sub-processor | Purpose | Location |
|---|---|---|
| Oracle Cloud Infrastructure | Application and database hosting | Frankfurt, Germany (EU) |
| Web hosting provider | Serving static application pages | See current disclosure on request |
| Email delivery | Sending alerts, verification codes and reports | See current disclosure on request |
| Telegram | Alert delivery — only if the customer enables Telegram | Global |
We will give notice before adding or replacing a sub-processor with access to personal data, and you may object on reasonable data-protection grounds.
Note on AWS: your own AWS account is not our sub-processor. We connect to it under credentials you issue, and your relationship with AWS is governed by your own agreement with them.
International transfers
Primary processing takes place in the EU. Where a sub-processor transfers data outside the EEA, transfers rely on Standard Contractual Clauses or an adequacy decision.
Audit
On reasonable written notice, and no more than once per year unless required by a regulator, you may request information necessary to demonstrate compliance with this DPA.
Signature
To execute this DPA as part of your subscription, contact legal@backuplens.com. We will provide a countersigned copy.