1. What cookies do here
Cookies are small values stored by your browser and sent with requests to the website that set them. Pinpilot by Codaratec uses first-party cookies to recognize a signed-in session and protect sensitive authentication flows. These cookies support features you choose to use, rather than advertising or audience profiling.
The current site does not install Google Analytics, AdSense, advertising pixels or Google sign-in. The public information pages can be read without logging in. Entering the demo or signing into a member workspace sets a session cookie.
2. Essential cookies
The following cookies are set by Pinpilot when the corresponding feature is used. Lifetimes below are the defaults in the application; a cookie can be cleared earlier by signing out, completing a flow or removing it in your browser. Restricted service session duration can be changed by the operator.
| Cookie | Default lifetime | Purpose |
|---|---|---|
pinpilot_session | 1 day | Recognizes your member or read-only demo session and allows the server to apply the appropriate workspace permissions. |
pinpilot_oauth | 10 minutes | Checks that the Pinterest authorization callback belongs to the connection flow initiated in your browser. It is cleared after a successful callback. |
pinpilot_admin | 8 hours | Recognizes a separately authenticated, restricted service-management session. It is not needed for ordinary public browsing or member registration. |
pinpilot_admin_nonce | 5 minutes | Supports a one-time challenge for restricted sign-in and helps protect that authentication flow from automated abuse. |
These cookies are marked HttpOnly, so page scripts cannot read them. Session and authorization cookies also use SameSite protections and are marked Secure on HTTPS deployments. The member and demo session cookie is scoped to the application, while the authorization and restricted-security cookies are scoped to their relevant service endpoints.
Server-side session expiry or revocation can require a new sign-in even before a browser removes a cookie. Cookies are not a substitute for server-side permission checks: the demo remains read-only.
3. Third-party services and external content
When you choose to connect Pinterest or open a Stripe checkout or billing portal, those services may use their own cookies under their own policies. Pinpilot’s cookie list does not describe cookies on other companies’ websites.
Some illustrative images and avatars in the interface, including the demo and member workspace, are loaded from external image hosts such as Unsplash. A request to an image host may disclose your IP address and request metadata, including browser-controlled referrer information. Whether an external host sets or receives its own cookies depends on that host and your browser settings. See our Privacy Policy for more about these requests and optional integrations.
4. Your browser choices
You can inspect, block or delete cookies using your browser’s privacy settings. You can usually restrict third-party cookies separately from cookies belonging to the site you visit.
Blocking Pinpilot’s essential cookies prevents sessions from working properly: you may be unable to remain signed in, enter the demo or complete a Pinterest connection. Deleting a cookie signs your browser out of the associated session but does not itself delete your account, content, billing records or Pins already published.
To stop a session, use the available sign-out control. To disconnect Pinterest, use the workspace’s connection controls and, if desired, revoke permission in Pinterest’s settings. For account deletion or other information requests, contact us through the process described in the Privacy Policy.
5. Updates and questions
We will update this page if the cookies or related integrations change. New optional tracking features, if introduced, will require an updated explanation and any choices required by applicable law.
For questions about browser storage or privacy, contact Codaratec.