Privacy Policy
This policy covers witharosa.ai, the Arosa app at app.witharosa.ai, sign-in at login.witharosa.ai, and the Arosa tools for ChatGPT served from mcp.witharosa.ai (together, "Arosa"). Questions and requests: michael@witharosa.ai.
What we collect
- Account data. Your name, email address, a salted hash of your password (never the password itself), whether your email is verified, and the OAuth connections you approve, such as connecting the Arosa tools inside ChatGPT.
- Tool inputs. The property addresses, borough-block-lot (BBL) identifiers and search queries you submit to the Arosa tools, and the source snapshots the tools retain for your account so a result can be re-opened later.
- Service logs. Request identifiers, a pseudonymous account and workspace identifier, tool names, timing, success or failure and safe error codes. The tool gateway does not write your raw queries or tool payloads into its logs.
- Cookies. Session cookies at login.witharosa.ai that keep you signed in. We do not use advertising or cross-site tracking cookies.
Why we use it
- To create and secure your account, verify your email and complete sign-in and OAuth consent.
- To answer your tool requests: resolving properties in US cities, returning public parcel records where available, and searching and fetching retained source evidence with citations.
- To enforce per-account request limits, prevent abuse, keep the service reliable and debug failures.
- To send account email you asked for, such as verification and password-reset links.
We do not sell personal data, share it for cross-context behavioral advertising, or use your tool inputs to train models.
Who receives it
We use service providers that process data to run Arosa, and public data services that answer property lookups:
- Google Cloud hosts the tool gateway and the private research service.
- Cloudflare hosts sign-in, email delivery and edge routing, and protects the app.
- Vercel hosts this public website.
- New York City public data services (such as NYC Planning GeoSearch and PLUTO open data) receive the address or BBL in a lookup, never your account identity.
- Exa, only when public web search is enabled for a query, receives that search query.
We may disclose data when required by law, or to protect the security of the service and its users.
How long we keep it
- Retained source evidence is kept for 30 days per account, then becomes unavailable and is pruned. Backup copies expire on the backup rotation schedule.
- Account data is kept while your account is active.
- Operational logs are kept only as long as needed for security and reliability, and in the ordinary course no longer than 12 months.
Your controls
- Disconnect anytime. Remove the Arosa connection in ChatGPT to revoke its access, or write to us to revoke an OAuth grant.
- Delete your account. Email michael@witharosa.ai from your account address and we will delete your account and its retained evidence, and confirm within 30 days.
- Access and correct. Email us to request a copy of your account data or a correction.
Security
Data is encrypted in transit. Passwords are stored as salted scrypt hashes. Tool access tokens are short-lived (10 minutes), scoped to read-only Arosa access, and bound to the Arosa tools audience. Each account's retained evidence is isolated from every other account.
Children
Arosa is not directed to children under 13 and they may not create an account. Users aged 13 to 17 may use Arosa only where their guardian's consent is not additionally required by applicable law.
Changes
When this policy changes materially, we will update the effective date above and post the new version here before it takes effect.