Privacy Policy

This notice describes the data flows of the ShamsMag website. Updated 26 October 2026.

Reading the website

Cloudflare delivers and protects the site. Network requests can include your IP address, browser information and requested URL. Existing article images may be delivered from our hosting provider. These services process network data to deliver the requested resources and protect their infrastructure. The site also includes a Cloudflare browser beacon for performance and usage measurement; this is separate from Google Analytics.

Optional analytics

Google Analytics is loaded only after you choose Allow analytics. Essential only does not load the analytics script. Your choice is stored in your browser. Use Cookie preferences in the footer to change it. Analytics data is handled by Google under its own privacy terms.

Tools and browser storage

The word counter, prompt builder, campaign link builder, image compressor and calculators run in your browser. Their input fields are not submitted to our server by the tool code. Your color-theme choice and cookie preference are stored locally. Editor browser drafts are also stored locally on the editor device.

Community questions

Public question submission is currently being configured. When submission is enabled, a submitted question can include its title, text, topic, display name and submission time. Approved questions may be published with the display name you provide. Questions are reviewed before publication. Do not submit confidential information, medical records or information about someone else that you do not have permission to share. Cloudflare Turnstile processes security signals when enabled to reduce automated submissions.

Newsletter interest

The homepage offers registration of interest in future email updates and states that newsletter delivery is not active yet. The form asks for an email address and agreement to receive updates, and says the signup is stored on ShamsMag hosting. Use the contact page to request removal.

Editorial accounts

The site uses an account system for editorial sign-in. Authorised staff use authenticated sessions to access management functions. Saved content changes and moderation actions can include an editor identifier in the audit history. Do not share your sign-in credentials.

Contact and requests

Messages sent by email pass through the email services used to send and receive them. To ask about a submitted question, request a correction or raise a privacy concern, use the address on our contact page. Include enough information to identify the relevant submission, without sending unnecessary sensitive data.

External services

See Cloudflare privacy information and Google privacy information. Links to other websites lead to services with their own practices.