01 / Scope
What this policy covers
This policy applies to RivetSift’s public website, founding signup flow, paid Austin weekly lead service, and the emails sent through those services. It does not describe the privacy practices of a third-party website linked from an Austin permit record or payment checkout.
Effective date: September 13, 2026.
02 / Information
What we collect
Signup information
When you request founding access, we collect the name, company, work email, selected market, selected plan, and list status you provide. We also keep the signup and weekly-list timestamps needed to operate the service.
Paid-recipient information
If you choose a paid plan, we use payment status, activation timing, the signup email, and checkout or payment reference data to match a successful payment to the right Austin recipient and maintain delivery access. The hosted payment process handles payment details; RivetSift does not claim to store full card numbers.
Delivery and preference data
We keep delivery status, message identifiers or delivery errors where available, and whether you have unsubscribed from future Austin issues. An opaque unsubscribe token is stored as a protected hash so the link can work without putting your email address in the URL.
03 / Use
Why we use it
- To confirm signups, maintain the requested weekly list, and provide access to Austin issues.
- To reconcile paid access and payment status with the selected plan.
- To send the weekly issue and related confirmation or operational notifications.
- To prevent duplicate, stale, or unsubscribed recipients from receiving future issues.
- To investigate delivery problems, respond to requests, and keep the service working.
04 / Delivery
Weekly issues and email notifications
RivetSift’s weekly issue is intended to give commercial cleaning teams a source-audited Austin construction shortlist. It may include a signup or payment confirmation, the issue itself, delivery-related updates, and other operational messages needed to provide the service. The issue is not a promise that a project needs cleaning work or that a listed contact will respond.
We send these messages to the work email associated with your signup. You can stop future Austin issue emails through the unsubscribe link in an issue; other messages may be sent only when needed to confirm or operate an account or payment request.
05 / Choice
Unsubscribe handling
An unsubscribe link contains an opaque, tokenized value tied to the recipient record. Using it marks that recipient as inactive for future Austin issue delivery. RivetSift then excludes that recipient from later Austin issues; the unsubscribe action itself does not claim to change a payment record or card details.
06 / Source data
Austin permit-source data
RivetSift starts with the City of Austin Open Data permits feed and links back to the public permit source. We may store the permit or project identifiers, permit and project names, project address and details, status and activity dates, work class and valuation, certificate-of-occupancy information, contractor name and published phone number when available, source URL, and the review notes needed to show what was checked.
This information comes from public sources and may be incomplete, delayed, changed by the source, or unrelated to a future cleaning opportunity. RivetSift does not represent a permit as a confirmed project award, buying signal, or endorsement of a contractor. Source links and issue notes are included so a recipient can review the underlying public record.
07 / Stewardship
Sharing, security, and retention
RivetSift shares the information needed to run the service with the providers that support email delivery and hosted payment or checkout infrastructure. We do not sell signup information. We do not add unrelated advertising or data-broker sharing to this service.
We use access controls, protected tokens, and the service’s normal operational safeguards for stored records and delivery links. No online system can promise absolute security. We retain signup, delivery, payment-status, and source data for as long as it is reasonably needed to provide the service, reconcile access, handle unsubscribe requests, resolve disputes, or maintain accurate issue history, then remove or de-identify it when it is no longer needed for those purposes.
08 / Contact
Questions about your information?
Email the RivetSift team at rivetsift-3@polsia.app. Include enough context for us to identify your signup, but do not send payment card numbers or other sensitive financial details by email.
Email RivetSift