1. Scope
This Cookie Policy applies exclusively to ApisKit and to the site:
kit.apisdom.com
Its purpose is to explain the use of cookies and other mechanisms for storing or retrieving information used on the user's device.
Cookie law is not technically limited to files called "cookies": it also covers other mechanisms for storing or retrieving information on the user’s device when they perform an equivalent function.
2. Controller
The owner of the site is the entity identified in the Legal Notice.
The full identification details are centralized at:
https://apisdom.com/legal#aviso
They are not reproduced again in this policy.
The AEPD itself establishes that it is not necessary to repeat the full company name in the cookie information when the complete identification details are available in other sections, such as the Legal Notice or the Privacy Policy, and the identity of the controller is evident.
3. What cookies and similar technologies are
Cookies are small pieces of information that may be stored on the device used to access a website.
Technically different mechanisms may also be used, such as local or session storage, when they are necessary to provide certain features.
For the purposes of this policy, references to "cookies" include these mechanisms when they perform equivalent functions of storing or retrieving information.
4. What ApisKit uses
ApisKit uses only cookies or technical technologies necessary for the operation of the site and of the features expressly requested by the user.
They may be used for functions such as:
- maintaining and protecting a started session;
- authenticating the user;
- allowing access to account areas;
- maintaining technical security controls;
- preventing fraudulent or abusive uses;
- keeping certain preferences expressly selected by the user when necessary to provide the requested feature;
- maintaining the technical operation of the application.
The AEPD considers exempt, among others, technologies intended exclusively for authentication or session identification, user security, user input and certain expressly requested preferences.
5. What ApisKit does not use
ApisKit does not use cookies for the purposes of:
- advertising;
- behavioral advertising;
- cross-site commercial tracking;
- building advertising profiles;
- unnecessary cookie-based measurement or analytics;
- commercial personalization based on browsing behavior.
Therefore, no unnecessary cookies whose operation depends on the user’s consent are used.
6. Consent
The cookies and technologies used by ApisKit are limited to those necessary to provide the functions expressly requested by the user or to technically enable the communication and operation of the service.
For that reason, they do not require prior consent under the exception provided in Article 22.2 of the LSSI.
Mere browsing is not interpreted as consent to install unnecessary cookies.
7. Duration
The necessary cookies and technical mechanisms will be kept only for the time appropriate to fulfill the function that justifies their use.
When a purpose can be fulfilled through a session technology, it will disappear at the end of the corresponding session.
When it is necessary to temporarily keep a preference or technical information, its duration will be limited to what is necessary for that purpose.
The AEPD establishes that even exempt cookies must have an expiration related to the purpose that justifies their use.
8. Cookies and third-party services
Certain technical features may depend on technology providers used to provide the service.
When a provider intervenes exclusively to provide a technically necessary function requested by the user, its use must be limited to that purpose.
This policy does not authorize any third party to use the information obtained from ApisKit for advertising, behavioral tracking or other unnecessary purposes of their own.
The AEPD expressly distinguishes this case: a third-party technology may remain within the exception when it is used exclusively to provide the requested service; if the third party uses it for other purposes, the information and consent obligations come into play.
9. Management from the browser
The user can view, block or delete cookies from their browser settings.
However, blocking strictly necessary technologies may cause certain ApisKit functions to stop working correctly, for example:
- maintaining a session;
- accessing an account;
- remembering a necessary preference;
- applying certain security mechanisms.
ApisKit does not condition access on the acceptance of advertising, analytics or tracking cookies because it does not use those categories.
10. Personal data
When a necessary cookie or technology involves the processing of personal data, that processing is subject to the ApisKit Privacy Policy.
This page does not reproduce again the purposes, legal bases, retention, recipients or rights regarding data protection already governed there.
11. External checkout
This Cookie Policy applies only to kit.apisdom.com.
If the user accesses Polar's external checkout:
they will be accessing an external domain and service. The cookies and technologies used there are governed by the policies and mechanisms established by Polar.
Their conditions are not reproduced here because they are not cookies installed by kit.apisdom.com.
12. Future introduction of non-necessary cookies
If in the future ApisKit were to introduce cookies or technologies for non-necessary analytics, advertising, tracking, profiling or another non-exempt purpose:
- this Cookie Policy must be updated;
- those technologies must not be activated before obtaining the required consent;
- the user must have a real option to accept or reject;
- rejection must be presented in a way comparable to acceptance;
- the different purposes must be configurable where appropriate;
- consent must be able to be withdrawn as easily as it was granted.
The AEPD requires prior information for non-exempt cookies, that accepting and rejecting be equivalent options and that withdrawing consent be as simple as granting it.
13. Changes to this policy
This Policy may be updated when the technologies used or the applicable legal obligations change.
If a purpose that requires consent is introduced, the modification of this policy will not by itself replace obtaining that consent.
The current version will be the one published on this page, together with the date of its last update.
