Privacy notice
This notice explains how Insolvation handles personal data in connection with insolvation.com, including article-alert subscriptions, site operations, first-party analytics, and security logging.
Data fiduciary. For the public site and newsletter surfaces on insolvation.com, the data fiduciary is Insolvation, reachable at info@insolvation.com. Service and infrastructure support may be provided by hosting, email relay, and analytics processors acting on its behalf.
Registered or operating address: Online publishing service operated through insolvation.com
Email address, confirmation status, subscribe and unsubscribe timestamps, source surface, page path, user agent, IP address used at signup or confirmation, notice version, policy version, and consent-proof records.
If you contact us by email or through any future contact form, we may process your name, email address, message contents, attachments, and correspondence history needed to respond and maintain a record of the request.
The site currently uses first-party analytics and readership metrics. Where analytics preferences are offered, they are kept separate from essential site operation. We also store a browser-side consent preference for analytics choices.
Server logs, request metadata, IP address, timestamps, error traces, and operational security events may be processed for abuse prevention, incident detection, debugging, performance, and audit trail purposes.
When you subscribe, the site asks for specific consent for new-article alerts. That consent is not bundled with general browsing, analytics preferences, or unrelated communications.
Subscribe forms on insolvation.com display a just-in-time notice explaining what is collected, why it is collected, how long records are kept, and where privacy-rights information can be found. Verified privacy-rights requests are also tracked in a dedicated backend workflow rather than remaining only as unstructured email correspondence.
| Category | Purpose | Examples of data involved |
|---|---|---|
| Email delivery / SMTP relay | confirmation emails, new-article alerts, verification emails, unsubscribe handling | email address, delivery metadata, message event logs |
| Hosting and infrastructure providers | site hosting, reverse proxying, uptime, backups, operational security | request logs, server logs, technical metadata |
| Analytics and measurement services | first-party readership and site-performance reporting | page path, timestamp, coarse technical/browser metadata, aggregated metrics |
| Security and debugging tools | fraud detection, abuse control, incident response, diagnostics | IP address, logs, error traces, request context |
| Data set | Retention approach |
|---|---|
| Pending subscription records | kept for up to 30 days unless confirmed sooner, then automatically removed by scheduled cleanup |
| Active subscriber records | kept while the subscription remains active and for as long as needed to deliver requested alerts and maintain consent history |
| Unsubscribed / suppression records | retained for up to 1825 days to respect the unsubscribe choice and prevent accidental resubscription mailings without renewed consent |
| Consent-proof events | retained with the related subscription record and suppression trail for auditability and dispute handling |
| Outbound mail event logs | retained for up to 365 days for delivery troubleshooting and abuse monitoring |
| Delivery verification runs | retained for up to 365 days for operational proof and regression checking |
| Privacy-rights / grievance workflow records | retained for up to 1825 days after closure unless a longer period is reasonably required for compliance, disputes, or legal hold |
| Security logs | generally retained for up to 90 days unless a longer period is reasonably needed for an active investigation, legal hold, or security incident |
| Analytics data | aggregated or event-level first-party analytics may be retained for up to 365 days, then deleted, reduced, or rolled into longer-term aggregate reporting |
| Contact or grievance correspondence | kept for as long as required to resolve the request and maintain a reasonable compliance record |
When you unsubscribe, Insolvation stops sending article alerts to that address. Some minimal suppression information may still be retained to ensure the unsubscribe choice is honored, prevent accidental re-mailing, support abuse controls, and preserve a compliance trail. Scheduled retention cleanup is designed to remove expired pending records and aged logs while preserving valid suppression integrity during the stated retention window.
Insolvation separates essential site operation from optional analytics preferences. The site may store a browser preference indicating whether you accepted or rejected analytics. Essential security and operational cookies, if any, are distinct from optional measurement choices.
| Category | Provider | Purpose | Duration |
|---|---|---|---|
| Essential | insolvation.com | security, routing, core site operation, load balancing, and abuse prevention | session or short operational period |
| Analytics preference | insolvation.com | stores whether you accepted or rejected optional analytics features | up to 12 months unless changed sooner |
| Analytics / readership measurement | first-party Insolvation analytics | article and page readership measurement, aggregated reporting, and performance monitoring | event retention governed by the analytics retention logic above |
If client-side non-essential analytics or marketing cookies are introduced later, Insolvation should seek consent before setting or using them.
Public subscription surfaces should ask only for the data needed for that purpose. For article alerts, the required field is the email address. Users should avoid sending unnecessary personal or sensitive information in any free-text contact channel.
You can request access, correction, deletion where applicable, withdrawal of consent, or help with unsubscribe and suppression issues. Insolvation may request reasonable information to verify identity before acting on a request affecting personal data. Verified requests are tracked in a dedicated backend workflow with status, timestamps, and resolution notes.
Depending on infrastructure choices, data may be processed in more than one jurisdiction. Insolvation uses hosting, email, analytics, and operational processors as needed to run the service. Access is intended to be limited to personnel and processors with a need to know. Security controls may include access restriction, audit trails, configuration controls, scheduled retention enforcement, and breach or incident handling procedures.
Insolvation may update this notice to reflect legal, technical, or operational changes. The effective policy version shown on this page is the version referenced in current collection-point notices and consent records.