DraftDraft — pending legal review. This document describes how Lifecycle works today and is not yet final. Questions: legal@lifecycle.lol.
Legal
Data Processing Addendum
A plain-language summary of the terms under which Lifecycle processes personal data in Customer Content on your behalf. A signable version is available on request.
Last updated: September 28, 2026
1. Roles
For Customer Content in a Cloud desk, your organization is the controller and Lifecycle is the processor. For On-prem desks, the data lives on your server and Lifecycle does not process it, except for sign-in, billing, and license heartbeats described in the Privacy Policy. Lifecycle is an independent controller for account, billing, and platform security data.
2. Your instructions
We process Customer Content only to run the desk features your administrators turn on, to secure and support the service, and as required by law. Connecting an integration (for example Microsoft Graph, a shipping carrier, or eBay) is an instruction to send the data that integration needs.
3. Data subjects and categories
- Your employees, contractors, candidates, and managers: names, work email, user principal name, job title, department, office, phone numbers, manager, start and last-day dates, and ticket notes.
- Device records: asset tags, serial numbers, models, assignment history, warranty dates, costs, and retirement photos.
- Shipping recipients: name, shipping address, phone, tracking numbers, and label files.
- Desk staff: sign-in identity, roles, and activity history.
Do not put special-category data (health, biometric, government identifiers) in free-text ticket fields; the service is not designed for it.
4. Security
- TLS for all traffic to lifecycle.lol, including hosted desks at lifecycle.lol/<name>.
- Per-instance data separation: every desk query is scoped to the instance on the request host, and hosted desks require invited membership.
- Role-based access (IT, HR, Finance, IT Admin) and sensitive-ticket restrictions inside a desk.
- Secrets such as directory bind passwords and API keys are never placed in URLs, and diagnostic logs redact passwords and tokens.
- Encryption at rest provided by our database host.
5. Subprocessors
You authorize the subprocessors on our Subprocessors page. We will post changes there before a new subprocessor handles Customer Content. If you object on reasonable data-protection grounds and we cannot address the concern, you may cancel the affected service and export your data.
6. Requests and incidents
Desk administrators can view, correct, export, and delete records themselves. We will help with data-subject requests you cannot handle in the product. We will notify you without undue delay, and within [72 hours], after confirming a personal-data breach affecting your Customer Content.
7. Export, cancellation, and deletion
You can export everything at any time from Settings → Backups. If a payment fails, a trial ends, or you cancel, the desk becomes read-only: you can still sign in, view, and export, but not make changes. Lifecycle never locks you out of your data for billing reasons.
Cloud data is not deleted automatically when a subscription ends. Email privacy@lifecycle.lol from an instance administrator to have it deleted; we delete it from the production database within [30 days] and it ages out of database-provider backups on their schedule.
8. Location and transfers
Cloud Customer Content is hosted in the United States. Where a transfer requires a legal mechanism, we rely on the EU Standard Contractual Clauses or an equivalent recognized mechanism.
9. Signed copy
To sign a DPA with your organization's details, email legal@lifecycle.lol. A signed DPA controls over this summary.