TheLifeStyleKey Tap. View. Connect.

Legal

Privacy Policy

Version: September 8, 2026.

What we collect

  • Account data: email, password hash, verification state.
  • Registration evidence: internal user row, age-affirmation and acceptance timestamps, and the accepted Terms, Privacy, and Acceptable Use versions. This does not constitute identity or age verification.
  • Key data: content, links, and media you choose to upload.
  • Handshake submissions: the name, chosen contact option, and optional note a visitor provides; the Key owner and authorized co-owners can view the submission and may add a private owner note.
  • Handshake safety and consent data: consent time and version, temporary-share linkage when applicable, and minimized pseudonymous safety identifiers used to rate-limit submissions, investigate abuse, and protect recipients.
  • Private Insights analytics: aggregate Key views, link clicks, QR image loads, time, and limited referrer-domain metadata. A QR image load is a file request, not proof that someone scanned the code. Retained analytics does not contain IP or user-agent hashes, fingerprints, visitor signatures, or viewer identities.
  • Separate safety data: minimized hashed IP/user-agent signals may be used for rate limiting, abuse prevention, reports, moderation, and audit integrity. Safety data is not used for product Insights or marketing.
  • Support requests: what you write, a reply email when you are signed out, your account ID when you are signed in, and minimized technical context such as the page path, application version, browser family, operating-system family, device class, and an error reference when available. We do not intentionally collect full URLs, session data, passwords, authentication codes, recovery codes, or Key sharing links in this context.

Why we process data

We process data to operate the service, facilitate the connection you request and prevent abuse, enforce our content policy, and meet legal obligations.

Sharing

We do not sell personal data. We may disclose limited data to infrastructure, email, security, and future hosted-payment service providers, or to law enforcement or legal counsel when required.

Payments

When paid billing is available after the production-readiness gate passes, Stripe Checkout collects payment details on Stripe systems, not through a card form operated by TheLifeStyleKey. We retain processor identifiers, subscription state, payment outcomes, and minimized webhook evidence, not PAN, CVV, or raw webhook contents.

Member alias relay

If the optional alias relay is later activated, an eligible Skeleton Key or Founders Key member may receive mail sent to an approved @mylskey.com alias at a verified private destination. It is a relay, not a mailbox, inbox, webmail service, or IMAP/POP account. Message content may be held temporarily only for security scanning, delivery, bounded retry, and bounce handling; minimized routing, abuse, suppression, and audit records may remain for their configured periods. Private destination addresses are not intentionally placed in relayed visible headers. This feature is not live until its mail-provider, scanning, DNS, deliverability, and abuse-readiness gates pass.

Key links

Active Key links are shared links, not access-controlled links, and can be forwarded. Visitors can save shared content or take screenshots. Browser tricks cannot prevent that. Replace your main Key link and revoke temporary links when needed.

Retention

Ordinary Handshake submissions are retained for 30 days by default; a Handshake the owner favorites, archives, or annotates with a private owner note may be retained for up to 365 days. Related Handshake notifications are removed when the Handshake is deleted. Aggregate Private Insights event and link-click rows are retained for 90 days by default. Every support-request category is retained for 730 days after actual closure, while separate minimized error-diagnostic records are retained for 90 days after creation. Closing a support request first removes its message, reply address, account link, technical context, and operator note. Account deletion preserves support records under their normal lifecycle while severing the account link, canceling queued replies that can no longer be safely delivered, and erasing encrypted reply content. Ordinary encrypted customer-data backup sets expire no later than 35 days after the corresponding active-data deletion, subject to technical rotation boundaries. We do not claim selective erasure from immutable media. Narrow tax, accounting, fraud, dispute, chargeback, security, legal-hold, regulatory, or legal-claims records may be retained when justified; this does not authorize retaining whole customer backup sets. A durable deletion ledger is reconciled before restored data can return to service. Privacy-rights request audit records are retained for at least 730 days. Security and abuse investigation records are retained for 730 days after actual closure; open investigations do not age out. An authorized legal operator may extend an individual closed record beyond its normal deadline only for safety, a dispute, or a legal obligation, and the later deadline and reason are audited. An unreleased legal hold suspends deletion until an authorized operator formally releases it; its review deadline does not release it.

Your controls

You can take a Key offline, replace its sharing link, revoke temporary links, and request account deletion. See Account Deletion for details.

Contact and requests

Use Contact Support for a privacy-rights request. Formal written notices may be sent to LiveTru Ventures, 2088 W US Highway 64, #2143, Murphy, NC 28906. Use Reporting & Takedown for a specific Key or image, takedown, or urgent safety issue.