Privacy Policy

Last updated: August 1, 2026

Lexi ("Lexi," "we," "us," or "our") provides an authenticated resale workflow through Death Pile, related support tools, and the shared workspace at https://deathpile.app. This Privacy Policy explains how we collect, use, disclose, retain, and delete information when you sign in, upload item photos, generate listing materials, join a shared team workspace, or contact us for support.

This release is an existing-account companion workflow. It does not add a public in-app checkout path, and we use the data we collect to operate the workspace rather than to run a consumer storefront.

1. Information we collect

• Account and identity data: name, email address, profile image, and authentication provider details from Google, Apple, or other supported sign-in methods.
• Workspace content: item photos, notes, measurements, pricing research, AI analysis results, generated drafts, tags, and operational status tied to your account or team.
• Usage and device data: browser or app version, IP address, session metadata, error logs, security events, and support interactions.

2. How we use information

• Authenticate users and keep workspaces synced across devices.
• Upload, store, organize, and retrieve item photos and listing materials.
• Run AI-assisted analysis and drafting steps used to identify items, summarize research, and assemble listing content.
• Support shared team workflows, including visibility into items, drafts, jobs, and related operational history.
• Protect the service, investigate misuse, and respond to support or deletion requests.

3. AI processing and service providers

To operate the Lexi workflow, we use service providers for authentication, infrastructure, storage, email delivery, and AI processing. Depending on the action you take, this can include providers such as Firebase, DigitalOcean Spaces, Resend, Google, Apple, Google Gemini, Anthropic Claude, OpenAI ChatGPT/Codex, Flue AI, Pi AI, AutoGPT, and proprietary models.

We use uploaded item photos and listing inputs to operate the product for you and your team. We may also use workspace content, service activity, and derived information to evaluate, develop, test, and improve Lexi features, listing quality, workflow automation, internal models, and related datasets and quality signals.

Individual account deletion does not delete or anonymize Team Data. Those business records remain under the Team Owner's control, and we use them under the Team Owner's service license while the Team exists. If the Team Owner completes permanent Team deletion, we remove the managed Team Data from the active service and improvement source systems, subject only to the limited receipt, backup, security, and legal retention described below.

Global product or source-quality facts can remain after Team deletion only when Team identifiers, Item identifiers, and Team content have been removed. These global facts are not a copy of the deleted Team workspace.

We do not sell your personal data, and we do not use your uploaded listing photos to train public AI models for the benefit of other customers or the general public.

Death Pile is for item photos and listing details only. Do not upload faces, IDs, addresses, receipts, payment cards, or other personally identifiable information in item photos, notes, measurements, or voice input.

4. Team and shared-workspace visibility

Lexi is a B2B, team-based resale workflow. The Team Owner is the customer that controls the business workspace. Authorized Team Members work in that workspace on the Team Owner's behalf. Items, item photos, notes, measurements, Research, listing drafts, Jobs, and related operational history stored in the Team are Team-owned business records ("Team Data").

Uploading or editing Team Data as an Authorized Team Member does not make the business record part of that member's personal account. If the member leaves or deletes their individual account, we remove their access, memberships, and personal attribution. The Team Data remains available to the Team Owner and other Authorized Team Members.

If you own a Team, you must transfer ownership or use the separate permanent Team-deletion flow before deleting your individual account. A multi-member Team requires transfer to another member. A solo Team requires explicit Team deletion, or adding a member and transferring ownership. Individual account deletion never deletes or orphans a Team automatically.

Permanent Team deletion is a separate owner-only action. It requires exact Team-name confirmation and deletes the Team's managed Items, photos, notes, drafts, invites, memberships, and workspace operational records. It also removes Team support and decision records and identifiable Team references from internal quality queues. It freezes new Team work, waits for active Listing and Research jobs to finish, and reconciles Team records and storage before completion. It does not automatically delete the Team Owner's individual account. You should upload content only when the Team Owner authorizes you to add it to the workspace.

5. Retention and deletion

We keep account, job, and workspace records for as long as they are needed to operate the service, support your team, meet legal obligations, and protect the platform.

Individual account deletion removes your authentication account, account profile, personal storage, incoming invitations, Team memberships, and personal attribution. It deletes personal-only Items and does not delete Team Data. Team Data remains under the Team Owner's control after an individual member's account is deleted. Personal-attribution cleanup includes structured attribution in retained Items, note revisions, Research and Listing Jobs, decision records, and support projections. A pending Team invitation created by the departing member remains available to its recipient as Team Data, but we remove the departing member's inviter attribution. If the account is linked to Sign in with Apple, we ask the member for a fresh Apple authorization and bind any usable credential to that account before cleanup. After local data and Firebase authentication deletion complete, we try to revoke Apple authorization automatically. If no usable Apple credential is available or automatic revocation fails, deletion still completes and we provide Apple's manual access-removal step.

Uploaded image files are stored in lifecycle-managed object storage. After processing, image files may be moved into managed storage that is configured for automatic cleanup after roughly 90 days. Related Team Data, including metadata, notes, and generated listing content, remains subject to the Team Owner's workspace controls and the Team-deletion flow.

Removing an individual Item from the active workspace is an ordinary Team-record lifecycle action. It may hide or soft-delete the Item while retaining it as Team Data. It is not the same as permanent Team deletion or individual account deletion.

You can request individual account deletion through Settings or, when you do not belong to a Team, from Team Gate. A Team Owner can separately request permanent Team deletion from Team Settings. We retain a minimized deletion receipt for 24 months. An individual receipt contains the account identifier, request type, request and response dates, outcome, and any basis for an incomplete request. We use it only to document and verify deletion compliance. Transient Team, Item, email-domain, and cleanup details are removed when processing reaches a terminal outcome. Completed Team-deletion receipts likewise remove owner, member, Team-name, Item-id, and lease details. They retain salted one-way owner and confirmation proofs only so the original owner can safely retrieve an idempotent result. Routine database expiration can occur shortly after the 24-month boundary. Some backups or security logs may persist when legally required or needed to protect the service. We do not retain deleted Team content merely as a deletion receipt.

6. Your choices and rights

Subject to applicable law, you may request access to your data, ask us to correct inaccurate personal information, request an authorized export of workspace data, or request deletion of your individual account. Team Owners may request deletion of their Team Data through the separate Team-deletion flow. We may ask you to verify your identity and, where relevant, transfer or delete a Team you own before completing individual account deletion.

If we later offer product settings or consent choices related to dataset creation, model improvement, or similar secondary uses, you will be able to review and manage those choices through the applicable product flow or by contacting us.

7. Children's privacy

Lexi is intended for resale operations and is not directed to children under 13. If you believe a child has provided personal information to us, please contact us so we can investigate and remove the data when appropriate.

8. Changes to this policy

We may update this Privacy Policy to reflect product, legal, or operational changes. When we do, we will post the updated policy here and revise the effective date above.

9. Contact

Support: support@deathpile.app

Privacy: privacy@deathpile.app

Website: https://deathpile.app