Cookies & Browser Storage

The API uses HttpOnly cookies for session renewal and short-lived Google sign-in verification or exchange steps. HttpOnly means application JavaScript cannot read these cookies. They are used to authenticate requests and complete sign-in, not for advertising. Blocking these cookies can prevent sign-in or session renewal.

The browser stores your access token and basic account details to maintain the signed-in experience. Local storage also holds theme preferences, selected roles or conferences, cached venue information, and in-progress submission metadata. Locally saved form data is a convenience and is not proof that a manuscript has been submitted or saved to the server.

Session storage holds temporary page state, such as deployment-reload recovery and dismissal markers. Unlike local storage, it is ordinarily cleared when its browser tab or session ends.

Choosing Google sign-in opens Google’s authentication service, which uses its own cookies and privacy controls. Public pages also load fonts from Google Fonts. Third-party websites reached through external links have their own storage practices. PaperNest’s current public interface does not implement advertising pixels or optional analytics-cookie controls.

You can clear or block cookies and site storage through your browser settings. Sign out before using a shared device, and clear site data when you finish if needed. Clearing local storage can remove unsaved manuscript form progress and preferences; save required work to your account first. Deleting browser storage does not delete server-side account or scholarly records.

For questions about cookies or browser-stored information, email media.brainfoundation@gmail.com.