Privacy Policy
Last updated November 8, 2026
Permit Studio (permits.owliesays.com), run by Owlie Says, helps people research building permits from official government sources. This policy explains what we collect, why, and the choices you have. You can read guides, maps and sources without an account.
What we collect
- Account details. If you sign in with Google, we receive your Google account's stable ID, email address, name and profile picture URL. If you sign up with email, we store your email address, your name and a salted, slow hash of your password. We never see or store your Google password.
- Sign-in sessions. A secure, HTTP-only cookie keeps you signed in for up to 7 days. We store only a hash of the session token.
- What you save. Projects you create, including properties, applications, tasks, deadlines, status observations, inspections, corrections and other permit-lifecycle records.
- Private files. Documents you upload, their versions and checksums, where each version is used, and malware-scan and quarantine records. Rejected files are isolated and are never offered for download.
- Collaboration. Project invitations, roles, correction responses, scoped professional reviews and the consent choices recorded for a project.
- Problem reports. If you use "Report a problem" on a guide, we keep your message and, if you give it, your email address, so a reviewer can fix the guide and reply to you.
- Records of changes. We keep a log of account and project changes (who did what, and when) for security and to keep the research record trustworthy.
- Connected apps. If you connect ChatGPT, Codex or another compatible MCP client, we keep the client name and identifier, the scopes you approved, connection and last-use times, and hashes of short-lived access and refresh tokens. Redacted tool records contain the tool name, outcome and duration, but not the prompt, tool arguments, result, token, email, IP address or user agent.
- Technical data. Like any website, our servers and our network provider receive your IP address and browser details when you visit. We use these to run and protect the site.
- On your device. Your theme and language choices are kept in your browser's local storage and never sent to us.
We do not collect payment details. We do not store owner, applicant or contractor names from public permit data.
Google user data
Google sign-in asks only for the basic scopes openid, email and profile. We use that information only to create your account, sign you in, and show your name and picture in the app. We don't use it for advertising, we don't sell it, and we don't share it with anyone except as described under "Who we share with" below. We don't access your Gmail, Drive, Calendar, contacts or any other Google data.
Permit Studio's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
How we use information
- To sign you in and keep your account secure.
- To save and show your projects.
- To let people you authorize collaborate on a project, exchange project documents and record scoped review opinions.
- To send account emails you ask for, such as email verification and password reset.
- To keep the site running, fix problems and prevent abuse.
We don't sell personal information, show ads, or use your data to train AI models. Processing on servers we operate is local processing. We do not send a project's documents to a third-party AI model unless a project owner or manager has recorded consent; revoking consent stops future external processing.
Who we share with
- Google, when you choose Google sign-in (see Google's Privacy Policy). Account emails are sent through Google's Gmail service.
- Cloudflare, which carries traffic to our site and protects it from attacks. It may collect privacy-focused, cookie-free visit statistics for us.
- People you authorize, when you invite them to a project or give them an organization or project role. Their role controls what they can see and change.
- An external AI provider, only if that project has an effective external-AI consent record and the feature identifies the provider before processing. Permit Studio does not currently use project documents to train a third-party model.
- A connected assistant provider, such as OpenAI, when you deliberately connect Permit Studio and ask that assistant to use an authenticated project tool. The provider receives the bounded project fields returned for that request or the fields needed for a project you explicitly confirm creating. These tools do not return project documents, addresses, permit numbers or client references.
- The law: we disclose information only when required by law or to protect people and the service.
The site and its database run on servers we operate ourselves. We don't use third-party advertising or tracking.
Keeping and deleting your data
We keep your account while it's open. You may delete an eligible project in the service, and you may request account deletion in the service or by emailing [email protected] from the address on your account. Account deletion completes within 30 days. Private document bytes are removed; immutable version and audit records keep only tombstoned, non-personal metadata needed to preserve the integrity of the history. Encrypted backups are retained for no more than 30 days, so deleted content ages out of them within that period. Security records that no longer identify you may be kept longer. You can also remove Permit Studio's access to your Google account at any time in your Google Account settings. You can disconnect ChatGPT, Codex or another connected app from the Connected apps section of your Permit Studio workspace; disconnecting revokes that app's active grant and tokens. Account deletion removes connected-app grants, codes and tokens and removes your identity from retained redacted tool records.
Permit Studio in ChatGPT and Codex
You can add Permit Studio to ChatGPT or Codex. Public place and permit-guide tools do not need an account. Project tools require you to sign in on Permit Studio and approve the displayed scopes. With projects:read, a connected app can list your projects, read one project's bounded summary and check application readiness. Withprojects:write, it can create a project only through a separate exact-details confirmation step. It cannot read another user's projects, download project documents, submit a government application or pay a fee.
For public research, we receive the place, project type and guide answers that the assistant sends. For authenticated tools, we also receive the scoped project request and return only the documented project fields. The assistant's provider handles your conversation and the tool data it receives under its own privacy policy; Permit Studio does not receive your full chat history. You can review and revoke each connection in Connected apps at any time.
Security
All traffic uses HTTPS. Passwords and session tokens are stored only as hashes, and access to the database is limited by role. No system is perfectly secure; if we learn of a breach that affects you, we'll tell you.
Children
Permit Studio is meant for adults planning building projects. It is not directed at children under 13, and we don't knowingly collect their information.
Changes and contact
If we change this policy, we'll update the date above, and for significant changes we'll let account holders know. Questions or requests: [email protected].