Kashaneh policies

Security and Privacy Overview

Final version 1.0 | Effective 22 November 2026

Kashaneh handles membership information and unpublished creative work with care. The member and editorial workflow is designed to keep private records separate from the public website, restrict information to people who need it, and retain it only for defined periods.

How access works

Members can access their own accounts, submissions, and registrations. The editorial process is identified: authorized editors see the author's name and internal account identifier. Ordinary editors cannot review their own work: one decides the first review and a different editor decides the second. Administrators may explicitly take over assignments and decide both stages, including their own submissions, and may grant supported account roles including administrator access; these actions are audited. Resubmissions and responses return to the editor responsible for the rejected stage. Authorized editors see operational queue and workload reports, which remain private. No initial triage, anonymous-review consent, or final author proof is required. Administrative and direct-publication actions are recorded. Privileged roles require multi-factor authentication.

How data is protected

Private workflow data and files are planned to be stored in AWS Australia. Unpublished files are kept private and scanned for malware before inline review or download. Access is limited to the owner and staff authorized for that submission. PDF uses a restricted viewer; TXT and DOCX previews display safely decoded or extracted text without running scripts or macros. Supported image, audio and video controls stay in the private record. Unscanned or blocked files are not served, and unsupported external pages use a link rather than an unsafe embed. Public pages are served separately as static website files. The planned production email integration uses Microsoft 365 for account and workflow messages; its data may be stored in the tenant's configured geography. Only content approved for public release is used in the public-site build or publication service. Future scheduled works must remain private. The public author name, biography, and portrait are separate from private account and editorial data. External media players contact their own providers and are subject to those providers' privacy practices.

Kashaneh uses secure connections, role-based access, backups, and account-session expiry. No internet service can be guaranteed completely secure. Members should use unique passwords, keep their account details safe, and contact Kashaneh promptly if they suspect account misuse.

Report a security or privacy concern

Contact pr@kashaneh.org and include the page or account involved and a safe way to reach you. Do not include passwords or session codes. Kashaneh will assess reports and respond through its incident and privacy procedures.

This overview does not disclose detailed infrastructure or incident-response procedures. See the Privacy Notice for information handling and retention. Report security concerns to pr@kashaneh.org.

Contact-form messages appear privately as External messages to authorized editors and administrators. Requests are bounded and rate limited. Direct and External conversations can be permanently deleted for everyone with an authorized action and clear confirmation; submission and application history is retained separately. Website manuscript references remain inactive plain text; dedicated media links remain supported. Original downloaded files remain unchanged. Input validation, bound database values, safe text rendering and isolated model source data work together; detecting words alone cannot guarantee protection against prompt injection.