Article Management System Rule Book & policies
The standards we publish to, and the practical guides for meeting them. The two reference documents below are the authoritative versions — read them here or download the PDF.
Privacy Policy - Authors
Last updated 19 Aug 2026
This Privacy Policy explains how Technology Fist handles personal data for authors using Article Management System.
As an author, the personal data we collect includes your name, email, affiliation, and the content of your submissions (title, abstract, files, and author list). Payment-related information (if you pay an APC) is limited to what's needed to confirm your payment - see the Refund Policy for how payments themselves are handled.
- We use your data only to operate the platform: managing your account, processing submissions/reviews/decisions, sending relevant notifications, and (where applicable) processing payments.
- We do not sell personal data to third parties. Data may be shared with the specific conference/journal you're interacting with, since that's the nature of the service.
- If a venue uses the separate Publishing platform, an accepted paper's author names, affiliations, title, and abstract are deposited with Crossref (a nonprofit scholarly infrastructure organisation) as part of DOI registration - this becomes permanent, publicly visible metadata, distinct from your regular account data, and is not something we can later delete on your behalf once registered.
- Data is retained for as long as your account or the relevant conference/journal remains active, plus a reasonable period for legal and record-keeping purposes.
- You may request a copy of, correction to, or deletion of your personal data (subject to what a venue needs to retain for its own academic/legal record-keeping, and subject to the Crossref-deposited metadata above) by contacting the conference/journal directly or Technology Fist.
- If you apply for access to our live demonstration environment, we record the details you provide (name, institutional email, organisation, stated purpose) together with the decision on your request and, if approved, whether the access link was used; this record is kept so access decisions are accountable.
- Where one person holds two accounts, a platform administrator may merge them on request or on clear evidence they belong to the same person: the duplicate's papers, roles and review records move to the retained account, the duplicate is deactivated (not deleted), and the merge is recorded in the audit log.
- We use standard technical safeguards (access controls, encrypted connections) to protect your data, though no online system can be guaranteed 100% secure.
Optional modules
Where a venue uses the review passport, you may choose to carry the peer review of a decided paper to another venue on this platform. Nothing is shared unless you create a passport, and each reviewer separately decides whether their report travels and whether their name travels with it. You may revoke a passport at any time. Reviewers' confidential comments to the chair are never included.
Where a conference uses the event layer, we hold the registration details you provide (name, email, affiliation, country) and, if you attend, a check-in record. A certificate issued to you carries a verification code; anyone holding that code can see your name, the venue, the type of certificate and its date on a public verification page. That is the point of the code - it lets a third party confirm the certificate is genuine - and no other personal data is exposed by it.