Last updated: September 20, 2026

PubMesh is a digital media network that operates publications, websites, newsletters, editorial products, publishing technology, and distribution channels. This Privacy Policy explains how PubMesh ("PubMesh," "we," "us," or "our") collects, uses, discloses, stores, and protects personal information when you interact with PubMesh or with a PubMesh-operated publication that links to this policy.

This is a network-level policy. PubMesh publications are generally editorial brands operating on shared PubMesh infrastructure, not separate privacy programs. Unless a publication gives you a separate privacy notice or identifies a different controller, this policy applies across the PubMesh network. Consent choices may still be scoped to the publication you are visiting so that a choice on one publication is not automatically treated as a choice for every other publication.

1. Scope

This policy applies to PubMesh websites and publication sites that link to it, newsletters, subscription forms, contact forms, reader-facing applications and features, events or promotions we operate, and connected publishing or distribution services when personal information is processed by PubMesh.

It does not govern a third-party website, social network, retailer, advertiser, payment provider, or other service that has its own privacy policy. When you follow a link to or interact directly with a third party, that third party's policy applies to its processing.

2. Information we collect

We collect information in three main ways: information you provide, information generated when you use our services, and information received from services you choose to connect.

Information you provide

Depending on the feature you use, this may include:

• your email address and newsletter preferences;
• your name, contact details, and the contents of a message you send us;
• account or profile information if a PubMesh service offers accounts;
• information you submit for a survey, promotion, event, correction request, editorial submission, or similar interaction;
• transaction, order, billing, shipping, or support information if a PubMesh publication offers commerce or paid products;
• information needed to administer a business, advertiser, contributor, creator, or commercial relationship; and
• information you provide when asking us to exercise a privacy right.

Our newsletter system uses confirmation-based subscription flows where configured. For the PubMesh network newsletter, email delivery uses double opt-in: subscribing requires confirmation, and you can unsubscribe at any time.

Information collected when you use our sites

Websites necessarily process some technical information to deliver pages securely. Depending on your device, browser, consent choices, and the publication you visit, this may include:

• IP address and network information processed by hosting, security, or delivery infrastructure;
• browser type, operating system, device type, language, and basic device characteristics;
• requested pages, referring page, timestamps, response and error information;
• interactions such as page views, story opens, publication referrals, network clicks, and, where applicable, advertising impressions or clicks;
• cookie, local-storage, consent, and preference information; and
• approximate location inferred from network information where a service provider makes it available.

Our current first-party PubMesh measurement system is consent-gated. Before the required analytics consent is given, optional first-party analytics events are not collected. The event collector is configured not to store raw IP addresses or raw email addresses in analytics events, does not create a persistent client identifier by default, and does not build cross-publication personalized reader profiles by default.

This does not mean an IP address is never processed. Internet, CDN, security, and hosting providers may need to process IP addresses transiently to route traffic, prevent abuse, and protect the service.

Information from connected services and third parties

If you choose to connect an account or service, such as a social media, distribution, commerce, advertising, analytics, or creator platform, we may receive information made available through that service's official authorization process. This can include account identifiers, profile information, page or channel information, publishing permissions, analytics, content metadata, or other information covered by the permissions you approve.

We do not ask you to provide the password to a third-party service when an official authorization flow is available. Authorization tokens or credentials needed to keep an approved connection working may be stored securely until the connection is revoked, expires, or is no longer needed.

We may also receive information from service providers, fraud-prevention and security providers, commerce partners, affiliate networks, advertising partners, publicly available sources, or business partners where permitted by law.

3. How we use information

We use personal information when reasonably necessary to:

• deliver websites, publications, newsletters, subscriptions, products, and features you request;
• confirm subscriptions and manage preferences;
• respond to messages, support requests, correction requests, and privacy requests;
• operate publishing, editorial, distribution, and connected-platform workflows;
• authenticate users and authorized connections where accounts or integrations are offered;
• protect our services, readers, systems, and partners against fraud, abuse, spam, attacks, and unauthorized access;
• understand how our publications and products perform;
• improve site reliability, reader experience, editorial products, and network navigation;
• measure aggregate audience and publication performance;
• administer advertising, sponsorships, affiliate programs, or commerce where a publication uses them;
• meet accounting, tax, contractual, regulatory, and other legal obligations;
• establish, exercise, or defend legal claims; and
• communicate material service, policy, security, or administrative changes.

We do not use sensitive personal information to target advertising. We do not use reader personal information to make decisions that produce legal or similarly significant effects about an individual.

Automation and AI-assisted tools may support editorial research, production, operations, support, or distribution. We do not treat reader personal information as a general-purpose training dataset for public AI models merely because you visit a PubMesh site or subscribe to a newsletter.

4. Legal bases where applicable

Where laws such as the EU or UK GDPR require a legal basis, our processing may rely on:

• Consent, for optional analytics, personalization, advertising technologies, marketing communications, or other processing where consent is required.
• Contract or steps requested by you, when processing is necessary to provide a subscription, product, account, connected service, or other feature you request.
• Legitimate interests, such as securing our services, preventing abuse, maintaining and improving our publications, understanding aggregate performance, and operating a sustainable media business, where those interests are not overridden by your rights.
• Legal obligations, when we must keep or disclose information to comply with law, regulation, court orders, tax, accounting, or other legal requirements.

You can withdraw consent at any time for future processing where consent is the basis. Withdrawal does not make earlier lawful processing unlawful.

5. Cookies, local storage, analytics, and privacy choices

PubMesh uses essential browser storage where needed to operate and secure services and to remember privacy choices. Optional categories such as analytics, functional features, personalization, and advertising are off by default where the applicable consent framework requires an affirmative choice.

Our current shared consent system is designed so that:

• essential functions remain available;
• optional processing does not start before the required choice;
• rejecting optional processing is intended to be as accessible as accepting it;
• newsletter consent is separate from site-tracking consent;
• a consent choice is not automatically shared across unrelated PubMesh publications;
• advertising and personalization are forced off when an applicable Global Privacy Control signal requires that result; and
• you can change or withdraw a choice later.

For details and controls, see Cookies & Privacy Choices and the Privacy Choices page linked in the footer.

6. Advertising, affiliate links, and sponsored content

Some PubMesh publications may use advertising, sponsorships, affiliate links, or commerce relationships to support their work. Those commercial relationships are addressed in our Advertising & Affiliate Disclosure.

We do not currently sell personal information for monetary consideration. Some advertising technologies can, however, be legally classified as "sale," "sharing," targeted advertising, or cross-context behavioral advertising in certain jurisdictions even when no money is paid for the information itself. Where a PubMesh publication uses technology that falls within those definitions, we will provide the consent or opt-out mechanism required by applicable law.

Advertising, personalization, and similar optional technologies are not treated as essential site functions. When consent is required, they may operate only after the relevant choice.

Specific advertising or measurement vendors can change over time. Vendor-specific technologies and choices may be identified through the applicable cookie or privacy-choice interface.

7. How we disclose information

We may disclose personal information to the following categories of recipients when reasonably necessary:

Service providers

We use companies that provide infrastructure, databases, security, content delivery, object storage, email delivery, hosting, communications, analytics, payment, commerce, support, and other technical or professional services. They process information for us under the terms of their services and applicable contractual or legal obligations.

Examples of core infrastructure currently used by PubMesh include:

• Supabase / PostgreSQL for operational database services. The current primary Dogu-One operational database is hosted in the EU Central (Frankfurt / eu-central-1) region.
• Cloudflare for network, security, delivery, and object-storage services used by PubMesh systems and media assets. Cloudflare operates global infrastructure.
• AWS email services for email delivery and related mail operations.
• Hostinger and related infrastructure providers for compute and runtime services supporting parts of the PubMesh platform.

Providers and architecture may change as we improve the service. When we move data between providers, we continue to apply this policy and applicable legal requirements.

Connected platforms and partners

When you intentionally connect or use a third-party service, we may exchange the information needed to perform the action you requested. For example, publishing to or reading authorized information from a connected social platform requires communication with that platform.

Advertising, affiliate, and commerce partners

Where a publication uses these services, limited identifiers or interaction information may be disclosed as necessary to attribute a referral, deliver or measure advertising, complete a transaction, or provide a requested commercial feature, subject to applicable consent and opt-out requirements.

Legal and safety disclosures

We may disclose information if reasonably necessary to comply with law or legal process, respond to lawful government requests, protect rights or safety, investigate fraud or abuse, enforce agreements, or protect PubMesh systems and users.

Corporate transactions

If all or part of PubMesh is reorganized, financed, acquired, merged, sold, or transferred, relevant information may be transferred as part of that transaction subject to applicable law and appropriate safeguards.

We do not disclose connected-platform credentials for unrelated marketing purposes.

8. Central operation across the PubMesh network

PubMesh uses shared infrastructure to operate multiple publications efficiently. This means functions such as security, hosting, newsletter delivery, legal requests, system administration, aggregate measurement, and publishing operations may be handled centrally by PubMesh rather than separately by each editorial brand.

At the same time, our current reader-measurement and consent architecture is deliberately conservative: publication consent is scoped to the publication, cross-publication consent sharing is off, and first-party analytics does not create a cross-publication personalized reader profile by default.

We may use de-identified or aggregate statistics across the network to understand overall reach, system health, editorial performance, or business performance.

9. Where information is stored and processed

PubMesh is an internet-based media network and uses service providers in more than one country.

Our current core operational database is hosted in the European Union, in the AWS eu-central-1 region (Frankfurt, Germany) through Supabase. Other information may be processed or stored by infrastructure, security, email, content-delivery, object-storage, social-platform, analytics, advertising, commerce, or professional-service providers in the United States, Canada, the European Economic Area, the United Kingdom, Türkiye, or other countries in which those providers operate.

Static editorial media and publication assets may be stored separately from operational reader records, including in distributed object-storage and content-delivery systems.

Service credentials and secrets used by PubMesh systems are managed separately from public website content using access-controlled secrets-management infrastructure.

Where applicable law restricts international transfers of personal information, we use appropriate contractual, organizational, or technical safeguards and rely on legally recognized transfer mechanisms where required.

10. Retention

We retain personal information only for as long as reasonably necessary for the purpose for which it was collected, including to provide requested services, maintain security, comply with law, resolve disputes, and enforce agreements.

Retention depends on the type of information and the relationship involved. For example:

• newsletter subscription information is generally retained while the subscription remains active and for a limited period afterward where needed to honor unsubscribe or suppression requests;
• consent and privacy-choice records may be retained to remember and demonstrate the choice you made;
• contact and support correspondence may be retained while a matter is active and for a reasonable follow-up period;
• connected-platform credentials are retained only while needed to operate the authorized connection and are removed or made unusable when the connection is revoked or no longer needed, subject to backup and security processes;
• security and operational logs are retained for limited periods appropriate to troubleshooting, fraud prevention, and security; and
• transaction, accounting, tax, or legal records may be retained for the period required by applicable law.

When information is no longer needed, we delete it, de-identify it, or isolate it from ordinary use where deletion is not immediately possible, such as within limited backup cycles.

11. Security

We use administrative, technical, and organizational measures intended to protect personal information from unauthorized access, alteration, loss, misuse, or disclosure. Measures may include access controls, encrypted transport, network protections, separation of service credentials from public content, secrets management, least-privilege access, logging, backups, and vendor security controls.

No internet service can guarantee absolute security. If we become aware of a personal-data incident requiring notification, we will provide notice as required by applicable law.

12. Your privacy rights

Your rights depend on where you live and the law that applies. They may include the right to:

• know whether and how we process your personal information;
• request access to or a copy of personal information;
• correct inaccurate information;
• request deletion;
• request portability of information you provided;
• object to or restrict certain processing;
• withdraw consent;
• opt out of targeted advertising, sale, or sharing where those concepts apply;
• limit certain uses of sensitive personal information where applicable;
• unsubscribe from marketing communications; and
• appeal a privacy-rights decision where applicable law provides an appeal right.

You may exercise a privacy right by emailing privacy@pubmesh.media. You may also use the Privacy Choices and Data Deletion pages linked from PubMesh sites for relevant controls.

We may need to verify a request before acting on it. Verification is used to protect information from unauthorized access or deletion. If applicable law permits an authorized agent to act for you, we may request evidence of that authority and, where permitted, confirmation of your identity.

We will not discriminate against you for exercising a legally protected privacy right.

Residents of the European Economic Area, United Kingdom, or Switzerland may also have the right to lodge a complaint with their local data-protection authority. Residents of U.S. states, Canada, and other jurisdictions may have additional rights under their local privacy laws.

13. Marketing communications

You can unsubscribe from a PubMesh newsletter by using the unsubscribe mechanism in the message or by contacting us. Unsubscribing from editorial or promotional email does not prevent us from sending non-marketing messages that are necessary to complete a transaction, respond to a request, provide a requested service, or address security or legal matters.

14. Children

PubMesh is a general-audience media network. We do not knowingly use our general reader services to collect personal information directly from children under 13 in the United States or below another age where local law requires parental consent.

Some PubMesh editorial brands may publish family, parenting, education, or children's content. Unless a specific service clearly says otherwise, those products are intended to be used or administered by parents, guardians, or other adults and are not designed to solicit personal information from children.

If you believe a child has provided personal information to us in a way that is not permitted, contact privacy@pubmesh.media.

15. Third-party links and embedded services

PubMesh content may link to or embed websites, products, videos, social posts, commerce offers, maps, players, or other services operated by third parties. Those services may collect information independently under their own policies. A link, mention, review, affiliate relationship, or embed does not make PubMesh responsible for the third party's privacy practices.

Where an embedded or optional third-party technology requires consent, we aim to apply the relevant consent control before activating it.

16. Public submissions

If you intentionally submit information for public posting, such as a comment, testimonial, public profile, reader submission, or other material intended for publication, the information you choose to make public may be visible to others and may be copied or indexed outside PubMesh. Do not submit information publicly that you do not want others to see.

17. Changes to this policy

We may update this Privacy Policy when our services, technology, business model, providers, or legal obligations change. The "Last updated" date at the top shows when this policy was most recently revised.

If a change materially affects how we use personal information, we will provide additional notice or obtain consent where required by law.

18. Contact us

For privacy questions, rights requests, or concerns:

privacy@pubmesh.media

For general legal matters:

legal@pubmesh.media

When contacting us about a particular publication, subscription, connected account, or service, please identify it so we can route and verify the request efficiently.