Cookie Policy
BROCHUREFORGE — COOKIES
According to the operator, BrochureForge's primary application server runs on an Oracle Cloud Infrastructure virtual cloud server in Frankfurt, Germany.
Operator: INOVIALAB TEKNOLOJI ANONIM SIRKETI
Address: 19 Mayıs Mah. Mehmet Akif Ersoy 1. Sok. No:2/3 Büyükçekmece, İstanbul
Registration: 4781195538
Support: info@brochureforge.com
BrochureForge serves individual and business customers. Paid subscriptions, when available for purchase, renew monthly under the terms disclosed at checkout. Hosting details are subject to the correction notice below.
1. SCOPE
Create a verified inventory of cookies, local storage, tracking tags and similar technologies.
2. ESSENTIAL TECHNOLOGIES
Classify real session, authentication and CSRF mechanisms according to their actual purpose.
3. OPTIONAL TECHNOLOGIES
Analytics, advertising and personalization require separate classifications and applicable permission conditions.
4. INVENTORY
Record provider, purpose, lifespan, first- or third-party status and category for each technology.
5. CHOICES
Acceptance, refusal and withdrawal of optional preferences must be clear and independently available.
6. RECORDS
Maintain evidence appropriate to preference purpose, notice version and timestamp.
7. CHANGES
Update the inventory and disclosures when technologies or providers change.
10. COOKIE INVENTORY
Each cookie or comparable technology requires an accurate provider, purpose, duration and classification based on browser testing. Unverified advertising or analytics technology must not be represented as active.
11. CHOICES
Where consent is legally required for non-essential technologies, refusal and preference updates must correspond to actual controls.
Cookie preferences. Strictly necessary cookies may be used for essential service functionality, session security and account access. Analytics, performance, advertising and marketing cookies requiring consent must remain inactive unless valid consent is obtained. Users must be able to accept, reject and subsequently revise applicable preferences. The cookie inventory must describe only technologies actually in use, including their providers, purposes and retention periods.
On 4 October 2026, anonymous HTTPS responses showed PHPSESSID and bf_lang cookies. PHPSESSID had Secure, HttpOnly, SameSite=Lax and Path=/, with no explicit expiry attribute observed. The language-preference-related bf_lang had Secure, SameSite=Lax, Path=/ and an expiry attribute, without HttpOnly. After the fix on 4 October 2026, HTTPS tests of the Turkish and English Legal Center pages confirmed one bf_lang Set-Cookie header per response. This limited observation is neither a complete cookie inventory nor confirmation of precise retention periods.