Introduction
This Cookie Policy explains how Vp Technology Ltda ("Pipeback", "we", "us", or "our") uses cookies and similar technologies on our website at www.pipeback.com, in the Pipeback application at pipeback.com, and on the forms published with Pipeback. It complements our Privacy Policy.
If you run Pipeback on your own server, this policy does not describe your installation.
1. What are cookies
1.1.Cookies are small text files a website stores on your device. They let the site remember you between pages and visits.
1.2.Similar technologies, such as your browser's local storage and session storage, keep small pieces of information on your device in the same way. This policy covers them too.
2. Cookies on our website
2.1. Preferences
- locale (Pipeback, website, 1 year): remembers the language you chose
2.2. Analytics
- PostHog (website, cookie ph_<project key>_posthog, up to 1 year): measures how the website is used, and records sessions so we can fix problems. Form inputs are masked in recordings.
2.3. Attribution
- pipeback_utm (Pipeback, website, local storage): remembers the campaign that brought you, so your signup is attributed to it
3. Cookies in the application
3.1. Strictly necessary
These make the application work. Without them you cannot sign in or use Pipeback.
- pipeback-session (Pipeback, app): keeps you signed in during your session
- XSRF-TOKEN (Pipeback, app): protects your requests against cross-site request forgery
- remember_web_<id> (Pipeback, app): keeps you signed in when you choose "Remember me"
3.2. Preferences
- sidebar_state (Pipeback, app, 7 days): remembers whether you keep the sidebar open or closed
3.3. Support
- Crisp (app): keeps your support chat conversation across pages and visits. The chat loads only once you are signed in.
4. Cookies on published forms
4.1.Forms published with Pipeback use only what they need to work:
- pipeback-session and XSRF-TOKEN (Pipeback, form pages): keep the page working and protect it from forged requests. On a password-protected form, the session also remembers that the password was entered.
- pipeback:access:<form id> (Pipeback, form pages, session storage): proves the password of a protected form was entered when the browser keeps no session, for example in an embed. It is cleared when the tab closes.
- pipeback:guest (Pipeback, form pages, local storage): keeps a random respondent id for this browser and any answers saved to finish later
- Pipeback.show_once_<form id> and Pipeback.do_not_show_after_submit_<form id> (Pipeback, the site that embeds a popup form, local storage): remember not to show a popup form again, when its owner set it up that way
4.2.Form visit counting is cookieless. A visit is counted with a hash that changes every day, and no cookie or browser storage is used for it.
4.3.A form with a CAPTCHA block loads Google reCAPTCHA, which may set its own cookies.
4.4.The owner of a form may add analytics trackers, such as Google Analytics 4 or Meta Pixel, to their own form. Those tools are controlled by the form's owner and their providers, not by Pipeback, and may set their own cookies.
5. Third-party cookies
5.1.PostHog, Crisp and Google set their own cookies under their own privacy policies. The full list of the providers we work with is on our Subprocessors page.
6. How to control cookies
6.1.You can block or delete cookies at any time in your browser settings. Each browser explains how:
6.2.If you block strictly necessary cookies, you will not be able to sign in to the application, and some forms may not work.
7. Changes to this policy
7.1.We may update this Cookie Policy when we change the cookies we use. The date at the top of this page shows when it last changed.
8. Contact
For questions about this Cookie Policy, write to support@pipeback.com.