Your privacy
Cookie Policy
How we use cookies to support project access, and how you can manage them.
Last updated: 20 September 2026
This policy explains how ScholarClarity uses cookies and browser storage, why they are used, and how you can manage them.
1. How we use cookies
Cookies are small pieces of information stored by your browser. We use first-party cookies to support secure sign-in and staff administration. We do not use advertising cookies, behavioural tracking, social-media pixels, or analytics cookies. Browsing our public pages, using the quotation calculator, or submitting a document does not set a cookie.
When you successfully sign in to your project tracker, a cookie keeps you signed in to that project and supports protected downloads. Separate cookies support authorized staff access and administration preferences. Our public service does not use optional cookies or display an optional-cookie consent banner.
2. Cookies used by this website
| Cookie | Where and when | Provider and purpose | Duration | Strictly necessary? |
|---|---|---|---|---|
aew_project_session |
Customer tracker after successful sign-in Not set on ordinary public pages, the submission form, or the tracker login screen. Set only after successful project login, setup, or reset. |
This website — Academic Editing Workflow plugin Carries a random project-session credential so the server can authenticate one project, derive CSRF protection, enforce inactivity expiry, and authorize protected downloads. It does not contain the project password or public reference. |
Cookie expiry: 7 days. Server access expires after 30 minutes of inactivity and no later than 7 days; logout revokes it immediately. | Yes |
wordpress_test_cookie |
WordPress administrator login Set when the WordPress login page is opened; not set by normal public pages. |
WordPress core on this website Checks whether the administrator’s browser accepts cookies before login. |
Browser session | Yes — administrator security |
wordpress_d512e5259d0abc130be25e0f8c57f5d6 / wordpress_sec_d512e5259d0abc130be25e0f8c57f5d6 |
WordPress administration Set only after a successful WordPress user login. |
WordPress core on this website Authenticates authorized staff to protected WordPress administration and plugin workflow screens. HTTPS deployments use the secure-name variant. |
Without “Remember Me”: browser session, with server validity up to 2 days. With “Remember Me”: 14 days of authentication validity and up to 12 hours of WordPress login grace. | Yes — administrator authentication |
wordpress_logged_in_d512e5259d0abc130be25e0f8c57f5d6 |
Signed-in WordPress views Set only after a successful WordPress user login. |
WordPress core on this website Allows WordPress to recognize the signed-in staff member outside the administration path and apply their permissions. |
Same login duration as the WordPress authentication cookie above. | Yes — administrator authentication |
wp-settings-{user ID} / wp-settings-time-{user ID} |
WordPress administration Administrator-only; not set for project customers or anonymous visitors. |
WordPress core on this website Preserves the signed-in administrator’s WordPress interface settings and the time those settings were saved. |
1 year | Yes — authenticated staff interface functionality |
wp-resetpass-d512e5259d0abc130be25e0f8c57f5d6 |
WordPress administrator password reset Conditional: only during a WordPress user password reset. It is separate from customer project-password reset tokens. |
WordPress core on this website Temporarily carries the WordPress password-reset login and key while an authorized staff user completes a reset. |
Browser session; cleared when invalid or after the reset flow | Yes — account recovery security |
wordpress_rec_d512e5259d0abc130be25e0f8c57f5d6 |
WordPress recovery mode Conditional: not part of ordinary browsing or project tracking; set only when WordPress recovery mode is entered. |
WordPress core on this website Authenticates a time-limited WordPress recovery-mode session after use of a valid recovery link. |
1 week | Yes — exceptional site recovery security |
3. Local and session storage
Local storage and session storage are browser features that can retain information on your device. Our public pages, submission form, and project tracker do not use these features to store your documents or project information. Staff administration tools may use browser storage for editing safeguards such as local autosave.
4. Protecting your project session
The project-session cookie contains a random sign-in credential, not your project password or document contents. It allows the website to check that you are authorized to access your project. It is protected from access by page scripts and limits when it is sent with requests from other websites.
Your sign-in expires after inactivity or when you log out. Before signing in, check that your browser shows a secure HTTPS connection without a connection warning. Keep your password and access links private, and sign out when using a shared device.
5. Managing cookies and policy updates
Use your browser settings to view, delete, or block cookies for this website. Blocking the project-session cookie prevents you from staying signed in to the tracker and accessing protected downloads. Logging out revokes your project session and clears its cookie. Deleting cookies does not delete your project records or uploaded documents.
We update this policy when our use of cookies or browser storage changes. The date at the top of this page identifies the latest revision.
6. More information
Read our Privacy Policy for information about how we handle personal information. If you have a question about cookies or project access, please contact us.