CMS Privacy Policy
Go to CMS ProductLast updated on:September 2, 2026
1. Scope
This policy covers the MedicalToxic CMS: the authoring and editorial system in which contributors write blogs, case studies and news, and in which editors review and publish them. It does not cover the public MedicalToxic website where the published output appears, nor ToxLumen or the Medical Toxicology Community. Each has its own privacy policy. This document replaces the "Medical Toxicology" policy dated 1 May 2025, which described this product before the website had a policy of its own.
2. Who This Applies To
The CMS is a closed, internal system for authors, editors, SEO managers, administrators and superusers working on behalf of Medical Toxicology LLC. It is not open to the public and it is not a consumer service. If you are a contributor, this policy tells you what the system records about your work.
3. What We Collect
Account and role data: your name, email address, assigned role, and engagement history. Authentication is handled by the central MedicalToxic account service. Content you create: drafts, published articles, case studies, news items, images, alt text, citations and SEO metadata. This includes: • autosave copies, written a couple of seconds after you stop typing; • offline backups, held in your browser when the connection drops and retried until the save lands; • version snapshots at every editorial milestone — submitted, accepted, sent back for revision, restored — each restorable with one click. Editorial workflow data: who submitted what and when, who reviewed it, what notes were returned, and what was published. Activity data: an activity log covering eighteen categories of event, recorded per member, plus login history, browser type and IP address kept for security. Support tickets: the content of tickets you raise, visible to you and to support staff.
4. The Activity Log
The CMS records member activity across eighteen categories, and version snapshots mean earlier drafts of your work persist after you have replaced them. We state this plainly because it is monitoring, and you should know it is there. It exists for editorial accountability. In a medically reviewed publication it must be possible to establish who wrote a claim, who approved it, and what changed in between. We use it to attribute authorship and approval, restore lost or damaged work, investigate security incidents, and meet our editorial obligations. We do not use it to make automated decisions about individuals, and it is not intended as a productivity-surveillance tool. Access is scoped by role: what an author can see of their own activity is not what an administrator can see.
5. How We Use This Information
• To operate the CMS and its editorial workflow. • To protect work in progress through autosave, offline backup and version history. • To maintain editorial accountability and an audit trail. • To control access and keep the system secure. • To respond to your support tickets. We do not sell personal information, and we do not use CMS data for advertising.
6. Artificial Intelligence in the CMS
The CMS assembles a daily toxicology news digest from PubMed and news sources, and a weekly newsletter, with the help of AI. Two commitments govern that: • Generated, then reviewed. AI-assembled material enters the same approval queue as everything else. Nothing reaches the public site without a human editor accepting it. • AI drafts are not attributed to a person who did not write them. An editor who reviews and approves a digest is accountable for approving it, which is not the same as authoring it. Where AI features process the text of a draft, that text is sent to our model provider solely to return output to us, and is not used to train their models.
8. Security
Data is held in encrypted databases on infrastructure operated to industry-standard security controls. Access is role-based and limited to those who need it, and authentication runs through the central MedicalToxic account service. No system is perfectly secure. If a breach affects your information we will notify you without undue delay.
9. How Long We Keep It
• Published content and its version history: retained indefinitely. A medically reviewed publication needs a durable record of what was said and who approved it. • Drafts and autosaves: retained with the item; superseded autosaves are pruned. • Offline backups: held in your browser only until the save succeeds. • Activity and login logs: retained for twelve months. • Account data: retained while you hold an account, and deleted within ninety days of your engagement ending. • Support tickets: retained for as long as needed to handle and record the matter. If you leave, your authorship attribution on published work remains, because it is part of the editorial record.
10. Your Rights
Depending on where you live, you may have the right to access the personal information we hold about you, to have it corrected or deleted, to receive a copy of it, and to object to processing. Deletion is limited where content forms part of the published editorial record. We can generally remove personal data that is not part of that record, and we will discuss bylines case by case. To make a request, use the contact form at medicaltoxic.com/contact-us.
11. Changes and Contact
We may update this policy. Material changes will be published here with a new "last updated" date. Medical Toxicology LLC 6421 N Tierra de las Catalinas, Tucson, AZ 85718, United States Questions about this policy: medicaltoxic.com/contact-us