PDF Editor and Converter - Create PDF Online

Cookie Policy

Last updated: May 10, 2024

This Cookies Policy (“Cookies Policy”) applies to our Website, available following the link pdfdone.com (“Website”).

What is this policy, and what is it about?

This policy is an integral part of our general Privacy Notice. However, as a user, this policy will provide a more detailed description of the cookie technologies we use on our Website.

What is Cookie technology?

This technology ensures the exchange of small files between your browser and the server on which our site is located. The generation of such a file is carried out automatically by your browser at our request, and a script is hosted on our server, or such a file is generated on the side of our server and sent to your system.

Why do we use Cookies?

We use cookies and other technologies to ensure everyone using the Website has the best possible experience. For example, when you use the Website, we may place several cookies in your browser. We use these cookies:

to enable us to hold session information as you navigate from page to page within the Website,
to improve your experience,
to track and analyze usage and other statistical information.

If you elect not to activate cookies or disable cookies later, you may still visit the Website. Still, your ability to use some features or areas of those offerings may be limited.

How to Turn Off Cookies

You can generally activate or later deactivate cookies through a functionality built into your web browser. If you want to disable cookies, then you can find instructions for managing your browser settings at these links:

Internet Explorer	Firefox	Chrome	Opera
Microsoft Edge	Vivaldi	Safari	Brave

If you want to learn more about cookies or how to control, disable, or delete them, please visit for detailed guidance. In addition, specific third-party advertising networks, including Google, permit users to opt out of or customize preferences associated with their Internet browsing. To learn more about this feature from Google, click .

Types of Cookies

We use the following types of cookies:

Essential cookies.	These cookies are necessary for our Website to function properly. They enable core features like user authentication and session management. You cannot opt out of essential cookies.
Technical cookies	Technical cookies are essential for enabling seamless user navigation and facilitating the utilization of various options and services offered by websites. Their primary functions include identifying user sessions, granting access to restricted areas, streamlining the process of orders and purchases, simplifying form-filling and registration procedures, and enhancing security measures. Additionally, these cookies play a crucial role in enabling multimedia functionalities such as video playback and integration with social networking platforms, thereby enhancing the overall user experience.
Marketing cookies	Marketing cookies are used to track visitors across Websites. The intention is to display relevant and engaging ads for the individual user, making them more valuable for publishers and third-party advertisers.

How long do we keep cookies?

Each cookie has its unique storage period (lifetime). Some we store seasonally (while one session of visiting and using our site is active), some we keep for a shorter period, and some longer, depending on the functions they perform. We describe the lifetime of each cookie in detail below.

Category	Cookie's Name	Feature	Provider	Life period
Technical	AMP_4cacea564a	Amplitude SDK creates a cookie that begins with the prefix amp_ and ends with the first six digits of your project API key. The cookie is used to keep track of a few bits of metadata for the SDK: device Id: A randomly generated string user Id: Upon user log-in, if your instrumentation sends this value to Amplitude, it's stored in the cookie. Amplitude recommends you set this to uniquely identify users. Amplitude encodes this value as Base64 before storing it. optOut: A flag to opt this device out of amplitude tracking. If this flag is set, no additional information will be stored for the user. sessionId: A randomly generated string for each session lastEventTime: Time of the last event, used to determine when to expire and create a new session Id eventId: An incrementing sequence of identifiers used to distinguish events identifyId: An incrementing sequence of identifiers used to distinguish identify calls sequenceNumber: A sequence number used to order events and identify and properly sequence them When the Amplitude JavaScript SDK loads, it checks the cookie to see if it has an amplitude device_id in it (if a user is a returning user and the device_id was generated in a previous visit). If it finds one, it uses that value. If it doesn't find one (either because it's a new user or the user recently cleared cookies), the SDK randomly generates a device_id, and also saves it to the cookie.	Amplitude	Defaults to 1 year. Most browsers will limit the lifetime of cookies set using document.cookie from 1 to 7 days.
Marketing	_gcl_au	To store and track conversions.	Google	Persistent
Marketing	_gcl_aw	To provide ad delivery or retargeting.	Google	90 days
Marketing	___gads	To provide ad delivery or retargeting.	Google	13 months

Changes to this Policy

We may update this Cookie Policy occasionally to reflect changes in our practices or for legal reasons. We encourage you to review this policy periodically for any updates.