Effective date: 22 November 2026 Contact: pr@kashaneh.org
This notice explains how Kashaneh handles information when a person visits the website, applies for membership, submits work, participates in an event, uses a public profile, contacts the Association, or subscribes to the newsletter. The operator is Kashaneh. Contact pr@kashaneh.org for information-handling enquiries. Applicable mandatory privacy rights continue to apply.
Information collected
Depending on the feature used, Kashaneh may collect account name, email address, password authentication data, language preference, membership application details and short biography, pen name, author biography, profile photograph and profile details, submission text and files, sponsor and affiliation disclosures, AI-use category, editorial decisions, comments, appeals, pickup assignments, queue counts and report exports, workflow messages, license acceptance and waiver records, event registration and attendance, newsletter subscription and unsubscribe records, and information sent through the contact form. The website and security services may also process technical information such as IP address, browser, device, and security events.
Do not submit sensitive personal information unless the form explicitly requests it and the information is necessary.
Why it is used
Kashaneh uses information to create and secure accounts; assess membership; receive and review work; communicate decisions and requested revisions; publish accepted work under the selected pen name; administer the license and waiver process; operate member profiles; register people for events; send essential notices and requested reminders; send optional newsletters with consent; answer contact requests; prevent abuse; maintain records; and meet applicable legal obligations.
Essential security and workflow notices remain enabled. Members may change language and optional communication preferences. Newsletter subscriptions are optional and can be ended with an unsubscribe link without logging in.
Who can see information
Access depends on role and workflow. Members can see their own applications, submissions, status, editorial decision comments, and their responses. Submissions are identified: authorized editors can see the author name and account identifier together with the work and relevant AI-use, rights, sponsor and affiliation disclosures. Ordinarily one editor decides the first review and a different editor decides the second, and ordinary editors cannot review their own work. Administrators may grant supported roles including administrator access, take over an assignment explicitly, and decide both stages, including their own submission; these exceptions and role changes are audited. There is no anonymous-review consent or final author proof. A revision or response stays on the same submission and returns to the editor responsible for that stage within the same editorial group. Authorized editors, the chief editor, and administrators can read the associated workflow messages. Administrators have all system roles; their actions are audited.
Published pages and public author profiles are visible to anyone. A publication displays the selected author name and an author section at the end with the approved biography, profile photograph, and a link to the public profile. Provide only biography and portrait information you are authorized to make public. Account email, private contact information, internal account IDs, sponsor disclosures, and private editorial discussion are not public. Administrators and editors can create an attributed author profile and publish directly with documented rights authority; this does not authorize impersonation or replace necessary consent. A published work may remain on the site after an approved waiver of exclusivity.
Where information is processed
Editorial AI and promotional posts
Authorized editors and administrators may request website-formatting checks and AI-assisted promotional summaries. Formatting preserves the author's wording and original uploaded files. Only the work title and text needed for summarization are sent to a vetted Amazon Bedrock model in Australia. Private account details, sponsor disclosures, editorial comments and channel credentials are excluded from the AI request. Processing stops if Australian routing or the model's approved privacy configuration cannot be verified. Manuscripts are not written to model-invocation logs by this feature.
Generated summaries and branded covers are drafts requiring editor or administrator approval. Public social posts use the approved author attribution, publication link and media, and only the selected destinations. Instagram, Telegram, Facebook Pages and configured webhook receivers process published content under their own terms and locations. Website publication may proceed while social posts await approval. Retries do not automatically repeat uncertain deliveries. AI-job drafts expire after seven days; approved social packages follow the submission record's retention, and action history follows the audit retention policy. Promotional AI assistance does not change the author's declaration about AI use in the original work.
The optional submission location starts from the author's private saved city/country, without device or IP geolocation. The author can edit it and choose public display separately for each work; display is off by default. Authorized editors and administrators may correct the text while preserving the author's display choice. Authors can change that choice after publication; hiding it removes it from the website and future public API/channel payloads. Copies already delivered externally are not automatically recalled. The profile's default location remains private.
Private account, membership, submission, review, and operational data is planned to be stored in AWS in Australia (Sydney). The planned production integration uses Microsoft 365 to deliver no-reply email from submissions@kashaneh.org, members@kashaneh.org, events@kashaneh.org, and newsletter@kashaneh.org; the Microsoft 365 tenant may process or store messages in its configured geography. Contact-form messages are stored in the private Australian workflow inbox for authorized editors and administrators. Sending email directly to pr@kashaneh.org is a separate option.
Only content approved for public release may be sent through GitHub Actions to build the static website. The public publication service must exclude future scheduled content until its release date. It is public after publication and may be processed outside Australia. Public content is delivered globally through the website's content distribution service. Private drafts, submissions, member records, and reviews are not sent to GitHub.
An external audio or video player may contact its media provider when loaded or played; that provider may process an IP address, device information, cookies, or viewing activity under its own policies. Use direct-hosted media where appropriate and do not embed arbitrary scripts. External links and media hosts are governed by their own privacy practices. This notice will be updated before introducing materially different providers or processing.
Authorized account owners and editorial staff may preview attached images, audio, video, and supported documents within the private submission record. Uploaded PDF, TXT, and DOCX are available only after the exact immutable version passes managed malware scanning; document previews use restricted PDF display or safely extracted text rather than executing active document content. Access is checked against the submission, and short-lived links do not make unpublished material public. Supported external links or players can contact the external provider during private review as well as after publication; unsupported pages may be offered as an ordinary link instead of embedded.
Editorial workload and administration
Editors can see submission status, pickup responsibility, active queue sizes, completed-work counts, and workload graphs. Authorized staff may export reports to manage the association. Exports remain confidential and must be stored securely, shared only with authorized staff, and deleted when no longer needed. Public event information may include an online link, date and time, topic, and named featured participants; obtain permission before publishing a participant biography or photograph. Public programs may include their purpose, details, and approved links. Removing a public event or program is separate from the retention of required registration or audit records.
Retention
- Declined submission records: one year after the final decision, including after account deactivation.
- Event registration and attendance records: one year after the event.
- General security and workflow audit events: one year.
- License acceptance and waiver records: while the related work remains published; retain longer if counsel or a legal obligation requires it.
- Account deletion: after an administrator approves deletion, remove profile and contact details, subject to the retention of submission records and license evidence above.
- Inactive account rule: members with no published submission who do not log in for six months are notified and given one month to log in. If there is no login, the account is disabled and flagged for administrator review for deletion.
- Newsletter details: keep while subscribed. After unsubscribe, retain the minimum suppression record needed to honor the request and prevent accidental resubscription; suppression information is kept only as needed to respect the unsubscribe request.
- Contact-form messages: up to one year unless permanently deleted earlier by an authorized editor or administrator. Direct conversations may also be permanently deleted for all participants by an authorized participant; submission and application history is retained separately. Minimal audit and deletion markers retain no message text and may remain for one year. Email sent separately to the published address follows Microsoft 365 mailbox retention.
Backups are planned to be retained for three months. The implementation must reconcile deletion requests with backup expiry and any applicable recordkeeping requirement.
Access, correction, deletion, and complaints
A member can update profile information in the account and may contact Kashaneh to request access, correction, or deletion of personal information. Deletion is subject to the retention rules and the publication licence. Contact pr@kashaneh.org. Kashaneh will acknowledge privacy complaints and explain how they will be reviewed. An unresolved concern may be escalated to an uninvolved administrator and, where applicable, the competent privacy regulator.
Security
Kashaneh uses role-based access, multi-factor authentication for privileged roles, encrypted connections, private storage for unpublished files, automatic malware scanning, audit records, backups, and access reviews. No online service can be guaranteed completely secure. Please do not reuse passwords and report suspected account compromise promptly to pr@kashaneh.org.
Changes
Kashaneh will publish a new version and effective date when this notice changes materially. The notice should be reviewed at least annually and whenever a new data use or provider is introduced.
Applicable privacy rights
Kashaneh uses the Australian Privacy Principles as a privacy baseline. Statutory coverage depends on the circumstances; this notice does not remove rights under any applicable privacy law. Where the Australian Privacy Act applies, unresolved complaints may be referred to the Office of the Australian Information Commissioner.
Contact form
Contact-form messages, sender names and reply email addresses are stored privately in AWS Australia for up to one year, visible as External messages to authorized editors, the chief editor and administrators. The form does not automatically forward email; the published email address remains a separate option. Short-lived hashed request-source and browser identifiers support abuse limits and expire within two days.
Optional public email and aggregate performance statistics
An author may choose to display the verified sign-in email address on their public author page. This is off by default. Consent is bound to the current verified address; changing the address requires a fresh opt-in. Hiding the address, disabling the account, or deleting the account removes it from subsequent public profile responses. Copies already obtained by other people cannot be recalled. This setting does not add the email to publication snapshots or social posts.
An administrator may enable optional aggregate Performance analytics. It is off by default. When disabled, no new analytics counters are written and the reports are unavailable; saved totals remain subject to retention. A cached public feature-setting lookup may occur without collecting a page view. When enabled, the site counts approved public pages/publications, approximate per-tab browsing sessions, normalized API routes and status groups, and aggregate sign-in/submission/review activity. Counters do not store query strings, private record identifiers, message bodies, authentication tokens, IP addresses or stable visitor identifiers. Browsers use a local last-view timestamp to estimate a new visit after 30 minutes of inactivity. Blocked scripts and automated traffic affect these estimates; they are not counts of unique people.
Daily aggregates are stored in AWS Australia for up to one year. There is no external advertising analytics service, scheduled reporting worker or automatic dashboard polling. Admin-only reports are generated on request and may be exported as JSON or CSV. User-status figures are current account snapshots.
