Website information
Privacy Policy
Applies to Everyday Balance, a men's everyday lifestyle publication. Last reviewed: 22 October 2026.
1. Introduction and scope
This Privacy Policy describes how Everyday Balance, an independent men's everyday lifestyle journal published at everydaybalance.info, handles information when visitors browse articles, select cookie preferences, or complete the general contact form. The publication is available to readers online. There are no member accounts, subscriptions, shopping baskets, payments or customer profiles. This policy addresses the technical handling needed to deliver pages, local preference settings and the limited information entered into the contact form. It also explains how to contact the website's published contact address for privacy questions. Any material addition of marketing tools, analytics or other data-handling features should be reflected in an updated notice before those tools are used.
2. Who handles your information
The publication operates under the name Everyday Balance. Privacy enquiries can be directed by email to [email protected], by phone to +44 117 496 0342, or by post to 26 Greenfield Road, Bristol, UK. The website hosting provider may process technical request information as part of providing the hosting service, according to its own contractual and retention arrangements. The contact page presents the publication's existing email and telephone contact options alongside a web form. The contact form checks the submitted details in PHP and then shows a confirmation page. It does not email or store the entered message. For a reply, please use the published email address or telephone number. Requests sent directly to the email address or by telephone are subject to the systems used for those separate channels.
3. Information you choose to provide
The contact page invites visitors to enter their name, email address, a written message and an acknowledgement of this policy. The fields are used in the web form's input checking and page-confirmation process. Please use the form for general enquiries about articles, corrections or website usability, and avoid sending passwords, bank details, identity documents, confidential files or sensitive personal histories. The form has a hidden field to help recognise automated submissions. A valid email address and a reasonably descriptive message are requested so that the page can distinguish complete submissions from accidental or malformed ones. The web form does not create an account or a subscriber profile. If you contact the publication through your own email provider, that provider applies its separate privacy arrangements.
4. Technical information and essential storage
Web servers can ordinarily receive technical request details such as an IP address, request time, requested filename, user agent and errors as part of sending a page to a visitor. Any hosting access-log configuration and log retention depend on the server operator. On the website itself, a browser local-storage value records the visitor's cookie preference and the time of that choice so the banner does not recur with every page load. The contact form does not require a PHP session or an account login. The implementation does not activate optional advertising cookies, profiling tags or audience analytics scripts. Google Fonts and the Tailwind styling service are third-party network resources whose servers may receive connection metadata when their files are loaded.
5. Purposes and lawful grounds
Information entered in the enquiry form is processed to check field length, email structure, the privacy acknowledgement and a basic anti-spam field, then to display the appropriate on-screen confirmation if valid. The form does not send a message to a mailbox or retain its contents. These functions are connected with the visitor's request to use the public form. The website also processes ordinary page requests to make the publication available and applies a saved browser preference to manage cookie-banner display. Where processing relies on legitimate interests or a visitor's request, those interests relate to basic site functionality rather than advertising. Selecting a cookie preference does not subscribe the visitor to a mailing list. Should additional uses of personal information be introduced, they would require an appropriate explanation and, where necessary, a separate affirmative choice.
6. External resources and recipients
Page styling uses a local stylesheet, while the site requests heading and body fonts from Google Fonts. When browsers retrieve these resources, the service providers may receive technical details such as an internet address, browser information and request metadata. Their use of such data is determined by their own notices and operational practices. The public form validates submissions and shows an on-screen confirmation, without sending an email or saving the message in a database. Email messages sent directly to the published mailbox are handled by the relevant email infrastructure, including the sender's chosen email provider. We do not integrate data-broker scripts, advertising tags or third-party contact-management services into this website's contact form. Any change to those connections should be reflected in this policy.
7. International transfers
Because the journal is available through the public internet and uses network-delivered fonts and styling resources, some technical requests may be handled by infrastructure outside the visitor’s region. The precise route and duration of network processing depend on hosting and network providers. If a future service introduces transfers of personal information for contact management or similar purposes, the responsible operator should establish the required data protection safeguards before enabling that service. The website does not assert that every third-party resource is served exclusively from a single data centre. Readers who prefer fewer third-party requests can use browser controls, although doing so may affect the appearance of fonts or page styling.
8. Retention and deletion
The contact form validates submitted fields and opens the thank-you page. It does not deliver an email or store the submitted message. The published email address is a separate correspondence route and any retention of emails through that route depends on the mailbox provider and operator practices. Web hosting providers may retain technical request and security logs for periods defined by their hosting settings and applicable obligations. Browser local storage keeps the visitor's selected cookie level until the visitor makes a new choice through Cookie Settings or clears site storage using browser controls. Requests concerning information held through external email correspondence can be addressed to the published contact email. This policy will be revised if a new contact-record management feature is introduced.
9. Security and access
The contact form uses both browser-side checks and PHP validation of required fields. Limits apply to message length and email format, and an unobtrusive hidden input is checked to discourage automated submissions. The website's Apache configuration includes headers covering content types, framing restrictions and referrer behaviour. Production hosting should use HTTPS, supported PHP software, regularly updated web-server packages and appropriately limited administrator access. Network services and browsers each have their own security responsibilities, so visitors should avoid adding credentials, payment information or confidential attachments to a general editorial enquiry. If the publication later introduces an email-delivery or data-management feature, access permissions and the relevant privacy disclosures should be reviewed at that time.
10. Your privacy rights
Visitors may have rights under applicable data protection law, including rights to request access, correction, erasure, restricted processing or an objection to certain processing. The exact scope depends on the type of information and the applicable lawful ground or exemption. Contact [email protected] for questions about data handled through published correspondence channels or website administration. We may ask for sufficient information to identify a relevant communication but should not request excessive proof of identity. Visitors can also clear their own cookie-preference record through browser controls or change it with the Cookie Settings button. The Information Commissioner's Office provides guidance and a route for complaints where concerns remain unresolved.
11. Children and sensitive details
This journal is written for adults and does not include a children's registration feature. Visitors should limit form submissions to ordinary editorial questions and avoid entering sensitive personal details about themselves or third parties. Public articles about activity, meals and personal time can be read without supplying a name or other contact information. The browser's cookie-preference choice is not used to construct a detailed personal profile. When sending an email directly to the published address, correspondents should consider whether they need to include the complete history or identifying details about a third person. The responsible website operator should always review new interactive features for data minimisation before adding them to the public site.
12. Changes and contact
This notice may be updated when technical features, provider arrangements, the publication's contact details or relevant requirements change. Updated wording will appear on this page, and material changes to personal-data uses should be brought to visitors' attention through an appropriate notice where legally required. For privacy enquiries use [email protected] or write to 26 Greenfield Road, Bristol, UK. Include the name of the page or feature involved so that a question can be understood without requesting unnecessary personal information. This policy is concerned with the public functionality described here and should not be treated as permission for future features that have not yet been introduced. Additional browser-storage details appear in the Cookie Policy.
Questions about this document?
To reach the team directly, use [email protected] or +44 117 496 0342.