Privacy

Effective date for the current TEST-service privacy notice: September 26, 2026, when the owner adopted it as the working TEST-mode draft. The owner has approved this TEST-service notice. Commercial launch remains separately gated. TEST mode can still involve real account, waitlist and support information.

Public permit information

PermitBriefly uses public building-permit records to provide property addresses, permit numbers, descriptions, issue dates, city/source information, valuations, and contractor business information when available. Status and final dates are included when available. Subscribers receive records for their authorized trade and territory through the dashboard and exports. Contractor grouping is restricted to the authenticated owner.

Private homeowner phone numbers and email addresses are prohibited in our permit dataset and subscriber outputs. We do not append homeowner contact lists. Collection selects permitted fields and applies contact-pattern filtering before normalized records are written. Additional filtering protects snapshots, dashboard responses, CSVs and brief content. Automated filtering is not a guarantee that every unusual or disguised contact format can be recognized. Please report an unexpected contact detail to support so we can investigate and remove it from the copies we control. Email addresses voluntarily provided for subscriber accounts, waitlists or support are separate from prohibited permit contact details.

Mail-merge exports use ‘Current Resident’ and the property address. PermitBriefly does not send letters or contact homeowners on your behalf.

Account, waitlist and support information

For subscriptions, we store an account identifier, email address received from Stripe, plan/tier, trade selections, territory/group and city selections, subscription and payment status, TEST status, creation/update times, Stripe customer and subscription identifiers, and access/seat or conflict status. We also store email opt-out settings and tokens, delivery/export attempt identifiers and outcomes, and processed billing-event identifiers and timestamps. These records support sign-in, access control, billing reconciliation, exclusivity and duplicate-delivery prevention. Refund requests record the account, email, plan, seat, first-charge date, request date and processing status. Card details are entered on Stripe’s hosted pages; our application does not store full card numbers.

The waitlist collects an email address and records the gutter trade, seven-city territory/cities and enrollment time. The owner uses it to review interest and availability. The current application has no automated availability-notification sender. Joining does not authorize unrelated marketing; any future availability-notification process must be disclosed before activation.

Support correspondence includes the sender address, message headers, subject, message text and any attachments you choose to send. It is used to answer support, billing and privacy requests. Please do not send card numbers, passwords or unnecessary sensitive information.

Account and waitlist records are held in the backend database. They are not exposed through a public customer directory. Owner views require a server-validated owner session; public and ordinary authenticated database roles have no access to the application’s private schema or tables. Subscriber access is checked against the signed-in subscription and current entitlement. The owner and authorized service-provider systems can process information needed to operate the service.

Saved permits, cookies and tracking

Saved permits are bookmarks containing city and permit-number identifiers in this browser’s local storage, not a browser-only copy of our permit database. Click a selected star to remove an individual bookmark, or clear this site’s browser storage to remove all saved selections. They do not sync between devices. Clearing browser storage does not delete server records, provider records or CSV files you previously downloaded. The service worker caches application files, not authenticated permit snapshots; older downloaded copies remain under your control.

Sign-in uses a one-hour session cookie marked HttpOnly and SameSite=Strict, and Secure on the hosted site. The application uses local storage for bookmarks and browser cache storage for its application files. The reviewed application includes no advertising pixels or analytics client script. Vercel still processes hosting requests and operational logs; browser-local bookmarks do not mean there are no server-side records. Stripe’s hosted billing pages and other provider websites have their own privacy practices.

The application does not change its behavior in response to browser Do Not Track signals. It does not embed third-party cross-site advertising trackers. Global Privacy Control is a separate signal, not the same as Do Not Track. The application has no GPC-specific handler; applicability and any required response remain a pre-launch review item. This notice does not claim legal compliance.

Service providers and recipients

• Vercel hosts the website and backend. It processes requests, network/request metadata, backend request data and operational logs to deliver and secure the service. The deployed application includes the permit snapshot. No external log drain was configured at review.
• Supabase hosts the PostgreSQL database containing subscription, seat, waitlist, refund, billing-event and delivery state, plus stored CSV exports and delivery logs.
• Stripe provides hosted checkout and the Customer Portal and processes billing/contact details entered there. It receives plan/selection metadata from the application and returns payment, customer and subscription identifiers and status. TEST mode uses test transactions.
• Resend processes explicitly approved owner TEST emails, including the recipient, sender, subject, message content and attached permit CSV, and delivery metadata. The current application does not route incoming support mail through Resend. Our verified Free plan has 30-day email/log retention under Resend’s published terms; backups persist for seven days. Its DPA describes remaining customer-data deletion within 90 days after account termination. Earlier removal of an individual message requires a separate request to Resend; termination is not the same operation. See Resend’s retention terms.
• Migadu receives support emails and attachments at support@permitbriefly.com and retains a mailbox copy. It forwards those messages to the owner’s Google/Gmail inbox, where a separate copy is retained. Supabase and Stripe do not receive those support attachments through this forwarding route.

Retention and deletion limits

The comparison state removes historical run entries older than twelve weeks when a city refresh is processed. This is not a twelve-week deletion guarantee for all copies: archived refresh folders, deployment packages, exports and provider copies are separate. The current per-city comparison records retain the latest known permitted fields listed above, including older permits omitted from a rolling source, so they are not incorrectly counted as new. They have no automatic age-based expiry.

Current TEST subscriber accounts, waitlist entries, refund/billing-event records, delivery logs and retained exports have no configured automatic deletion schedule. Migadu and Gmail support-message copies and attachments likewise have no application-managed expiry. They remain until separately reviewed and removed. The retention and disposal schedule has received owner approval. Verification of its implementation remains pending. Approval alone does not establish deletion of existing records, archived copies, exports, logs or provider copies. Cancellation or clearing browser storage does not automatically remove these records.

Provider-managed logs and backups have separate retention and recovery behavior. The current Supabase Free plan does not include project backups; local operational copies and other providers’ retained copies are separate. We have not verified an end-to-end deletion deadline across Vercel, Supabase, Stripe, Resend, Migadu and Google. Removing a database record or one email copy does not delete all provider records, backups, billing records or downloaded files. We do not promise immediate deletion from every backup or provider.

Privacy requests

Email support@permitbriefly.com to request an account correction, waitlist removal, deletion, or investigation of an exposed contact detail. State the request and use the account/waitlist email when possible. The owner reviews requests manually and may ask for proportionate confirmation of account control before changing or disclosing private account data. Do not send a password or full card number. There is no automated deletion button.

The owner reviews the affected application and provider copies separately and explains what was corrected or removed, what could not be removed, and the specific reason for any continued retention, such as an unresolved billing dispute or applicable recordkeeping requirement. A privacy request does not itself cancel a subscription; use Manage billing for cancellation. Provider backups and independently downloaded copies may remain beyond removal from the active application.

Policy changes and TEST MODE

Material policy changes will be identified in a dated notice on this page. The current TEST-notice effective date is separate from commercial-launch approval. A launch date will be recorded only when authorized. No customer policy-notification emails are sent during TEST MODE.

During TEST MODE, refund requests are recorded in the private owner inbox in the application; they do not send an email. Any separately authorized application-generated TEST emails go only to the approved owner email address. Subscribers and waitlist members do not receive test messages. Live purchasing remains disabled.

Account · Home