Information Security Policy

1. Introduction

PressFudge operates pressfudge.com, a press release distribution service. Every order involves material our customers trust us with: account details, unpublished press releases, company information and payment records. Protecting that material is part of the service itself, not an afterthought. This policy explains, in plain language, the security measures we run, what happens if something goes wrong, and the small number of things we ask you to do on your side. It is a summary of our practices for customers and partners; it sits alongside our Privacy Policy, which explains what personal data we collect and why.

2. Information we protect

The information covered by this policy falls into four groups. Account information: your name, email address and login credentials. Order and content information: the press releases, briefs, company details, images and links you submit for distribution, together with your order history. Payment records: the amount paid, the network used and the transaction ID (TXID) you provide for a USDT payment. Communications: messages you exchange with our team through the site, email, contact forms and live chat.

3. Encryption and password security

Every page of pressfudge.com is served over HTTPS with an SSL/TLS certificate, so information moving between your browser and our servers is encrypted in transit - including sign-in, checkout and your dashboard. We recommend you never use the site over a connection your browser flags as not secure. Your password is never stored in readable form: it is processed with a one-way cryptographic hash, which means nobody at PressFudge can see or recover it, and a forgotten password can only be replaced, never retrieved. If you use the "remember me" option, your browser holds a revocable token rather than your password, and signing out invalidates it.

4. Payment data security

PressFudge accepts payment in USDT (Tether) only, sent from your own wallet to the receiving address shown on your order page. Because of how we take payment, a whole category of risk simply does not exist here: we never receive, process or store bank card numbers, card security codes, wallet private keys or seed phrases, and no PressFudge page will ever ask you for them. Anyone who contacts you asking for a seed phrase or private key is not us - stop and tell us immediately. The only payment data we keep is the record needed to run your order and our accounts: package, amount, network (TRC20, ERC20 or BEP20) and the TXID you submit. Transaction IDs are visible on the public blockchain by design; they are not treated as secrets, but we still store and handle them as part of your private order record. How payments work in full is set out in our Payment Policy.

5. Access control

Access to customer information inside PressFudge is limited to the people who need it to do their work. Team members use individual accounts - shared logins are not permitted - and administrative access to order and customer records sits behind a separate, restricted admin panel that customers never see. Access is granted on a least-privilege basis, and it is removed when a team member changes role or leaves. On the customer side, your account can only ever see your own orders, files and reports; the system checks ownership on every order, deliverable download and report link, so one customer cannot open another customer's material by guessing an address.

6. Server and application security

The site runs on professionally managed hosting with server-level firewalls, and the underlying software - server operating system, PHP runtime, framework and libraries - is kept patched, with security updates applied as they become available. The application itself is built with standard protections throughout: forms are protected against cross-site request forgery (CSRF), sessions are carried in secure cookies (see our Cookie Policy), uploaded files are restricted to safe document types and stored outside the public web root, and content you submit through our article editor is filtered to strip scripts and other active code before it is stored or published.

7. Backups and availability

We keep regular backups of the site and its database so that orders, accounts and reports can be restored if the hosting environment fails. Backups are access-controlled in the same way as live data. If the site is unavailable for a period, your published placements and reports are unaffected - they live on the independent news outlets that carried your release.

8. Monitoring and logging

We keep logs of sign-ins, administrative actions and system errors, and we review them for signs of misuse - for example, repeated failed sign-in attempts or attempts to reach records that do not belong to the signed-in account. Automated safeguards, including rate limits on sensitive forms such as sign-in, password reset and order-status lookups, reduce the value of automated attacks.

9. If something goes wrong: incident handling

If we detect a security incident - unauthorised access, a compromised account, or a credible report from a customer - our response follows a fixed order: contain it (lock accounts, revoke sessions, block the source), preserve the evidence, assess what information was involved, and fix the root cause before restoring normal operation. Where an incident affects your personal data and the law requires notification, we will tell you without undue delay, explain what happened and what we have done, and advise you on any steps worth taking, such as changing your password. You can report a security concern at any time to hello@pressfudge.com; reports from customers have helped us before and are always taken seriously.

10. Your responsibilities

Security is shared. We ask you to: use a strong, unique password for your PressFudge account and never share it; sign out on shared devices; double-check the network and receiving address on your order page before sending any USDT payment, because blockchain transfers cannot be reversed; only ever copy payment addresses from your own signed-in order page, never from an email or message claiming to be us; and tell us straight away if you notice anything suspicious about your account or orders. PressFudge staff will never ask for your password.

11. Third parties

We rely on a small number of established providers - principally our hosting company and email delivery - and we only work with providers that protect data to a comparable standard. We do not sell customer information, and we do not hand order records to third parties except where needed to deliver your distribution (for example, your release itself is, by the nature of the service, sent to the news outlets that publish it) or where the law requires it.

12. Changes to this policy

We review this policy as our systems and the threat landscape change. The current version will always be published on this page with its effective date; material changes to how we protect your information will be reflected here before or as they take effect.

Contact: Questions about security or this policy - email hello@pressfudge.com or call +1 (332) 291-2175.