Your information should be treated with care.

Who operates Lift With Meaning

Lift With Meaning is a project operated by Manuel Gezalyan. References to “I,” “me,” and “Lift With Meaning” on this page refer to Manuel Gezalyan as the person responsible for this project and its handling of information.

What you may choose to share

When you ask to receive a result-specific First LIFT guide by email, you provide your preferred name and email address. The website also receives the one result category needed to choose the correct guide—Meaning, Awareness, Practice, Recovery, or Transfer. The guide request is transactional and does not enroll you in marketing.

Joining the general Lift With Meaning email list is a separate, optional choice. That general marketing signup uses your first name and email address, not your scorecard result category. The new generic signup is not connected yet. Kit may continue to hold records for people who previously joined the Lift With Meaning email list, including legacy signup-source or form information from which a result category may be inferred, along with marketing-email delivery or engagement information created under Kit’s settings. Those legacy records are not used for the current result-guide delivery path. If you reply to an email, you may also share whatever you choose to include in that message.

The public scorecard runs in your browser. Its individual answers and score calculations are not submitted, and you do not need an account to take it. This is separate from the private Member House experience described next.

If you apply to the Lift With Meaning community, you provide your name, preferred name, email address, country and time zone, optional referral source, age confirmation, required agreements, and answers about purpose, contribution, faith-shaped participation, accountability, disagreement, confidentiality, boundaries, immediate danger, autonomy, and leaving. The application specifically asks you not to submit diagnoses, treatment history, medical records, medication information, trauma details, or additional clinical or medical details.

An active member may give you a private application link containing a random code after the “#” in the address. That fragment is read in your browser, removed from the address bar, and submitted only if you choose to submit the application. Lift With Meaning does not use the member-share feature to record a link opening, page view, or click, and it does not place a referral cookie or use local browser storage to follow you. The code is stored temporarily with the application. Only if your verified application is later approved while the sharing member remains active does the service create a lasting record that one member shared the application with the newly approved member. The code is erased from the application after approval or decline; while review remains open, it follows the application’s retention rules. The record is kept out of admission review and cannot change the review standard or decision. The sharing member receives no applicant identity, answers, status, decision, activation information, or count through member-facing features. An authorized owner may see the minimal attribution after approval while carrying out separate administrative duties, including when that owner was the sharing member.

Application answers and private reviewer notes are not placed in the member directory. If you are approved, activate a member account, and complete a profile, Lift With Meaning stores the display name, bio, purpose, and contribution statement you provide, along with your Lifter identity, any Beacon recognition, and any separate Committed Path paid-access label and Founding Five number. It may also store reading-list entries—title, author, reading status, and visibility choice—and supported-organization entries—name, support reason, optional website, and visibility choice.

Your profile starts undiscoverable. If you expressly turn on “Discoverable profile,” your display name, bio, purpose, contribution statement, Lifter identity, any Beacon recognition, and—while active—your Committed Path and Founding Five labels and founding number may be shown to every active approved member who has accepted the current Community Guidelines. Those same role labels may also appear to members already connected with you. A separate choice controls whether your profile photograph appears there. Reading and supported-organization entries appear only when you separately mark those entries “Approved members.” The directory does not expose your email address, authentication identifier, scorecards, missions, check-ins, Side Quests, journals, XP, milestones, orientation answers, Beacon evidence, review status, or review notes, and it is not published on the open web. These visibility choices apply to the whole eligible active-approved-member audience; the service does not provide a list of who viewed a profile or item. Turning a choice off stops future directory display but cannot recall a screenshot, copy, or disclosure someone already made.

The member database stores your directory settings, including whether the profile is discoverable, whether the photograph is visible, a contact preference, and ordinary version and timing information. If you expressly accept the current Community Guidelines, it also stores the accepted version and the server-recorded acceptance time. Acceptance is a separate, unchecked choice and is never inferred from account creation, an application, or acceptance of other terms. Accepting the Guidelines does not make your profile discoverable or consent to show your photograph; those remain separate controls.

Discoverability and photograph visibility start off, and the contact preference starts at “No contact.” If discoverability is off, photograph visibility and contact are also off. Connection requests are available under the other two settings, but direct member messages are available only between two active approved members whose connection was accepted and remains accepted. The recipient may disable new messages, block the sender, or remove the connection at any time. Those choices stop new messages without erasing the prior history. Each participant can read that history only while their own member access remains active and they have accepted the current Community Guidelines, unless it is later deleted through a verified privacy process or must be handled differently by law.

An approved member may optionally add a profile photograph. A clear photograph of the member’s face is strongly encouraged because the intended community should feel human and accountable, but the photograph is not required. Before upload, the browser applies the image’s orientation, center-crops it, and exports a square PNG. The server does not trust that browser step: it accepts only a bounded PNG, validates its structure, fully decodes and re-compresses it, and rebuilds a canonical PNG without ancillary metadata. The resulting file is stored as a private object in the site’s Sites R2 storage, with limited ownership and image metadata in the member database. It has no public bucket or presigned URL. Retrieval requires the branded member origin, a password-authenticated session, active approved membership, directory eligibility, and the member’s separate photograph-visibility choice.

The profile-photo feature does not perform face recognition, create a biometric template, identify a person, or infer health, emotion, personality, or other traits from the image. Replacing a photo switches the member profile to the new private object and ordinarily deletes the superseded object immediately; an unreachable superseded object is also covered by the account-deletion purge. Removing a photo deletes the current private object before clearing its profile reference. A verified account-deletion request removes every object under that member’s private storage prefix before the authentication account and local member records are deleted. A storage failure stops that destructive sequence so it can be retried instead of leaving an active external account after local identity is gone.

If you use connections, Lift With Meaning stores the two members involved, who sent the request, an optional request note of up to 500 characters, whether it is pending, accepted, declined, or canceled, and ordinary version and timing information. The optional note is shown only to the intended approved-member recipient and its sender. If connected members choose to message, Lift With Meaning stores each message’s participants, text, sender, connection, client-request identifier, and timing information. Each participant can read that conversation history only while their own member access remains active and they have accepted the current Community Guidelines, subject to verified deletion and law. These are stored text messages, not end-to-end encrypted communications, and they are not monitored in real time. Do not use a request note or message for emergencies, medical records, passwords, authentication codes, payment-card or financial-account details, or third-party confidential information.

If you block another member, Lift With Meaning stores who you blocked and the information needed to enforce the block. Blocking hides both members from each other in the directory, prevents new requests, and cancels a pending or accepted connection without notifying the blocked person through the feature. If you submit a report, Lift With Meaning stores the reported member, any related connection or message, the category and details you provide, the immutable evidence snapshot created for that report, its review status, and private human-review information. Lift With Meaning does not routinely scan or read member message text. The community-moderation queue exposes only a message a user deliberately reports and that report’s immutable evidence snapshot. Authorized personnel or service providers may otherwise access stored messages only when reasonably necessary to operate, secure, or troubleshoot the service, comply with law, or protect the service or its users. Reports are not automatically shown to the reported person and never automatically warn, restrict, suspend, remove, or otherwise sanction anyone. Lift With Meaning may withhold a reporter’s identity or other report details when disclosure would expose someone’s privacy or safety, subject to applicable law.

When an active member saves a private First LIFT baseline, the member database receives all twenty answers, the five calculated domain scores, total score, lowest-domain result, instrument version, and completion time. When a member starts and works through a seven-day Primary Mission, the database also stores the selected focus domain, mission dates and status, and daily completion status and effort rating. On Day 8, the follow-up stores only the four repeated anchors for that mission’s focus domain and four separate, domain-specific evidence answers. The repeated anchors create the comparable before-and-after focus score; the evidence answers provide context and are not blended into that score. The database also records participation-based XP events and milestones used to show the member’s Beacon Path. These are educational program records and calculations, not medical or psychological diagnoses.

If you complete Mission & Boundaries, Lift With Meaning stores the orientation version, your answers and acknowledgments, and the completion time. If you later ask for review of Carried It Outward, Lifted Another, or final Beacon recognition, the member database stores the three written reflections you submit, the kind and status of the request, version and timing information, the member-visible decision or next steps, and a private administrator evidence note. Submissions specifically ask you to omit another person’s name and identifying details. A human administrator—not a score, payment, referral, credential, popularity measure, or automated model—makes the review decision. The resulting Lifter identity or Beacon recognition may appear where your member role is otherwise visible; the underlying evidence and review record do not.

If an active member uses Side Quests or journals, the member database stores the entries the member chooses to create. A Side Quest includes its title, reason or alignment, Mind/Body/Soul/Integrated domain, status, optional dates, visibility preference, version and timestamps, plus any structured progress, obstacle, lesson, service, or other entries and optional next steps. A journal entry includes its reflection, training, idea, or general type; title; written body; occurred time; visibility preference; version; and timestamps. Side Quests and journals are private by default. Selecting “approved members” only stores a preference for a possible future feature; V1 does not let another member read them.

Side Quests and journals are for private educational reflection and self-documentation. Please do not use them for medical or clinical records, crisis communications, or another person’s confidential information. The platform does not analyze this writing to diagnose a condition, infer a personality or psychological trait, determine risk, or make an admission, ranking, reward, payment, XP, milestone, or Beacon decision.

If an approved applicant accepts a private member invitation, Supabase receives the email address used for the account, a password that Supabase secures and does not disclose to Lift With Meaning, an authentication user identifier, and ordinary account-security information such as sign-in, recovery, device, IP-address, and verification records. Lift With Meaning stores the Supabase user identifier beside the approved local membership record so that a verified identity can be checked against the current membership status. Creating an authentication account does not make application answers public or place them in Supabase.

If you start or manage the Founding Five offer for The Committed Path, Stripe processes the payment method and billing information needed for recurring charges. Lift With Meaning stores or receives your member identifier; Stripe customer, checkout, subscription, price, invoice, and event identifiers; founding number; subscription status; billing-period and cancellation dates; any invoice-issue type and timing, notice and resolution state; and the exact recurring-price disclosure, consent language, policy versions, and acceptance time associated with checkout. Lift With Meaning does not receive or store your complete payment-card number.

If you book a Personal LIFT Session, you may also provide contact information, scheduling details, your time zone, a regular or extended-hours availability request, your scorecard result category, and the situation or question you want to discuss. The service may also create session communications, brief preparation or working notes, your written seven-day plan, a follow-up email or voice note, and any feedback you choose to share. Please do not submit medical records, government identifiers, financial account details, or more sensitive information than the service requires.

Some scorecard, application, mission, check-in, progress, Side Quest, journal, session, or message information may qualify as consumer health data. Those practices, including rights available under Washington and Nevada consumer health data laws, are described in the separate Consumer Health Data Privacy Policy.

Why I use it

I use this information to send the result-specific resource you requested; verify and review community applications against the stated conduct and participation requirements; request clarification; record admission decisions; create a private member-share attribution only after a verified application is approved; create and secure approved member access; document deliberate acceptance of the current Community Guidelines and Mission & Boundaries orientation; provide a member-owned profile, the expressly opt-in approved-member directory, connection requests, stored messages between accepted active connections, blocks, private human review of user-reported messages and immutable report evidence, and community moderation; provide saved scorecard history, Primary Missions, check-ins, progress comparison, Side Quests, journals, XP, milestones, member-requested evidence review, and an audited human Beacon decision; create and administer Committed Path billing, enforce the ten-place founding limit, preserve recurring-payment consent, provide required transactional notices, prevent duplicate or fraudulent checkout, and separate paid access from Lifter identity and Beacon recognition; deliver general writing and updates only to people who separately chose marketing; process Personal LIFT Session payments; evaluate and respond to availability requests; schedule and prepare for requested sessions; provide the service you purchased; respond when you contact me; understand what questions and problems readers care about; and protect or improve the website and its services.

Community applications are reviewed by a human against the stated conduct and participation requirements. I do not use the answers to diagnose applicants, assign personality traits, or target advertising.

A member-share code or attribution is not used to admit, rank, reward, pay, advertise to, or change access for anyone. It does not create XP, change anyone’s Lifter identity, influence a Beacon decision, or create any other advantage for the applicant or the member who shared the link.

Member scores, comparisons, completion percentages, XP, and automatic milestones are calculated from the answers and activity the member submits. They help organize the educational experience; they are not used to diagnose, predict mental health, determine medical risk, set a price, target advertising, or establish a person’s moral worth. The two outward milestones and final Beacon recognition require a separate documented human review. Beacon recognition is not automatically purchased or awarded merely because a number increased.

Message text and reported-message evidence are not used for diagnosis, psychological, personality, or risk scoring, Lifter-identity or Beacon-recognition decisions, marketing, XP, or payment decisions.

The services that help me do this

Lift With Meaning uses service providers to operate the website, application database, transactional email, optional general email list, payments, and scheduling. Resend sends requested result guides, application-verification messages, and required Committed Path billing notices such as confirmation, annual renewal reminders, and payment-attention messages. For a guide request, Resend receives your preferred name, email address, and a first-party guide link from which the result category can be inferred; it does not receive your scorecard answers or scores. For application verification, it receives your preferred name, email address, and a one-time verification link, not your written application answers. For a billing notice, it receives your preferred name, email address, founding number, and relevant renewal or payment-status context, but not your complete payment-card number.

The result-guide delivery path is available only when the site is configured to acknowledge that open and click tracking are disabled for the relevant Resend sending domain. The email contains a non-instrumented Lift With Meaning link, but Resend may still process ordinary message-delivery, security, and provider-log information under its own terms and privacy practices. The email service you use to receive the message may also process or scan the message and its result-revealing guide link under that provider’s own practices.

Kit is reserved for separately chosen, general Lift With Meaning marketing and may continue to hold existing subscriber records, including legacy signup-source or form information from which a previously submitted result category may be inferred and marketing-email delivery or engagement information created under Kit’s settings. The current result-guide delivery path does not send Kit a scorecard result category. Google processes booking information and provides the online meeting. Stripe hosts The Committed Path checkout and billing management and processes subscription payments, taxes when configured, invoices, cancellations, refunds, payment security, and fraud prevention. The website hosting and D1 database infrastructure serves these pages, transmits guide requests, may process the requested guide’s result-revealing URL when a PDF is opened or downloaded, and stores community applications and any temporary member-share code submitted with them; member share codes generated at approval for new members or once at feature launch for existing members, and usable only while the related membership is active; approval-only member-share attributions; local membership and billing status; recurring-consent and founding-place records; billing-event audit data; member profiles and lists; directory settings; connection requests and notes; messages between accepted active connections; blocks; reports and immutable reported-message evidence; moderation metadata; saved scorecards; missions; check-ins; progress calculations; Side Quests and their entries; journals; XP events; milestones; Mission & Boundaries completions; Beacon evidence and decisions; and audited Lifter or Beacon decision records. Private profile-photo files and their limited metadata are stored in Sites R2 object storage. Side Quest, journal, and member-message text is stored in the member database, not the profile-photo object store. Cloudflare Turnstile protects guide requests and community applications from automated abuse by processing browser-environment and interaction signals needed for that security function. Cloudflare states that Turnstile does not access, store, or transmit form entries or other page inputs. Their handling of information is also governed by their own terms and privacy practices.

Supabase provides approved-member identity, password authentication, invitations, account recovery, session management, and related security records. Supabase receives the approved member’s email address, authentication user identifier, secured password credential, and ordinary technical and security information needed to provide those functions. Lift With Meaning does not receive a readable copy of the password. Supabase is not the authority that decides whether someone may enter the member space: the website checks the verified Supabase user identifier against the current Lift With Meaning membership record before granting access. Member profile text, lists, profile-photo bytes or metadata, scorecard answers and scores, missions, check-ins, evidence answers, Side Quests, journal entries, XP, and milestones are not sent to Supabase merely because the member signs in.

Lift With Meaning does not receive or store your complete payment-card number. You can read Resend’s privacy policy, Kit’s privacy policy, Google’s privacy policy, Stripe’s privacy policy, Supabase’s privacy policy, and Cloudflare’s Turnstile privacy explanation.

Technical information and cookies

Like most hosted websites and embedded forms, this site and its service providers may automatically receive technical information such as an IP address, browser or device details, access dates and times, and page or form interactions. They may use cookies or similar technology to operate, secure, and understand their services.

The member-share feature itself is deliberately narrower. Its random code is placed in a URL fragment, which is not sent to the website as part of the ordinary page request. The application page reads and removes the fragment locally, does not record the opening or click, and sends the code to Lift With Meaning only with a submitted application. The feature does not set a referral cookie, use local or session storage for the code, or add it to advertising or analytics.

The member area uses essential, secure, host-only authentication cookies on the member website to keep an approved member signed in and refresh the session. Those cookies are not advertising cookies and are not deliberately shared with the public website or unrelated subdomains. Authenticated pages and responses are not intended to be stored in a shared cache.

Member House V1 limits the directory to signed-in, active approved members who expressly accepted the current Community Guidelines, and returns only profiles whose owners expressly enabled discoverability. Until current-version acceptance is recorded, other-member directory viewing and search, connections, new member messages, block-list viewing, and other-member photograph retrieval remain closed; account settings and the owner export remain available, and block/report safety actions may still be submitted without returning another member’s profile. A future Guidelines version makes an older acceptance noncurrent until the member separately accepts the new version.

Core profile fields, the profile photograph, and each reading or supported-organization item have the separate visibility controls described above. Mutual blocks hide both members and prevent new messages or directory access between the pair. Email addresses and authentication identifiers are never directory fields. Side Quests, journals, scorecards, missions, check-ins, XP, milestones, orientation answers, and Beacon evidence and review records remain owner-only even if a future visibility preference is stored. Member messages have no public URL, are not end-to-end encrypted, are not monitored in real time, and are not routinely scanned or read. The community-moderation queue exposes only user-reported messages and their immutable report snapshots; the limited operational, security, legal, and protective access described above still applies.

“Print or save as PDF” uses the print function in your own browser or device. Lift With Meaning does not create or store a separate PDF on its server through that control. Printing, saving, syncing, sharing, or backing up a copy places it on a device or service you choose, outside Lift With Meaning’s control; you are responsible for protecting that copy.

Lift With Meaning does not retain the preferred name, email address, result category, message, Resend response identifier, or delivery log from a result-guide email request in its own database. To limit automated abuse, the site creates non-reversible rate-limit markers derived from the requesting IP address and email address and stores only the marker, request window, attempt count, and any temporary block time—not the raw IP address or raw email address in that rate-limit record.

Lift With Meaning does not currently run its own targeted-advertising tracker or sell browsing information. Your browser settings and privacy controls may affect technologies used by the service providers.

Security and incident response

I limit administrative access to people who need it for the purposes described, use encrypted connections for transmission, separate member authentication from membership authorization, and require verified identity before destructive privacy requests are completed. No website or provider can promise absolute security. If I learn of unauthorized access, acquisition, or disclosure, I will investigate and provide notices to affected people, regulators, or others when applicable law requires it.

What I do not do

I do not sell or rent your name, email address, replies, or other personal information. I do not want more information than I need to serve you responsibly.

Your choices

Requesting a guide, submitting a community application, starting or managing The Committed Path, or booking a session does not automatically enroll you in marketing emails. Transactional messages about your requested guide, application, membership confirmation or reminder, payment problem, cancellation, purchase, appointment, plan, and follow-up are separate from optional email-list communications.

You can unsubscribe at any time by using the link at the bottom of any Lift With Meaning marketing email. A signed-in active member can change or withdraw directory discoverability, photograph visibility, reading-item and supported-organization visibility, and contact preference. A message recipient can disable new messages, remove the connection, or block the sender. Those choices stop new messages but do not erase the prior history. Each participant can read that history only while their own member access remains active and they have accepted the current Community Guidelines, subject to verified deletion and law. A member can also cancel or decline a connection, unblock another member, and submit a good-faith report. Turning visibility off stops future display through the directory but cannot recall information another approved member already saw or copied.

A signed-in active member can use “Download my data” to download an authenticated JSON snapshot of the Member House records tied to that account. Export version 6 includes member identity and Beacon-recognition metadata; the member’s own share link and the time its code was created; profile and list records; directory settings and any Community Guidelines acceptance version and time; every connection involving that member, including retained request notes and status history; messages the requesting member sent or received; blocks that member created; reports that member submitted; reported-message evidence only for reports that requesting member submitted; saved assessments; missions and check-ins; Side Quests and their structured entries; journals; XP events; milestones; Mission & Boundaries answers and completion; the member’s submitted Beacon evidence, review status, and member-visible next steps; the current Committed Path billing summary; and the recurring-consent records returned by the member service. It includes profile-photo metadata but not the private image file itself. To protect applicants, the snapshot never includes who opened or used the member’s link, any applicant’s identity, answers or status, member-share attribution records, or referral counts. To protect other members and review integrity, it never includes reports submitted against the requesting member, reported-message evidence from another person’s report, private moderator data, private administrator Beacon or moderation notes, who blocked the member, full payment-card information, or private Stripe security data. It does not claim to include separate application, booking, complete transaction or invoice, marketing, email-provider, authentication-provider, security, or request-audit records. A verified access request may cover additional records, subject to other people’s privacy and safety rights.

You may also ask what other information is associated with your subscription, application, member account, or booking; request access or a copy not included in the download; request a correction; withdraw a pending application; close a member account; or ask that information be deleted. Those additional access and copy requests—and all correction, withdrawal, account-closure, and deletion requests—still use the verified email process below. Requests remain subject to information that must reasonably be kept for completed transactions, safety incidents, tax, fraud prevention, dispute resolution, or other legal obligations. Closing an authentication account ends access to the private member area but does not silently erase records that must lawfully or reasonably be retained for a separate stated purpose.

How long I keep it

Lift With Meaning does not keep the name, email address, result category, or message from a result-guide request in its own application database. Resend may retain transactional delivery or security records under its own policy. Rate-limit markers for guide requests become eligible for deletion more than seven days after their temporary block has ended and are removed when the current manual retention cleanup is run; there is not yet an automatic deletion schedule.

I delete or de-identify declined or withdrawn application answers within ninety days after the decision, unless a documented safety incident, abuse-prevention need, dispute, or legal obligation reasonably requires limited information to be kept longer. An application left pending without activity will normally be deleted or de-identified within twelve months. If an applicant becomes a member, the application may be retained while the membership remains active and for up to twelve months afterward to administer the relationship and community standards.

A submitted member-share code is held while an application remains open, including during clarification or a capacity waitlist, and is erased from that application after approval or decline. It is also erased if the sharing member’s record is deleted. A member’s own random code is generated when approval creates a new member record, or generated once at feature launch for an existing member record. It becomes usable only while membership is active and remains attached to that member record while it exists; suspension or revocation makes it unusable. Deleting the member record removes its code and clears any still-pending application copies from the active database. An approval-only attribution is linked to the two member records and the approved source application. Deleting either member record or that application removes the attribution from the active database. Provider backups and any limited legal or security retention follow the rules described here and in the Consumer Health Data Privacy Policy.

Supabase authentication records are kept while the member account is active and are deleted from active account records after a verified account-deletion request or completed removal when no legal or security reason requires limited retention. Supabase may retain limited security, abuse-prevention, backup, or provider records according to its own documented obligations and retention practices. The local membership record may retain the minimum status and audit information reasonably needed to enforce a suspension, resolve a dispute, prevent abuse, or document a deletion request.

Member profile text and lists, directory settings, connection records and request notes, member messages, blocks, reports and immutable reported-message evidence, review metadata, a current private profile-photo object and its metadata, saved scorecard answers and results, missions, check-ins, evidence answers, progress calculations, Side Quests and their structured entries, journals, XP events, milestones, orientation completions, Beacon evidence, decisions, and audited Lifter or Beacon decision records are kept while the account is active so the requested features, relationship history, safety controls, and human review can work. Declining, deferring, recognizing, or withdrawing a Beacon request preserves that versioned history rather than rewriting the original evidence. Declining, canceling, or removing a connection changes it to a terminal state but does not delete its participants, request note, messages, status, or timestamps; blocking likewise cancels a pending or accepted connection without erasing that history, and unblocking does not restore it.

Deleting an individual Side Quest, quest entry, or journal entry hard-deletes it from the active member database; deleting a Side Quest also deletes its structured entries. Releasing a Side Quest changes its status and does not delete it. An explicit photo-removal request deletes the current private object before its database reference is cleared. During verified account deletion, every object under the member’s private storage prefix is deleted first, then the Supabase authentication account and local member row and dependent Member House records—including directory settings, connections, member messages, blocks, reports, reported-message evidence, Side Quests, and journals—are deleted from the active database. Report and moderation records are not kept in a separate legal-hold system today. Limited request, security, suspension, abuse-prevention, transaction, or legal records outside those active member tables may be retained when reasonably necessary and allowed by law. Provider backups may persist for the limited period described in the Consumer Health Data Privacy Policy.

Recurring-payment consent evidence is kept for at least three years, or at least one year after the related subscription ends, whichever period is longer. Founding-number history is kept so a claimed number is not sold again. Payment, invoice, refund, cancellation, and transaction records may be retained for up to seven years for tax, accounting, fraud prevention, disputes, and legal obligations. Closing a community account does not require deletion of these minimized retained records, but they are no longer used to authorize member access.

I delete or de-identify intake responses, preparation notes, and session-specific working notes when they are no longer reasonably needed for delivery, follow-up, safety, or a dispute—normally no later than twelve months after the final follow-up unless you request earlier deletion or a legal obligation requires longer retention.

Browser privacy signals

Because Lift With Meaning does not currently run its own targeted-advertising tracker or deliberately permit a third party to collect member or consumer health data over time across unrelated websites for targeted advertising, it does not currently change its own behavior in response to Do Not Track or Global Privacy Control signals. The independent providers named above may respond to those signals under their own policies.

Contact

Email privacy questions or requests to trinity@liftwithmeaning.com. State whether you are asking for access or a copy, correction, withdrawal, account closure, or deletion. I may ask you to reply from the address connected to the record or provide only the additional information reasonably necessary to verify identity. You do not need to create a new account to make a request.

Children’s privacy

This website and email list are intended for a general adult audience and are not directed to children under thirteen. The community application and membership are limited to adults eighteen and older. I do not knowingly collect community applications from minors or personal information from children under thirteen. If I learn that such information was submitted, I will take reasonable steps to delete it.

If this policy changes

I may update this page as the project and the services supporting it evolve. When I do, I will change the date above and make material changes clear.