1import"../chunks/Bm6YAp9C.js";import"../chunks/8eo8wfh5.js";import{g as c,e as r,i as u,f as d,a as o,b3 as h,$ as y,b4 as p,h as v}from"../chunks/CYT7WipP.js";import{h as m}from"../chunks/BrbfiLnh.js";import{D as b}from"../chunks/CPVm3LpO.js";import{I as f}from"../chunks/HkTH11pB.js";import{C as g}from"../chunks/CQEponjN.js";var w=r('<div class="callout-icon svelte-h2tfa5"><!></div>'),P=r('<div class="title svelte-h2tfa5">Non-binding Summary</div>'),H=r(`<ul><li>HYVOR is a privacy-focused company.</li> <li>We only collect data necessary for the operation of Hyvor Post.</li> <li>We only share your data with third parties when necessary for the operation of Hyvor 2 Post. This includes email delivery.</li> <li>We never sell data to third parties.</li></ul>`),$=r(`<p>This Privacy Policy extends the general privacy policy available at <a href="/privacy">hyvor.com/privacy</a>. It specifically addresses how Hyvor Post collects, uses, and protects data.</p> <p>By using Hyvor Post, you agree to the practices described here and in our main Privacy 3 Policy.</p> <!> <hr/> <h2 id="definitions">1. Definitions</h2> <ul><li><strong>User:</strong> A person who creates a Hyvor Post account to manage their content 4 and newsletters.</li> <li><strong>Subscriber:</strong> A person who subscribes to a newsletter created by a Hyvor Post 5 user.</li> <li><strong>You:</strong> A customer, subscriber, or entity who visits our Services.</li></ul> <h2 id="introduction">2. Information We Collect</h2> <p>In addition to the account data collected on hyvor.com, Hyvor Post may collect the 6 following:</p> <h3 id="newsletter-data">2.1 Newsletter-Specific Data</h3> <ul><li><strong>Subscriber Information:</strong> Names and email addresses of people who subscribe 7 to your newsletters. This data is provided by you or collected via your public subscription 8 forms.</li> <li><strong>Content Data:</strong> Newsletters, drafts, and metadata you create within the Hyvor 9 Post platform.</li></ul> <hr/> <h2 id="data-usage">3. How We Use This Information</h2> <ul><li>To deliver your newsletters to your subscribers.</li> <li>To help you manage, export, or delete your subscriber list.</li> <li>To improve our service and diagnose issues.</li></ul> <p>We do not sell, rent, or use your data or your subscribers' data for any advertising 10 purposes.</p> <hr/> <h2 id="data-retention">4. Data Retention</h2> <ul><li>We retain your data for as long as you have an active Hyvor Post account or until you 11 request deletion.</li> <li>You can delete your account and all associated data at any time through the Hyvor Post 12 Console.</li> <li>We may retain some data for legal or compliance purposes, but it will be anonymized or 13 pseudonymized where possible.</li></ul> <hr/> <h2 id="data-sharing">5. Data Sharing</h2> <ul><li>Your data can be shared with law enforcement or regulatory bodies when required by law 14 or to protect our rights.</li></ul> <hr/> <h2 id="data-processors">6. Data Processors</h2> <p>We use GDPR-compliant sub-processors (e.g., email delivery providers) to send newsletters 15 and ensure platform stability. A full list is available at the <a href="/sub">sub-processors of HYVOR</a>.</p> <hr/> <h2 id="our-servers">7. Our Servers</h2> <p>All data collected by Hyvor Post is stored on secure servers located in the European Union. 16 We use industry-standard security measures to protect your data.</p> <hr/> <h2 id="your-rights">8. Your Rights</h2> <p>Subscribers have the right to unsubscribe from newsletters at any time. You can do this by 17 clicking the "Unsubscribe" link in any newsletter email or by contacting the Hyvor Post user 18 who sent you the newsletter.</p>`,1);function U(l){m("h2tfa5",i=>{c(()=>{y.title="Privacy Policy | Hyvor Post"})}),b(l,{title:"Privacy Policy (Hyvor Post)",subtitle:"Last Updated: 2025-06-01",children:(i,W)=>{var a=$(),n=u(d(a),4);g(n,{icon:t=>{var e=w(),s=h(e);f(s,{size:30}),p(e),o(t,e)},title:t=>{var e=P();o(t,e)},children:(t,e)=>{var s=H();o(t,s)},$$slots:{icon:!0,title:!0,default:!0}}),v(52),o(i,a)},$$slots:{default:!0}})}export{U as component};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.