Privacy & Data Handling Policy

How your information is collected, stored, used, and protected on In His Head.

1. Who runs In His Head?

In His Head is run by a single individual as a personal awareness project. It is not a business, charity, or registered organisation.

All privacy and data-related enquiries can be made through the contact form on this website.

2. What information we collect

2.1 Information you choose to submit

This includes:

• Stories submitted through the Share Your Story form
• Replies posted on individual stories
• Messages sent through the contact form
• Optional fields such as name, age range, and country
• Any text you voluntarily submit

You may choose to post anonymously. You should avoid sharing identifiable details about yourself or others.

2.2 Technical information

Like most websites, basic hosting logs may collect:

• Browser and device type
• Approximate region (not precise location)
• Pages visited
• Time of access

No advertising pixels, tracking cookies, or behavioural analytics are used unless explicitly added in future.

3. How your submitted content is used

Stories and replies may be reviewed, lightly edited, categorised, and published on the website if approved.

Your content is used only to:

• Provide a platform for shared experiences
• Promote awareness around men’s mental health
• Support others who may relate to your story

We do not:

• Sell your data
• Share it with advertisers or third parties
• Use your content commercially
• Post your content outside this website without permission

4. How long we keep your data

Published stories and replies: kept indefinitely unless removal is requested.

Unpublished submissions: kept for up to 30 days before deletion.

Contact messages: kept as long as needed to respond and maintain records.

5. Where your data is stored

Data submitted through forms is processed by Netlify Forms, which stores submissions on secure servers.

Approved stories and replies are stored in JSON files that are part of the website build.

No complex databases or third-party integrations are used.

6. Who can access your data

Only the individual running In His Head has access to:

• Story submissions
• Replies
• Contact messages

No external moderators, volunteers, or partners have access to raw submission data.

7. Your rights

Under GDPR (UK/EU), you have the right to:

• Request copies of personal data you’ve submitted
• Have your data corrected
• Request deletion of your story, reply, or contact message
• Withdraw consent at any time
• Change your displayed name to “Anonymous”
• Ask how your data is stored or handled

To exercise these rights, use the Contact page.

8. Anonymous submissions

If you choose to submit anonymously:

• Your name is not stored
• No identifying information is recorded
• Your IP address is not used to personally identify you

9. Sensitive topics & safety

Stories may include emotionally sensitive content. If a submission indicates immediate danger or crisis, it will not be published. Instead, we signpost to crisis resources in the Support section.

We do not store medical information, diagnoses, or clinical records.

10. Third-party services

The site uses:

• Netlify for hosting and form processing
• Basic hosting logs for performance and troubleshooting

No advertising networks, analytics trackers, or marketing tools are used unless explicitly added in future updates.

11. Security measures

Reasonable steps are taken to protect data, including:

• Secure HTTPS hosting
• Minimal data collection
• Limited access to submissions
• Removal of identifiable details during moderation

While every effort is made to protect data, no small website can guarantee absolute security.

12. Content removal requests

You may request removal or editing of any content you submitted. Please include helpful details such as:

• Approximate submission date
• Story title or topic
• Any identifying text

Most requests are handled within 7 days.

13. Children’s privacy

This project is intended for adults. Submissions from individuals under 16 should not include identifying details and may not be published.

14. Changes to this policy

This policy may be updated as the project grows. Significant updates will be reflected with a revised date.