Privacy
Version 2 / 1 October 2026 UTC. Provider configuration below is evaluated for this deployment.
Asked & Found is the service brand in Charlotte, NC. Contact support@askedandfound.com for access, correction or deletion requests. The operator's legal name and business address still require confirmation. The receiving inbox and its delivery path have not been verified; do not send sensitive information until those details are available.
What each service receives
| Purpose / provider | Data and retention |
|---|---|
| Hosting and operational logsVercel | Requested paths, timestamps, response status, network/browser information and application error logs. Team plan and absence of log drains inspected 1 October 2026 UTC: Pro, no configured drains. Vercel documents one day of runtime-log history on Pro. This does not establish deletion of all hosting/security records. |
| Account storageTurso (libSQL database) | Name, email, password hash, sessions, verification records; sessions may include IP address and user agent. Better Auth and Prisma run in our app; they are not separate remote recipients. Account records have no scheduled deletion in the application. Session expiry is not deletion of the account. Database and backup retention must be confirmed for the selected storage. |
| Account emailsResend configured for account verification and password resets; delivery not independently verified | Recipient email, transactional message and verification/reset link when delivery is configured. Resend publishes 30-day email/log retention for Free, Pro and Scale. The applicable account plan and any custom arrangement remain unverified; this is a vendor policy, not a verified account-specific deletion promise. |
| Ordering and paymentsEmail ordering; no online checkout configured | Order email contains the details you choose to send. Online card details are entered with the linked provider, not in this app. The support inbox provider, invoice provider and their retention/deletion settings are not yet verified. Payment records are subject to the provider's records policy and any required transaction retention. |
| Usage analyticsVercel Web Analytics page views | Page views and browser/device/referrer information handled by Vercel. This app defines no custom analytics events. Vercel describes aggregated, non-identifying analytics. Account-specific history and underlying processing retention have not been independently confirmed. See the provider privacy documentation. |
Vercel runtime-log policy / Vercel Analytics privacy / Resend retention policy
Guest requests and website checks
The order form prepares a draft in your browser. It does not send that draft to an order database. You decide whether to send it using your email provider. A copied draft or opened email app is not receipt confirmation. Sent emails and delivered reports can remain in the operator's inbox and working files; their retention period has not been confirmed.
The checker sends HTTP requests from our server to your submitted public URL, related files and sometimes a contact page. Those sites receive the request URL and our server connection information. Fetched content is processed to display the result; the checker has no saved-report database or mailing-list signup.
The in-memory limiter holds IP-derived visitor keys and request timestamps. Its ten-minute allowance is a rate-limit window, not a guaranteed deletion deadline: old timestamps are dropped when that visitor is checked again; entries can otherwise remain until eviction from the 5,000-key map or server restart. Active-request keys are released when a check finishes. Hosting logs are separate.
Browser storage and human report work
Account cookies support sign-in; you can clear them in your browser or sign out. The display edition uses the af-theme local-storage key and remains until cleared or replaced. No advertising cookie code or marketing sequence is implemented by this app; that does not describe cookies on linked checkout or vendor websites.
The operator's probe code supports Anthropic, OpenAI and Perplexity APIs when credentials are supplied. This site's HTTP demonstration uses none of those APIs. A real assistant report must identify the providers, interfaces and public business facts actually sent; confidential customer records should not be supplied for probing. Consumer interfaces and their retention are separate from API policies.
Access, correction and deletion
Contact support with the account or order concerned and the records you want changed or removed. We must verify authority, identify copies in the account store, inbox, report files and relevant providers, and confirm any records that must be retained for transactions or disputes. There is no verified automatic deletion workflow or universal deadline across these systems yet; we will not claim that a request has completed without checking them.
See the service terms and the dated HTTP demonstration. The provider identity, inbox and account-specific retention gaps above remain open.