Privacy & About

Notice version: 2026-10-23 · LAP Advisor 0.10.99

Who we are

LAP Advisor is a Magna Power Innovations Corporation company, developed by Robert Acuña. LAP Advisor helps buyers organize property evidence, compare scenarios and prepare questions for their lending and real estate teams.

Questions or concerns: lapa-questions@magnapowerinnovations.com.

Our privacy commitment

LAP Advisor does not sell personal data. Private financial profiles are not included in the property information shared through team invitations. We use service providers to operate the application and process requested features, as described below.

Concessions messages and invitation notices

You may explicitly send a reviewed concessions discussion to one accepted buyer-agent invitation for an owned home. The message contains the home address, scenario purchase price, requested seller credit and requested price reduction. It excludes your saved profile, income, debts, credit score, cash balances and loan quote. Previewing alone sends no message. Confirmed sends are encrypted and retained in the existing property-message conversation under its access and removal rules. The signed ten-minute preview is held only in the page, cleared when leaving/hiding it, and never grants access.

The current My Team form also requests an email notice when creating a buyer-agent invitation. The notice goes only to that invitation’s email address, uses a fixed sign-in/acceptance link, and includes no home address, property facts or financial details. Provider acceptance is not proof of inbox delivery; failed or unconfirmed sending is reported separately while the in-app invitation remains available. Co-buyer invitations remain in-app only. Success dialogs display the invited email for confirmation; they do not create a new invitation or send mail by themselves.

Information you enter

Account information supports sign-in and account recovery. Saved homes, property notes and source references are stored for your workspace. Household details, home preferences, geography notes, financial entries and quote drafts can be saved in your encrypted private buying plan after your consent. Unsaved entries may be lost when you leave or reload the page.

Public sources and AI research

Property and lender research uses public sources, alongside information you enter. It is not accurate to describe all app data as publicly sourced. Research requests may send public property references, location, numeric home criteria and product interests to an AI research provider. The lender research flow excludes free-text goals, credit scores, income, balances and credit reports from its AI search request. Retrieved information can be incomplete, outdated or incorrect.

Area weather

When you request area weather, the entered property address is sent to the U.S. Census geocoder and the matched coordinates to the National Weather Service. The lookup does not send your financial profile or private notes. Results remain on the current page; LAP does not save an area-weather history.

Credit reports

The optional credit-report review processes supported files temporarily to extract labeled score fields. This flow does not save the report or send it to an AI provider. Extracted scores remain in the current browser session until cleared or the page is closed or reloaded.

Account support

Explicitly authorized maintenance staff can look up account setup metadata, such as name, email, verification status and password-onboarding completion. Each account lookup records the staff identity, target account reference, support reason, optional ticket reference, time and outcome. Audit records exclude passwords, sign-in tokens, private financial profiles and document contents. Saved-property support requires a separate emailed authorization request. The buyer must explicitly approve while signed in to the receiving account, or read the dedicated six-digit support code back to the requesting manager. Approved support is limited to saved property facts and cannot edit the account, inspect private notes/finances/documents or access team/co-buyer records. Support requests, email acceptance/failure, approvals, views, revocations and completion notifications are recorded in a separate activity ledger. Authorized managers can search their own support history and export diagnostic reconciliation reports containing related actors, times and outcomes; these reports exclude property facts, private notes, financial values and approval secrets. Approval tokens and code verifiers are stored as hashes (the six-digit code uses a keyed verifier); raw codes/tokens are excluded from activity exports. Manager authenticator secrets are encrypted. Buyers can review or revoke support, search their own request history and download redacted activity at /support. Buyer downloads record the buyer identity, request reference, time and outcome in the audit; they exclude property facts, private notes, financial values and approval secrets. The original email contains an approval link and a dedicated support code; keep them private. Audit records are separate from saved buying-plan data; contact us about access and retention questions.

Team sharing

You can invite someone to a property or grant a co-buyer read-only access to your shortlist. The recipient must accept using the invited email account. Private finances, budgets, credit information, notes and loan scenarios are excluded from these shared views. Revoking access cannot recall information someone has already viewed or exported.

Service providers and security

The application uses Cloudflare services for hosting, authentication-related infrastructure, database storage, email delivery and bot checks, with configured AI providers for requested research features. EpochShield receives limited security-event categories and outcomes; its telemetry payload excludes borrower identifiers, documents and raw IP addresses. Monitoring and enforcement are separate capabilities; the portal status describes the connected mode.

We have not verified that every provider processes and stores all information exclusively within the United States. This notice makes no U.S.-only storage promise.

When sign-in rate protection is enabled, LAP derives a daily HMAC network token from the connecting IP. The private EpochShield Worker uses the token for short-lived attempt counters; raw IP addresses are not sent to it. Counters expire after a 60-second window and are removed during subsequent checks or scheduled cleanup, normally within two minutes. Shared networks share the attempt limit. Receiver outages leave existing authentication and bot checks in place but suspend this extra rate limit.

Private agent registration

Existing verified agent accounts can save professional details at Agent registration: legal name, full license and issuing jurisdiction/type, firm, office and mailing addresses, and office/direct telephone numbers. The verified account email is checked for every request. Profile details and the original submission snapshot are encrypted using the authentication secret with a separate agent-profile key context. These details are not publicly listed, shared with buyers, sent to AI providers or exposed through a referral-code lookup. Authorized management reviewers can access the submitted legal name, full license/jurisdiction/type and current firm, with audited access; office/mailing addresses, telephones, email and incomplete drafts are excluded from this review tool.

A separate registry reserves the permanent agent identifier, referral code, registration timestamp and a keyed full-license/jurisdiction digest. Profile edits do not regenerate that identity. Name/license corrections, code collisions and unsupported formats require a future reviewed correction workflow; they do not automatically activate professional verification or payments. Codes contain portions of the submitted first name/license and registration month, so sharing a code reveals those fragments. Referral tracking and rewards are not active.

Deleting the account removes its live encrypted agent profile. The minimal registry remains reserved with its account link removed, preventing reassignment and repeat registration of the same license. Keyed identifiers are pseudonymous, not anonymous. Metadata audit references and existing backups remain subject to retention procedures; a full retention and correction policy remains to be completed. This form does not accept tax identifiers, W-9 documents or bank information.

Manual agent registration reviews

Authorized management accounts with recent sign-in and authenticator verification can record dated checks of submitted name, active license details and firm affiliation. These are manual observations with a source URL, evidence note, outcome, reason, reviewer, profile revision, timestamp, license expiry date and a recheck deadline. LAP does not automatically retrieve or certify the source, prove account-holder identity, or grant a license/payment entitlement. Agents can see the outcome, reason and dates, but not internal evidence notes or reviewer identity. A profile save marks an earlier review out of date; expired or unreadable evidence cannot show a current review.

Review evidence and snapshots of the submitted name/license/firm are encrypted with a separate review key context using the existing authentication secret. Review metadata and audit references remain outside the ciphertext. History is retained as append-only records for ordinary portal operations, including after account deletion; it is not an independent tamper-proof audit archive. Deleted/unverified/non-agent accounts are excluded from current review access. A complete retention, correction, recovery and independent integrity policy remains open. Do not include tax identifiers, bank details, passwords or private buyer information in review notes or source URLs.

Buyer-shared property briefings

Property briefings let a verified-email agent account summarize a buyer’s saved property facts and retained record coverage through an accepted, active agent invitation. Permission is checked against the current account, recipient email, invitation generation and saved-home ownership. Briefings exclude buyer notes, finances, documents, messages, other team responses, free-form research and raw county records. Only bounded property fields, source/capture dates, record coverage/counts, fixed limitations and property questions are included. Regional coverage remains limited to existing connectors.

Previewing and preparing text/print copies are audited with account/invitation references, generation, report digest, time/outcome and export choices. Addresses, source URLs, facts and report text are not copied into audit reasons; no new persistent report table or browser storage is created. Reports run no new research and send no email. Exports omit address, parcel, MLS, location and source URLs unless explicitly included; remaining facts can still identify a property. Listing tracking queries/fragments are removed. Reference portal links do not establish that a source was retrieved.

Agents must confirm transaction use before preparing a copy. Future reads/exports recheck current access and report contents. Once downloaded, printed, copied or shared, a report is outside LAP’s access controls and cannot be recalled by invitation revocation or account deletion. Obtain authorization before distributing or publishing buyer-shared property information. Data displayed in an open browser reflects its last load; refresh to recheck changes.

Private agent follow-ups

Agents can track eight standard property discussion topics inside Property briefings, using an accepted active agent invitation. Progress, structured next step and optional due date are private to that agent account and invitation generation. These values are encrypted using the existing authentication secret with a separate follow-up key context. Topic keys, account/invitation references, generation, property snapshot digest, revisions and creation/update timestamps remain database metadata. There are no free-text notes, document uploads or new buyer-finance fields in this checklist.

Other agents, the buyer and management grants do not receive this private progress through the checklist, reports or print copies. A discussion status does not verify property evidence. Changed shared facts require review before progress can be reaffirmed; private buyer notes are excluded from that comparison. Due dates are Pacific calendar dates and create no email, reminder or calendar event.

Invitation renewal starts a separate checklist and prevents portal access to earlier progress, including for the same returning agent. Earlier encrypted rows remain retained until the parent account/invitation is deleted or a defined retention procedure removes them. Clearing an item removes its live encrypted progress; metadata-only audit references and backups remain under existing retention procedures. Audit reasons do not contain progress state, next step, due date, address or property facts. A complete retention/key-recovery policy remains operational work. Future reads/writes recheck account/invitation permission and current revisions; browser display reflects its last load.

Private agent work overview

Agent work overview summarizes an agent’s own private checklist progress across currently accepted agent invitations. It returns shared property addresses, progress counts, next saved due dates and last-save times. Private buyer notes, finances, documents, names/emails and message/response content are excluded; another invited agent’s checklist is not included. Summary values are computed by decrypting the agent’s existing follow-ups for up to twenty properties per page. No additional copy of progress is stored.

Optional address search is submitted in a bounded request body, not an address-bearing page URL, and searches only eligible shared properties. Audit reasons record whether a search was used, page references/count and time/outcome, without the search text, addresses, due dates or progress counts. Page filters operate locally on the loaded page; all counts describe that page. Due dates and changed-fact flags reflect the last load and can overlap. No reminders, emails or calendar events are created.

Opening a property uses an opaque invitation/generation fragment and rechecks current access in Property briefings. A link grants no additional permission and does not accept an invitation or export a report. Private overview results are cleared/reloaded on browser focus; old request responses cannot replace a newer view. The standard print view shows a notice instead of private progress. Screenshots/manual copying remain outside LAP’s access controls.

Appearance preference

Normal or dark mode is saved in this browser to restore your choice across portal pages and tabs. It does not change your account profile or share financial information. If browser storage is unavailable, the selection applies only to the current page.

App ratings and private feedback

Verified buyers and agents can optionally save one current 1–5-star rating, a category and a comment, linked to their account. Authorized maintenance staff can review this private feedback. Comments are encrypted in the feedback database using the application authentication secret with a separate feedback key context. The current service version and submission/review times are recorded. Feedback is not sent to AI research providers or published as a testimonial, and does not grant newsletter or contact permission. Please do not include financial information, passwords, documents or other people’s personal details.

You can edit or withdraw your current feedback at Rate this app. Withdrawal removes the live rating/comment; audit references retain actor/account IDs, feedback/revision references, times and outcomes, without comment text. Backups follow existing retention procedures; no immediate universal backup erasure is promised. An optional home-save prompt stores only an account-scoped opaque identifier and last-shown timestamp in this browser for a thirty-day cooldown. It stores no rating or comment in browser storage. Other browsers have separate prompt preferences; when storage is unavailable, repeat prompts are limited within the current page session.

Private buying calendar

At My calendar, verified accounts can enter private milestones or appointments for a buying plan or owned saved home. Event details are encrypted using the existing application authentication secret with a separate calendar key context. Ownership, event identifiers, revisions and creation/update times remain database metadata. Calendar entries are not shared through team invitations or support mirroring and are not sent to AI providers. Avoid sensitive details in event titles.

Explicit calendar-file downloads exclude titles by default; you can choose to include a title. Files contain event dates/times, state, an event identifier and any selected reminder, without home addresses, account details or attendees. Importing or sharing a file moves that information outside LAP and into the receiving calendar’s storage and visibility rules. LAP does not send reminders or invitations; reminders depend on importing into a compatible calendar. Edits/cancellations in LAP do not automatically update external copies. Deleting an entry removes its live encrypted payload; metadata-only audit references and existing backups remain subject to retention procedures. Save, delete and download audits retain account/event/revision references, times/outcomes and the download title-inclusion choice, without event titles, dates or home addresses.

Property messages

Property messages lets a buyer and one accepted property-team member exchange private text. Other invitations, co-buyer shortlist access and maintenance/support permissions do not grant access. Both participants and the recipient are shown before sending. No financial/profile/document/calendar data is automatically attached; do not type sensitive account or financial details into messages. Messages are not sent to AI research providers. No newsletter or testimonial permission is implied. Messages update on open/refresh; no email/push notification or read receipt is sent.

Text is encrypted in the app database using the existing authentication secret with a separate messages key context, bound to the message, author and invitation generation. This is server-side encryption, not end-to-end encryption. Participant/invitation/message IDs, revisions and creation/removal metadata remain stored. Reads/sends/removals record metadata-only audits without text or property addresses. Authors can remove live text while keeping an author/time marker; copies already viewed or saved cannot be recalled. Revocation blocks further access; renewing an invitation starts a new conversation and does not reveal earlier messages. Earlier text, markers, audit references and backups remain subject to retention procedures; contact LAP about deletion requests, especially for conversations no longer accessible through the portal. No universal retention deadline is promised.

Newsletter and marketing preferences

Newsletter preferences are optional. Signup interest remains pending until you explicitly confirm after email verification/sign-in. Existing accounts are not automatically enrolled, and declining does not affect app access. We record the account/email snapshot, keyed email reference, choice, exact wording/version, source and time. The email snapshot is stored alongside the existing account email; it is not encrypted. Newsletter delivery is not active in this release. Required account/security and requested support emails are separate.

A private email-specific unsubscribe link works without sign-in and suppresses all newsletter/marketing for that address. Links reveal no address but should be kept private: anyone holding one can opt out, never opt in or access an account. Suppression retains a keyed email reference, reason and time independently of account deletion. These identifiers are pseudonymous, not anonymous. Re-subscribing requires a fresh explicit preference save; changing email requires new consent for the new address. Audit records include account/key references, choices, wording/version, source, times and outcomes without raw email or unsubscribe tokens. Authorized managers can see counts only, not recipient lists or grant consent. No private app messages, finances, documents or support records are included. Retention, backup and key procedures apply; no universal retention deadline is promised.

Newsletter editorial drafts

Authorized managers can prepare their own monthly newsletter issues, record content-review attestations and download review copies. Article text, optional quotes/attribution and internal permission references are encrypted with a separate context under the existing application secret. Owner/month/state/revision/time/content hashes and approval attestations remain database metadata. Encrypted historical revisions and audit references are retained; archiving is not deletion. No universal retention deadline is promised.

Private ratings, app messages, support and financial/property data are not automatically copied into drafts. Quotes require separate publication permission; the editor records a reference/attestation rather than the app independently verifying that permission. Unconfirmed quote text/attribution is withheld from previews and review-copy exports. Copies exclude recipient lists and internal permission references. Managers may export a current eligible-audience count, not identities. Content approval and planning dates do not send or schedule emails. Contact LAP about draft/quote retention or deletion requests.

Your controls

Use Delete saved plan in My buying plan to remove that saved profile and its package drafts. Property evidence and account records are separate. You can remove homes from your shortlist and revoke team access through the workspace. For account-data questions or deletion requests beyond these controls, contact the email above. No universal deletion or backup-retention deadline is promised here.

Private seller home details

Optional room, appliance, utility, repair, builder and grounds statements are stored as an encrypted private ledger with version history and the property address recorded for each snapshot. Supplied record references remain seller claims, not independently reviewed evidence. Entries may optionally refer to an owned uploaded record from the same dossier revision. The ledger displays only currently readable private metadata and availability; it does not retrieve file contents or invoke scanning. Removed/unreadable records show an unavailable link; earlier seller statements and their textual references remain in encrypted history until account deletion. Current-entry removal or starting fresh retains earlier encrypted versions for reconciliation. Account deletion removes the current ledger and its encrypted history; opaque audit references remain. Withdrawing or editing a seller dossier does not erase the ledger. The ledger itself is private. Optional room/asset labels and their snapshot date can be included only through the separately approved excerpt-sharing workflow below; other entries and fields are excluded.

Private seller-document quarantine

When separately activated, verified sellers can consent to store PDF, PNG or JPEG property records encrypted in a dedicated Cloudflare R2 bucket. Descriptive labels and file metadata are encrypted in the database; original filenames are not retained. A separately activated private scanner may process file contents only after the owner explicitly requests it. An owner download additionally requires separate activation, fresh matching scan proof and explicit confirmation. Inline original-file previews, original-file sharing with buyers/managers, public scanning services and AI processing remain disabled. Separately activated PDF text review can provide an owner-only temporary text preview for explicit excerpt approval. Encrypted scan proofs and opaque audit references are retained; a scanner result does not establish document accuracy or guarantee safety. File signatures are checked, which does not establish that a file is safe.

Files remain in quarantine until removed; removal and cleanup retain opaque audit references. Withdrawing a dossier does not delete its files. Account deletion removes access but can leave encrypted objects and cleanup tombstones requiring operator reconciliation. Interrupted uploads and storage failures may also need operator cleanup. There is no scheduled automatic retention/deletion service in this stage. Keep original records and contact LAP about retention or cleanup requests.

Private buyer My Drive

After separate operator setup, verified buyers may consent to upload DOCX, DOC, XLS, XLSX, PDF, TXT, HTML or MD files into a private R2 bucket. Bytes and descriptive labels are encrypted using a separate drive key and owner/file contexts; original filenames are discarded. Format/header checks are limited. Uploading does not scan for malware, remove ActiveX, render, download, share or send file content to AI. After separate operator activation, an owner may explicitly send a current quarantined PDF to the private LAP malware scanner. The bytes, fresh challenge and checksum are sent without account identity, label or original filename. Encrypted dated observations remain attached to the owned file; a new attempt supersedes older results. No-threats-detected does not guarantee safety or remove active content. Scan proofs are deleted when their file is explicitly removed; opaque audit references remain. Other file types are not inspected in this stage. Files remain unreleased in quarantine. The Free pilot permits 80 MB of raw files, up to 100 records and 5 MiB per file; incomplete and archived uploads count toward the allowance. Thirty-day archiving is a logical inventory state, without automatic deletion or cold-storage migration. Owners can explicitly remove files. Failed uploads/removals may require retry or reconciliation. Account deletion removes owner access but retains opaque encrypted-object cleanup records; an operator must reconcile old orphans. Backups and operational retention remain separate responsibilities.

Approved excerpts and private concerns

An owner may explicitly save a reviewed, encrypted excerpt and invite an exact buyer email separately. Approved title, excerpt, page/dates, account display name and any explicitly selected room/asset labels become readable under the invitation and current-source checks; excerpt text and room/asset associations require buyer acceptance. Original files and the private ledger are excluded. Owners may compare two current approved excerpts and record a private possible-conflict note of up to 600 characters. Saving the note withdraws both excerpts in one audited transaction. Notes are encrypted with a separate per-owner/record context and are not shared with buyers, professionals or AI. Excerpts, invitation history and concern notes remain until their owning dossier/account is deleted; withdrawing blocks access without erasing history. Opaque audit references remain. Previously viewed or external copies cannot be recalled. Provider backups and operational cleanup remain separate responsibilities.

Retained lender research

The mortgage company library retains public product excerpts and service tags for reuse. It does not store buyer scenarios, credit scores or private financial screening. Source checks retain dated excerpt-presence and service-topic observations, up to ten checks per source. Mentions can include navigation or qualified wording; they do not establish eligibility or current product availability.

The Nerdy Stuff · Start-up