Cookie Policy
Pleated Blind aims to manage the website experience securely and in a measured manner. Some cookies enable basic functions to work. Others are only activated according to the visitor's preference. Each technology is evaluated with its purpose and usage period. Non-mandatory cookies must not be run without the necessary preference mechanism being operated. This policy explains the cookie usage principles.
1. Purpose of the Cookie Policy
This Cookie Policy regulates the technologies used on the Pleated Blind website. The text covers visitors, members and users. The policy focuses only on cookie practices. Different activity areas are evaluated separately.
The website may store some information on the browser. Similar technologies may also be used for the same purposes. The usage method varies according to the technical nature of the relevant tool. Each technology does not produce the same legal result.
The table below explains the basic concepts used in this policy. Concepts must be used with the same meaning on preference screens.
| Concept | Description | Application Equivalent |
|---|---|---|
| Cookie | Small data file that can be saved to the browser | Session, preference or analysis record |
| Session Cookie | Temporary record that can be deleted when the browser is closed | Cart or session management |
| Persistent Cookie | Record that can remain on the device for a determined period | Preference or measurement functions |
| First-Party Cookie | Cookie placed via the Pleated Blind domain | Execution of site functions |
| Third-Party Cookie | Cookie placed by external service provider | Analytics, advertising or embedded content |
| Preference Panel | Tool where the user manages their cookie selections | Accept, reject and category settings |
Definitions must be kept consistent with the real technical structure on the live site. The policy must be updated when new tools are added.
2. Data Controller's Contact Information
The data controller managing cookie practices must be clearly stated. The brand name does not replace the official trade title. Contact information must be published in an accessible manner. Technical requests may be submitted via appropriate channels.
The table below shows the basic information belonging to the data controller. Fields in brackets must be filled before publication.
| Information Type | Description |
|---|---|
| Brand | Pleated Blind |
| Data Controller | [OFFICIAL TRADE TITLE TO BE ADDED] |
| Tax Office | [TAX OFFICE TO BE ADDED] |
| Tax Number | [TAX NUMBER TO BE ADDED] |
| MERSİS Number | [MERSİS NUMBER TO BE ADDED IF ANY] |
| KEP Address | [KEP ADDRESS TO BE ADDED IF ANY] |
| Phone | +90 540 336 3873 |
| +90 540 336 3873 | |
| info@pliseperde.com | |
| Address | Esenyalı Mah. Edebali Cad. No:13/C, 34903 Pendik/Istanbul |
When information changes, the current version must be published. Old texts may be archived when necessary.
3. Purposes of Cookie Use
Cookies may be used for different technical purposes. Each cookie's purpose must be determined in advance. Unnecessary records must not be created. Usage period must be kept proportional to the purpose.
Some tools support site security. Some may remember user preferences. Some technologies may provide statistical measurement. Advertising tools must be evaluated separately.
The table below shows the basic purposes of use. Categories not present on the site must be removed before publication.
| Purpose of Use | Description | Possible Cookie Type |
|---|---|---|
| Session Management | Enable uninterrupted navigation within the site for the user | Mandatory cookie |
| Cart Function | Enable temporary remembering of selected products | Mandatory cookie |
| Security | Reduce suspicious movements and unauthorized transactions | Mandatory cookie |
| Preference Remembering | Store language, appearance or user settings | Functional cookie |
| Statistical Measurement | Evaluate visit behaviors in aggregate form | Performance or analytics cookie |
| Advertising Management | Measure or personalize promotional works | Advertising or marketing cookie |
Each cookie must be used only within the explained purpose. When new functions are added, the preference system must be re-examined.
4. Cookies by Duration
Cookies may vary according to their duration on the browser. Temporary records may be deleted at session end. Persistent records may be stored for a determined period. Durations must not be kept longer than necessary.
The table below shows the duration-based separation. Exact retention periods must be added after technical scanning.
| Cookie Type | Basic Feature | Possible Usage Area |
|---|---|---|
| Session Cookie | May be deleted when the browser session ends. | Cart, login or security transactions |
| Persistent Cookie | May be kept on the device for a certain period. | Preference, analysis or advertising functions |
The durations of persistent cookies must be shown clearly in the technical inventory. Records with indefinite duration must be examined separately.
5. Mandatory Cookies
Mandatory cookies help the site's basic functions to operate. Without these cookies, some areas may not work properly. Session security or preference record may be an example of this. They must not be used for marketing purposes.
Users must be clearly informed about mandatory cookies.. However, it may not be possible to opt out in every case. This category must be interpreted narrowly. The mandatory label must not be used to legitimize unnecessary tracking tools.
The table below shows the inventory fields for mandatory cookies. Actual cookie names must be written after technical scanning.
| Cookie Name | Provider | Purpose | Duration | Party |
|---|---|---|---|---|
| [COOKIE NAME] | [PROVIDER] | [SESSION / SECURITY / CART / PREFERENCE RECORD] | [DURATION] | [FIRST PARTY / THIRD PARTY] |
This table must be filled when the live site scan is completed. Unused example rows must be removed.
6. Functional Cookies
Functional cookies may improve user experience. Language, appearance or personalization preferences may be remembered. These records are not always mandatory. If the user's request is not clear, preference must be obtained.
The site may continue to work when functional cookies are turned off.. However, some personalization options may become disabled. This result must be shown clearly to the user. Preference management must be understandable.
The table below shows the inventory format to be used for functional cookies. Exact information must be added after technical scanning.
| Cookie Name | Provider | Purpose | Duration | Default Status |
|---|---|---|---|---|
| [COOKIE NAME] | [PROVIDER] | [PREFERENCE REMEMBERING PURPOSE] | [DURATION] | [PASSIVE / TECHNICAL EXAMINATION REQUIRED] |
Functional cookies must also be evaluated according to the actual usage structure. Unnecessary records must be removed.
7. Performance and Analytics Cookies
Analytics cookies may provide statistics regarding site usage. Visited pages or session behaviors may be measured. These records may be used in site development works. They must not be run automatically without obtaining preference.
The anonymization options of analytics tools must also be examined. IP masking alone may not be sufficient. External service providers must be evaluated separately. Actual technical settings are the basis.
The table below shows the inventory structure to be used for analytics cookies. Each provider must be explained in a separate row.
| Cookie Name | Provider | Purpose | Duration | Default Status |
|---|---|---|---|---|
| [COOKIE NAME] | [EXAMPLE: ANALYTICS SERVICE PROVIDER] | [STATISTICAL MEASUREMENT PURPOSE] | [DURATION] | Passive |
Analytics technologies must be activated after the visitor's preference. When consent is not given, relevant commands must not be loaded.
8. Advertising and Marketing Cookies
Advertising cookies may be used to measure or personalize promotional activities. These tools may track visitor behaviors. External advertising platforms may create additional records. They must not be activated without obtaining clear preference.
Advertising technologies must be kept passive by default. The user must be able to easily reach the reject option. Preferences must be changeable later. Advertising cookies cannot be put into the mandatory cookie category.
The table below shows the inventory structure to be used for advertising cookies. Platforms not actually used must not be added.
| Cookie Name | Provider | Purpose | Duration | Default Status |
|---|---|---|---|---|
| [COOKIE NAME] | [ADVERTISING PLATFORM] | [MEASUREMENT / RETARGETING / PERSONALIZATION] | [DURATION] | Passive |
Advertising tools must be run after acceptance in the preference panel. In case of rejection, loading must be blocked.
9. Embedded Content and External Services
External content may be used on the website. Video, map or social media components may place cookies. These services may be operated by independent providers. Each component must be examined separately.
Embedded content must not be loaded without obtaining user preference. A preview area may be used. Content may only be activated after active selection. This way, unnecessary record creation may be reduced.
The table below shows the technical examination areas of external services. Unused components must be removed from the text.
| Service Type | Possible Provider | Examination Subject | Preference Approach |
|---|---|---|---|
| Video Player | [PROVIDER] | Embedded video cookies | Must be loaded after user preference. |
| Map Component | [PROVIDER] | Location and viewing records | Technical structure must be evaluated separately. |
| Social Media Component | [PROVIDER] | Tracking and interaction records | Must be kept passive by default. |
| Live Support Tool | [PROVIDER] | Session and messaging cookies | Must be examined separately according to its function. |
External services' policies may change over time. Technical scanning must be renewed at certain intervals.
10. Cookie Preference Panel
The cookie preference panel must offer the user real choice opportunity. Accept and reject options must be accessible. Non-mandatory categories must be kept passive initially. The user must be able to easily access detailed settings.
Panel design must not be misleading. The accept button must not be unnecessarily emphasized. The reject option must not be hidden. Category descriptions must be kept simple.
The list below shows the basic options that must be present in the preference panel. The technical infrastructure must actually implement these functions.
- Accept All
- Reject All
- Manage Preferences
- View Mandatory Cookies
- Turn Functional Cookies On or Off
- Turn Analytics Cookies On or Off
- Turn Advertising Cookies On or Off
- Save Preferences
- View Policy Text
- Change Preferences Later
The panel must not be just a visual notification. The user's selection must be technically implemented.
11. Sample Cookie Notification Text
The short text below may be used in the cookie panel to be shown during the first visit. The text must include direction to the detailed preference area.
Sample short notification: Mandatory cookies are used on our website. You activate functional, analytics and advertising cookies according to your preference. You may change your selections whenever you wish.
The list below shows the buttons that can be used in the notification area. Buttons must be presented at the same visibility level.
- Accept All
- Reject All
- Manage Preferences
The short notification does not replace the detailed policy. The user must be able to easily access the full text.
12. Changing Preferences Later
The user must be able to change their cookie selections later. A persistent link may be shown in the footer area. The preference panel must be re-openable. New selections must be technically implemented.
Preference change affects future loads. Records remaining in the browser may also be deleted separately. The user may also use browser settings. Preference management must be continuously accessible.
The list below shows the steps that can be offered for preference change. User experience must be kept simple.
- Open the "My Cookie Preferences" link in the footer area.
- View the active categories.
- Turn off the categories you don't want.
- Save your new selections.
- If necessary, clear browser cookies.
- Reload the page.
When preferences are saved, the new status must be implemented by the system. A malfunctioning panel must be examined separately.
13. Management via Browser Settings
Users may delete or block cookies via browser settings. Each browser may offer different options. Blocking mandatory cookies may disrupt some functions. Site experience may be limited.
The table below shows the possible results of browser settings. The user must examine the current settings on their own device.
| Browser Operation | Possible Result | Element to Note |
|---|---|---|
| Deleting All Cookies | Saved preferences may be removed. | Site preferences may be re-selected. |
| Blocking Third-Party Cookies | External services may be limited. | Embedded content may not work. |
| Blocking All Cookies | Basic site functions may be affected. | Cart or session transactions may be disrupted. |
| Deleting Cookies at Session End | Persistent preferences may not be preserved. | Settings may be re-selected. |
Browser management is independent of the preference panel within the site. The user may use both methods together.
14. Effect of Data Transfer Abroad
Some third-party cookie providers' infrastructure may be located abroad. Analytics, advertising or embedded content services must also be examined. Transfer conditions may vary according to the tool used. Actual system architecture is the basis.
Tools with the possibility of transfer abroad must be shown in the technical inventory. Legal basis must be evaluated separately. Necessary assurance mechanisms must be examined. Assumption-based lists must not be used.
The table below shows the basic fields that can be used in transfer examination. Exact information must be verified with provider documents.
| Provider | Service Type | Server or Transfer Status | Legal Examination |
|---|---|---|---|
| [PROVIDER] | [ANALYTICS / ADVERTISING / VIDEO / MAP] | [TO BE VERIFIED] | [LEGAL BASIS TO BE EXAMINED] |
This section must be updated after the real technical infrastructure is verified. Unused services must not be included in the text.
15. Cookie Inventory
The cookie inventory must show the technologies working on the live site in detail. Each cookie must be written in a separate row. Provider information must be clearly stated. Durations must be technically verified.
The table below is the template for the final cookie list to be published. After technical scanning is complete, example fields must be replaced with real information.
| Cookie Name | Category | Provider | Purpose | Duration | Party | Default Status |
|---|---|---|---|---|---|---|
| [COOKIE NAME] | [MANDATORY / FUNCTIONAL / ANALYTICS / ADVERTISING] | [PROVIDER] | [SHORT AND CLEAR PURPOSE] | [DURATION] | [FIRST PARTY / THIRD PARTY] | [ACTIVE / PASSIVE] |
The cookie inventory must be updated as new integrations are added. Technical scanning must be repeated at certain intervals.
16. User's Rights and Application Method
Users may manage their cookie preferences. They may request information about technical problems. They may reject non-mandatory cookies. They may change their saved preferences later.
The list below shows the basic transactions users may apply regarding cookies. Applications must be submitted clearly and understandably.
- Viewing cookie preferences
- Rejecting non-mandatory cookies
- Making selection based on category
- Changing saved preferences
- Deleting browser records
- Requesting information about technical problems
- Submitting relevant requests in writing
Additional information may be requested according to the nature of the applications. Unnecessary personal information must not be sent.
17. Communication Channels
Communication may be established via the following channels regarding cookie preferences or technical problems. Written notifications facilitate record creation. The subject of the request must be written clearly. A screenshot may be added if necessary.
The table below shows the communication channels that can be used. The relevant method must be chosen according to the nature of the request.
| Channel | Information | Purpose of Use |
|---|---|---|
| Brand | Pleated Blind | Cookie preferences and technical notifications |
| Phone | +90 540 336 3873 | General information |
| +90 540 336 3873 | Written support and screenshot sharing | |
| info@pliseperde.com | Technical requests and written notifications | |
| Address | Esenyalı Mah. Edebali Cad. No:13/C, 34903 Pendik/Istanbul | Written applications |
Phone calls may be used to provide general information. It is recommended that detailed requests be submitted in writing.
18. Policy Updates
Pleated Blind may update the cookie policy according to technical changes. New services may be evaluated separately. Unused tools must be removed from the inventory. The current version must be published on the website.
Substantial changes must be reflected in the preference panel. The validity of previous selections must be examined separately. Re-preference may be obtained if necessary. The policy text must be continuously kept consistent with the technical infrastructure.
19. Entry into Force
This Cookie Policy enters into force on June 12, 2026. The policy was prepared to explain cookie usage on the website. It may be updated when the technical inventory changes. The current text is published in an accessible manner.
The table below shows the basic version information regarding the document. The version number must be changed when updated.
| Document Information | Value |
|---|---|
| Document Name | Cookie Policy |
| Brand | Pleated Blind |
| Data Controller | [OFFICIAL TRADE TITLE TO BE ADDED] |
| Entry into Force Date | June 12, 2026 |
| Version | 1.0 |
| Contact Email | info@pliseperde.com |
The policy must be kept consistent with the real cookies used in the live system. Assumption-based cookie lists must not be published.