Only the storage needed for a useful study experience.
This notice explains how Prepward uses necessary web cookies, browser storage, and third-party flows such as Google sign-in and Stripe Checkout.
At the time of this notice, Prepward does not intentionally use advertising cookies. Necessary session storage and third-party provider technologies can still be used when you sign in, pay, or choose an integrated service.
1. Essential session cookies
The web learner experience uses an essential session cookie to keep a signed-in account connected to authenticated requests. In production, the session cookie is configured for secure transport, is not readable by normal page scripts, uses a same-site policy, and is scoped to the site.
This storage is necessary for sign-in, account protection, CSRF protections, access checks, and actions such as loading your plan or saving an answer. If you block or delete essential cookies, the learner app may not be able to keep you signed in or complete authenticated actions.
2. Browser and app storage
The web application may use browser-managed storage for temporary interface state and the mobile application may use platform-secure storage for session and offline study data. This can include queued answers, offline packages, device registration, or preferences needed to provide a requested feature.
Clearing browser or app storage can sign you out, remove local queued work, or require an offline package to be downloaded again. Where possible, synchronise while online before clearing storage. Account data held on the server is described in the Privacy Policy.
3. Third-party providers
Google sign-in
Where enabled, the learner app loads Google Identity Services only for the sign-in option. Google may use its own cookies or similar technologies under Google's terms and privacy information. You can use the email one-time-code flow instead when it is available.
Stripe Checkout
When web checkout is enabled, the app opens Stripe Checkout. Stripe may use cookies, local storage, or other technologies needed for fraud prevention, payment security, checkout operation, and preference handling under Stripe's policies. Prepward does not receive or store your full payment-card number through the learner app.
App stores
Apple and Google may process device, account, and transaction information when you use their mobile purchase flows. Their own policies govern those provider-controlled technologies.
4. Your choices
- Use your browser settings to view, block, or delete cookies, understanding that essential sign-in features may stop working.
- Choose email sign-in instead of Google sign-in when that option is available.
- Leave a Stripe Checkout page or use your payment provider's controls if you do not want to complete a web purchase.
- Turn off optional reminders or device permissions in the app or device settings when those features are not wanted.
- Contact the privacy team if you need information about personal data associated with a cookie or device identifier.
Deleting cookies does not delete your learner account. To request account deletion, follow the steps on Account deletion.
5. Changes and contact
We may update this notice when the web application, mobile application, authentication flow, payment provider, or legal requirements change. The date at the top of the page shows the current version.
For questions about cookies, browser storage, or privacy, contact privacy@barozelabs.com. For a technical sign-in or device problem, contact support@barozelabs.com.