Trust & Security
How Geminga Newswire handles your data, secures your account, and keeps your releases moving — written plainly for the teams doing due diligence.
When you distribute a press release through Geminga Newswire, you are trusting us with your content, your account, and the analytics that measure your reach. This page sets out, without embellishment, what we collect, who processes it on our behalf, and the practices we use to protect it. Where a topic has a fuller legal treatment, we link to it rather than paraphrase.
Geminga operates the Service at geminganewswire.com. Nothing here should be read as a certification claim — see Security Practices for how we frame that.
Data Handling
Our distribution analytics are designed to measure the performance of a release, not to build profiles of the people who read it. For each distributed press release we collect:
- Aggregate reach — how many times a release was served across our website, feeds, and syndication partners.
- Pixel views — impressions from the transparent tracking pixels embedded in distributed releases, used as a coarse measure of opens and scroll depth.
- Click tracking — clicks on the short links that replace outbound URLs inside a distributed release.
Two commitments matter most to buyers evaluating us:
- We do not sell personal data. Analytics exist to report your reach back to you, not to be brokered onward.
- IP addresses are not shared with customers or with distribution partners. We use them internally for bot filtering, approximate country-level geolocation, and rate limiting; partners and customers receive only aggregate, non-identifying metrics.
For the full inventory of what each pixel, short link, and tracked asset records — and the reader-facing controls to reduce it — see our Privacy & Tracking disclosure.
Subprocessors
We rely on a small set of established infrastructure providers to run the Service. Each processes data only for the purpose noted below and under its own security and privacy commitments.
| Subprocessor | Purpose |
|---|---|
| Hetzner | Application hosting and server infrastructure |
| Cloudflare | CDN, edge delivery, and DDoS protection |
| Stripe | Subscription billing and payment processing |
| ZeptoMail / Zoho Mail | Transactional email (invitations, notifications, receipts) |
| Website analytics for our public pages |
This list is kept consistent with the recipients named in our Privacy & Tracking notice. Some providers operate outside the EEA and UK; where personal data is transferred internationally we rely on the lawful transfer mechanisms those providers make available.
Security Practices
We describe our security as a set of practices we actually follow — not as certifications we have not earned. Concretely:
- Encrypted transport — all traffic to and from the Service is served over HTTPS/TLS.
- Hashed passwords — account passwords are stored as one-way hashes, never in plain text.
- Role-based access control — organizations assign members one of five roles (viewer, editor, approver, admin, owner), so people see and do only what their role permits.
- Session management — authenticated sessions are server-managed, with CSRF protection on the dashboard and admin areas.
- Payment data stays with Stripe — card numbers are handled entirely by Stripe. We never see or store full card details.
Compliance Posture
Our data handling is GDPR-aware: we identify a legal basis for each category of processing, minimise what we collect, and support data-subject rights including access, correction, deletion, restriction, objection, and portability. The specific legal bases and the process for exercising your rights are set out in our Privacy & Tracking notice.
Compliance for the content of a release remains with the issuer. You are responsible for meeting the regulatory requirements that apply to your announcements — for example SEC disclosure rules or FTC advertising and endorsement standards — as described in our Editorial Guidelines. We provide the distribution rails; the accuracy and lawfulness of what travels on them is yours.
Uptime & Status
We aim to keep the Service and its feeds continuously available, and we publish live availability rather than ask you to take our word for it. For current uptime and any active incidents, see our status page.
Questions from your security team?
If your procurement or security review needs detail beyond what is on this page, reach out through our Contact page and we will respond with specifics.
View Plans