Privacy Policy

Effective date: October 27, 2026

This policy describes what information is handled when you read prsourcecode.com, how the operator uses it and what choices you have. The operator is whoever runs this blog about tech PR tools, media relations and press releases. Where the policy says we or us, it means that operator.

What our servers record

When a page of Prsourcecode is requested, the servers that deliver it normally log technical details. These can include your IP address, the time of the request, the address of the page, the browser and device type, and the page that sent you here. We use these records to keep the blog available, to investigate errors and abusive traffic, and to see in broad terms which articles on PR software, pitching or release writing attract readers.

Cookies and similar storage

The blog may place cookies or use comparable browser storage. Some support basic page function. Others, where switched on, count visits, remember a display choice, support advertising or note which article led a reader to a software vendor so that an affiliate referral can be credited. A cookie set by an analytics, advertising or affiliate provider is under that provider’s control, not ours, so its notice is the place to check how it is used.

Controlling tracking in your browser

You can clear or block cookies in your browser, browse privately, or use extensions that restrict trackers. If your browser sends a do-not-track or global privacy signal, we treat it as an opt-out request wherever the tools we use are able to honour it. Some features may behave differently once cookies are blocked.

Email and anything you send us

If you write to [email protected], we receive your address and the content of your message. Because readers sometimes work in communications, a message may mention a company, a campaign or a journalist. Please share only what is needed. We use messages to reply, to correct articles and to keep a record of the exchange. We do not sell them, and we will not publish them or name you without asking first.

Newsletters and forms

If the blog offers a newsletter or a form, the details you enter are used only for that purpose, such as delivering the updates you asked for. Any mailing will include a way to opt out, and a short email to us will also get your address taken off the list.

Outside services we rely on

Publishing online depends on other providers. These can include hosting and content delivery, audience analytics, advertising and affiliate networks, and embedded material such as videos or social posts. They may receive technical data about your visit so their service works, and they handle it under their own policies.

Retention

Server logs are kept for a limited time and then deleted or reduced to anonymous totals. Emails are kept while they remain useful for answering you, correcting a page or meeting a legal duty, and are removed once that need has passed.

Asking about your information

Depending on where you live, you may be entitled to ask what personal information we hold, to have it corrected or erased, to object to certain uses and to withdraw consent given earlier. Email [email protected] with a short description of your request. We may need to confirm your identity first, and we will respond within the period the law sets.

Children

Prsourcecode is written for working and aspiring communications people and is not aimed at children under 13. We do not knowingly collect information from children. If you think a child has written to us, let us know and we will delete the message.

Security

We take reasonable steps to protect information, such as secure connections and limited access to the inbox. No system connected to the internet is entirely safe, so we cannot guarantee absolute protection.

Data crossing borders

Providers that support this blog may process data in other countries, where the rules can differ from those near you. By continuing to read the blog you accept that your information may be handled in this way.

Updates to this policy

We may revise this policy as the blog or the law changes. The effective date above shows when the current version began, and continuing to use the blog after a revision means you accept it.