Scope and contact
Cirrovyn LLC operates NoticeFeed. This notice covers information about website visitors, subscribers and teammates, people appearing in county property records, and people contacting us. You do not need an account or subscription to ask about your information.
Email support@noticefeed.com or write to Cirrovyn LLC, 7901 4th St N #33724, St. Petersburg, FL 33702, USA. Please provide only what is needed for your request. Do not send passwords, API keys or full payment-card details. Do not send identity documents unless we arrange a necessary, secure verification step.
Information we use and why
Accounts and billing. We use email addresses, authentication records and sessions to provide account access. We store account membership, plan and subscription status, billing-provider identifiers, saved searches, email preferences, usage counters, invitation records, API credentials and webhook configuration. We retain policy acknowledgement versions and timestamps. We use this information to operate the service, enforce plan permissions, manage billing, prevent unauthorized access and support customers. Supabase Auth handles passwords. Stripe processes payment details; our application stores billing identifiers and status rather than full payment-card numbers. Checkout recovery records retain the selected plan, customer identifier or email, return addresses and the current attempt/session information to avoid duplicate purchases.
County and property records. We obtain code-compliance and parcel information from public county and local-government sources in the locations listed in our coverage section. It can include case numbers, dates, descriptions, status and history; property addresses and identifiers; recorded owner names and mailing addresses; property characteristics; county homestead information; assessed values; and recorded sale dates and amounts. We link records by property identifiers and organize them for search and delivery. We do not collect skip-traced phone numbers or personal email addresses through this pipeline.
Our recency score uses only the county case date. Other labels can compare county mailing and property addresses, show a county homestead flag, group property types or identify foreclosure-related wording in a case description. These transformations are ours, not additional county findings. They do not establish residence, current occupancy, financial hardship, equity or willingness to sell. We retain observation and source-check timestamps to manage updates and identify changes.
Delivery, security and operations. We process message recipients, subjects, contents and delivery status to send account messages and requested record updates. Delivery queues can temporarily contain owner-linked property records. We keep operational outcomes, bounded error details and usage records to maintain reliability, investigate problems and enforce limits. Our hosting and security providers process network and request information. Account request limits use IP addresses; API usage summaries include network identifiers such as autonomous system numbers. We do not add a browser fingerprint or IP address to policy acknowledgement receipts.
Support and postal correspondence. We process contact details, correspondence, attachments and the information needed to handle account, billing and privacy requests. Business mail sent to our mailing address is received, opened and scanned by Northwest Registered Agent, then made available to us in its online account. Support correspondence is handled through our Microsoft 365 mailbox. Please avoid including unnecessary sensitive information.
Who receives information
Subscribers receive the property records available under their plans, which can include recorded owner names and mailing addresses. They may access records through search, email, downloads and authorized API or webhook integrations. Account owners control their invited teammates and configured destinations. These recipients can retain copies. Paid access to owner-linked records may be treated as a sale of personal information under some privacy laws; public-record exclusions differ. We do not make a blanket claim that every record or transformation is exempt.
Cloudflare hosts the application, handles scheduled processing and delivers customer and authentication emails. Supabase supplies database storage and authentication. Stripe processes payments and subscription management. These services receive the information needed for their functions; email delivery includes recipients and message contents. Microsoft 365 handles support email, and Northwest Registered Agent handles postal mail as described above. Google receives browser requests when a page loads Google Fonts. We may also disclose relevant information when legally required or when reasonably necessary to investigate security incidents or protect legal rights.
Deleting information in NoticeFeed cannot recall a file, email or response already received by a customer or an external destination. We explain the actions we can take on a request and any recipient follow-up required by applicable law rather than promising deletion of every copy.
Cookies and browser resources
We use session cookies to sign you in and maintain access, and browser storage for display preferences such as the theme. Blocking session cookies may prevent sign-in. Pages load fonts from Google Fonts, which receives the associated browser requests. Hosting and security systems may process request information independently of these cookies. The application does not currently use advertising cookies or a third-party advertising analytics SDK.
Record updates and withholding
Parcel records are scheduled for refresh every 30 days, subject to bounded processing capacity and successful county access. Records without usable initial parcel data retry more slowly. Updates are not real time; outages and backlogs can delay detection.
When a successful source check detects withheld owner details, removal of previously published mailing details, or loss of a previously usable parcel record, NoticeFeed places a hold on matching records. A missing record can be an availability issue rather than a verified privacy request. Network errors alone do not establish withholding. Holds hide matching cases from customer results and future deliveries, invalidate affected queued messages and persist across later imports. Records are not automatically restored just because source details later reappear.
Suppression limits distribution; it does not erase all internal records. Restricted source records and minimal case/property suppression identifiers remain to prevent reappearance and support review. Information already delivered, or a response or send already in progress, cannot always be stopped or recalled. Contact us if information needs attention before the next scheduled source check.
How long we keep information
The following describes application retention. Periods make information eligible for cleanup; deletion is not guaranteed to occur at the exact deadline. Cleanup runs in limited batches after a successful daily operator summary and can be delayed by outages or backlogs.
| Information | Application retention |
|---|---|
| County cases | Open cases remain while tracked, including restricted suppressed records. Closed cases become eligible for deletion 365 days after we record closure. Suppression identifiers survive case cleanup. |
| Operational job logs; sent or canceled messages | Eligible for deletion after 14 days. |
| Unsent email | Stops being claimed for delivery after 30 days. Cleanup cancels and clears its contents after any active processing lease ends; the canceled row then follows the 14-day rule. |
| Disabled webhook payloads | Cleared after 30 days; endpoint configuration and the delivery cursor remain until removal or account closure. |
| Detailed usage and delivery history | Generally 90 days. The latest daily delivery cursor remains to prevent duplicate delivery. Monthly export counters retain the current and three prior calendar months. |
| Expired invitations and revoked API keys | Invitations become eligible for removal 30 days after expiration; revoked keys 90 days after revocation. |
| Accounts and current product settings | Remain until account closure or removal through the relevant account controls. The current checkout recovery attempt remains until safely replaced or the account is closed. Policy receipts are removed with the associated authentication user. |
| Completed account-closure receipts | A minimal completion receipt remains for 365 days. Unfinished closures remain until resolved. |
| Suppression identifiers | Remain while the source is in use to prevent suppressed information from reappearing. |
Billing records, provider logs and backups, support email and postal scans are managed separately. We retain correspondence as needed to resolve requests, maintain necessary records, meet legal obligations and address disputes; we do not promise a fixed deletion period for those provider systems. Closing a NoticeFeed account does not automatically erase records in Stripe, the support mailbox or the postal-mail account. Contact us for a review of the relevant information. Information retained in backups remains subject to provider recovery and retention processes.
Your choices and requests
Use account controls to manage saved searches, email preferences and integrations. Record-update emails include unsubscribe options for the category and for all lead emails without requiring sign-in. Opting out of those emails does not cancel a subscription. Necessary account, security and billing messages may still be sent. You can also contact support about email preferences.
Contact support@noticefeed.com or write to our mailing address to request access to information, correction, suppression, deletion or account closure, or to ask about applicable sale/other privacy choices. Property owners do not need an account or subscription. Include enough information to locate the relevant records, such as a property address, case number or folio, and a way to reply. Authorized representatives may contact us; we may ask for evidence of their authority.
We assess the request and verify identity or authority as appropriate to its sensitivity. We explain the action taken, any information retained and the reason, any applicable exception, and any appeal rights or additional methods required by applicable law. Available statutory rights depend on the jurisdiction and circumstances, and we handle requests within applicable legal time limits. If you disagree with our response, reply to support and request a review. We do not charge for submitting a request or require a purchase.
Requests concerning your subscriber account, your appearance in property records and another recipient's outreach are different. Correcting NoticeFeed does not change the county's source record. Account closure removes logins and related application data after ownership and billing review, including addressing future renewal; it is separate from ordinary subscription cancellation. Suppressing property records does not necessarily erase restricted source copies. We will describe these distinctions when responding.
Security and notice changes
We use access controls, authentication and other safeguards to limit unauthorized access. No internet service or transmission is guaranteed completely secure. Protect account and integration credentials and contact support if you suspect misuse.
We identify this notice by version and effective date. We will communicate material changes and obtain consent where applicable law requires it. An update does not retroactively change what you previously acknowledged.