Privacy Policy
How information is handled across the agency website and the intended PMN News contributor workflow—and what still needs confirmation.
Information collected
This policy covers the PMN Global website and the News features implemented in its code. PMN’s legal operator identity and the full processing details of the separately hosted contact portal require confirmation.
Information you choose to send may include your name, email address, organization, enquiry and correspondence. The separate contact portal presents fields for name, email, phone, profile type, what you are looking for, a profile link, a message and consent. Ordinary website requests also expose technical information such as IP address, requested URL, browser information and request time to hosting and delivery services. The exact hosted logging settings have not been verified.
The News backend has not yet been set up. The account, submission and upload sections below explain the intended handling when those features become available; they do not claim that PMN is currently receiving contributor data through them.
Reasons for data collection
Enquiry information is used to understand and respond to the conversation you initiate. When contributor features are enabled, account information supports sign-in and permissions; submissions, sources and images support editorial review and publication; operational records support moderation, access checks and abuse prevention.
These descriptions identify the purposes visible in the implementation. They do not establish a legal basis for every activity. Applicable legal bases, any consent requirements and any further agency use of enquiry information require confirmation before the affected processing is undertaken.
Account and contributor information
The intended News sign-in uses email and a one-time code through Supabase Auth. Account creation may follow verified sign-in. Profile records include a user identifier, display name, biography, role and creation time. PMN does not ask contributors to choose an account password in this workflow.
The implementation uses a hashed email identifier for a sign-in rate-limit record. Hashing that identifier does not mean the account email is anonymous: the authentication service still needs the email address. Your byline and any author details included in a published article may be public; the private login email is not a published article field.
Article submissions
A submission can contain a title, summary, article body, category, byline, tags, source links, organization, original-source details, a cover image reference and rights/policy acknowledgements. The intended database also stores revisions, review feedback, status changes and publication records.
Drafts and submissions are designed to be accessible according to contributor and editorial permissions. Approved published article content, bylines, sources and selected images become available to readers. Published material can be copied by readers or indexed by search engines; withdrawing an article does not itself remove copies held elsewhere.
Uploaded documents and images
The implemented contributor upload accepts JPEG, PNG and WebP images, not arbitrary documents, PDFs or video files. It checks file signatures, size and dimensions, re-encodes accepted images as WebP and creates a thumbnail. It stores image identifiers, ownership, dimensions, alternative text, captions and credits.
Accepted image processing does not deliberately retain the original file’s embedded metadata, but faces, addresses and other private information visible in the image itself can remain. Do not upload sensitive records or images you lack permission to use. Documents sent separately by email or through the contact portal need separate handling and retention review.
Data storage and third-party services
Vercel hosts the main website. The unconfigured News integration is built for Supabase Auth, a Postgres database and a private news-media storage bucket. Uploads and image delivery are designed to check access through the website rather than exposing a public storage bucket.
Emails and sign-in delivery depend on the email services actually configured. The separate contact portal’s backend is not part of the reviewed repository. Its storage provider and processing flow have not been confirmed. No specific hosting country, international-transfer arrangement, backup policy or subprocessor contract is claimed in this document.
Security practices
Implemented controls include verified sign-in checks, role-based permissions, database row-level access policies, server-side validation of submissions and images, and access checks for image requests. Session cookies are configured with HttpOnly, SameSite and secure transport settings in production.
These controls describe code, not a certification or a guarantee that the unconfigured hosted backend has been secured or independently audited. No system can be promised completely secure. Do not share sign-in codes or unnecessary sensitive information, and use the contact details below to report a concern.
Data retention
No approved retention schedule was supplied for enquiries, accounts, submissions, media, revisions, editorial records, authentication logs or backups. The code does not establish a complete automatic deletion schedule for those categories. No fixed number of days or years is promised here.
The owner must define retention criteria for active enquiries, ongoing service obligations, editorial history, legal requirements, security and dispute handling, including what happens after account closure. Unpublishing or marking an article deleted does not by itself demonstrate that every related record, media object, cache or backup has been erased.
Your privacy rights
Depending on the law that applies and the circumstances, you may have rights to request access, correction, deletion, restriction or objection to processing, or a copy of certain information. Where processing relies on consent, withdrawal may also be relevant. These rights are not presented as unconditional or identical in every location.
Contact PMN to raise a request or concern. The owner and legal reviewer must confirm applicable rights, exceptions, response periods and any right to contact an appropriate regulator. This document does not establish a regulator, data protection officer or statutory deadline.
Correction and deletion requests
Email the contact in section 15 with a clear description of the information or article involved and the correction or deletion you seek. Include the relevant URL and an account email where appropriate. Do not include passwords, sign-in codes or unsolicited identity documents.
PMN may need proportionate information to confirm the request relates to you and to protect other people’s records. No self-service account deletion flow is currently implemented. A request involving published journalism, legal obligations or editorial records may need a different assessment from a profile correction; do not assume a request automatically removes every record or third-party copy.
External services and links
The contact portal at connect.pmnglobal.info is operated as a separate website experience. Its form and Google Analytics requests were observed without submitting information. No Terms or Privacy page link was found in its page links during that inspection; the owner must resolve the notice and consent arrangements before this policy can cover the full contact journey. The main contact page itself links to that portal or opens your email application; the current page does not submit an enquiry to a main-site contact database.
Email attachments, external publications, source links and other websites are handled through their own services and notices. This policy does not describe an unverified portal backend as if it were part of the News database.
Policy changes
This policy may be revised as operating arrangements change or further details are confirmed. Its version and review date must accurately reflect the services enabled at the time.
Before introducing new collection, optional analytics, new sharing arrangements or materially different uses of information, PMN must review the notice and any required communication or consent steps. Merely changing a policy does not itself establish permission for a new use.
Privacy contact information
Use PMN’s existing business email below for privacy questions, correction requests or concerns about submitted material. Use a subject such as “Privacy request” and provide only the information needed to identify the issue. No dedicated privacy officer or separate privacy mailbox has been confirmed.
The owner must confirm who monitors this address, how requests are recorded and escalated, and what legal contact details must accompany the final notice.