How this service handles data.

Service and contact

Service name: Fast Public Record Bot. Operating country: United States. For support or account-data requests, contact personalrecordsai.support@gmail.com. We use your email to confirm registration and help you recover account access.

Service requests

When you request a free review, Supabase stores the package, request reference, status and submission time with your account ID. You can view and export your own request. The project operator can read your saved checklist for the review and update your status. To withdraw or request removal, contact support with your request reference.

Fast Public Record Bot: saved business workspace

The signed-in workspace at /workspace lets you explicitly save one checklist per account. It stores your business name, category, city or service area, business model, owner-or-representative choice, checklist review choices and timestamps in Supabase. These details are sent only when you select Save to my account. Use public business details only. Do not enter street addresses, customer records, verification documents or credentials.

Your account can read, update, download and delete its own saved checklist. Other customer accounts cannot access it through the application. The project operator has administrative access. Saving replaces the previous saved version. Deleting removes the saved checklist from the active application database; it does not erase copies you downloaded or promise deletion from provider logs or backups. No automatic retention period is configured.

This workspace provides a fixed preparation checklist. It does not run an AI model, search public records, connect to your Google account, submit applications or guarantee approval. The legacy dashboard and practice histories below remain fictional test workflows.

Browser-only business checklist

The preparation tool uses a business name, proposed category, city or service area, business model and review answers only in the current browser tab. These entries are not sent to our server, saved to your account, stored in browser storage or passed to Google. Reloading or closing the page clears them. Copying puts the checklist on your clipboard; printing uses your browser and chosen printer or PDF destination. You control those copies. Enter street addresses and verification evidence directly with Google.

The checklist uses fixed guidance, not an AI model. The site host can still process ordinary page requests and service logs; the checklist entries are not included in those requests.

What the account pilot stores

Supabase Auth manages the test account email, password authentication and session records. The app stores a display name, fictional tracked-record titles and statuses, and fixed preparation scenarios with practice-review events, template versions and timestamps. A minimal activity log stores the account and affected-item identifiers, action type, account-or-system attribution and time for profile, record and draft changes. It does not copy profile values, record contents, email addresses, passwords or session tokens. It starts when enabled and does not cover sign-ins or password changes. Authentication passwords and session tokens are not included in account exports.

Where it goes

The pilot can run locally on the project owner’s computer or on the free Render test host, and connects to the existing Supabase development project. Profile and fictional workflow data are stored there under account ownership rules. This pilot does not send a business application to Google, connect a Google account, or call an AI model.

Signed-in customers can read their own records. The project operator has administrative access through the development project. Normal application and provider logs may also contain request and service information.

Browser storage

Authentication uses browser cookies to maintain the session and complete email sign-in flows. Browser-only checklist answers stay in memory. The signed-in workspace sends its business details and review choices to the database only when you select Save to my account. The separate practice workflow saves fixed fictional snapshots. This app has no advertising or analytics integration.

Access and removal

The workspace provides a download of your saved business checklist. When saved workspaces are enabled, Account Settings also includes that checklist in the account export alongside your profile, fictional tracked records, preparation history and activity metadata. Legacy collections are limited to 1,000 entries each and state whether more entries exist. Keep downloaded files private on shared computers.

You can delete your saved business checklist directly from the workspace after confirming the action. For removal of the entire account, email personalrecordsai.support@gmail.com. The operator must verify account ownership before acting. There is no self-service account deletion or automatic retention schedule yet. Activity entries require explicit removal after account deletion. No removal deadline or backup deletion promise is made by this test service.

Support email

Support messages are handled through Gmail and include your email address and the content you choose to send. Share fictional examples only. Do not email passwords, verification codes, reset links, account exports, identity documents or real customer records. A support-response or email-retention schedule has not been established.

Keep private records outside this tool

Do not enter customer records, personal addresses, government identifiers, financial information or identity documents. The public checklist accepts basic business details in your browser only. The signed-in business workspace saves basic business details only when you choose Save. Legacy record tracking and practice histories remain for fictional examples only.