Explicit Consent Text

This text regulates the optional data processing activities that may be carried out by Pleated Blind. Mandatory order records do not fall within the scope of this consent. The buyer decides only for the transactions they choose, of their own free will. Each preference is managed independently. Not giving consent does not prevent shopping. Explicit consent can only be used for transactions limited to specific purposes. Given permission can be withdrawn later.

1. Purpose and Legal Nature of the Text

Explicit consent is a declaration of will regarding the use of personal data within specific transactions. This declaration cannot be general, unlimited or indefinite. The data subject should be able to understand which transaction they are permitting. Results must be shown clearly.

Pleated Blind requests explicit consent only for optional activities. Mandatory transactions may be carried out with different legal grounds. Order creation, invoicing or delivery is not linked to this text. Each purpose is evaluated separately.

The table below explains the basic concepts used in this text. The boundaries of the concepts must be preserved on application screens.

Concept Description Application Equivalent
Explicit Consent Free will declaration for a specific transaction Empty checkbox marked by the user
Data Subject Natural person whose personal data is processed Customer, visitor or applicant
Data Controller Business that determines processing purposes and methods Official business using the Pleated Blind brand
Optional Transaction Activity not mandatory for service provision Visual publication or reference sharing
Withdrawal of Consent Data subject's future-oriented permission revocation Stopping transactions after the request date

Definitions are used only for transactions subject to explicit consent. Other activities are evaluated with their own legal bases.

2. Data Controller's Identity Information

The data controller carrying out activities subject to explicit consent must be clearly stated. The brand name alone is not sufficient. Official business information must be completed before publication. Application channels must be kept accessible.

The table below shows the basic information belonging to the data controller. Fields in brackets must not be left empty.

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
WhatsApp +90 540 336 3873
Email info@pliseperde.com
Address Esenyalı Mah. Edebali Cad. No:13/C, 34903 Pendik/Istanbul

When official information changes, current records must be reflected on the website. Old text versions may be archived when necessary.

3. Basic Principles of Explicit Consent

Explicit consent must be related to a specific subject. The data subject must be informed before the transaction. Preference must not be taken under pressure. Service provision must not be linked to unnecessary consents.

General expressions do not create a valid permission mechanism. Expressions such as "any kind of data processing" must not be used. Each transaction must be shown with its own name. Certainty is the principle.

The list below shows the basic principles that must be preserved on the consent screen. Technical design must be prepared in accordance with these principles.

  • A separate selection area must be used for each purpose.
  • Checkboxes must be left empty by default.
  • Not giving consent must not prevent shopping.
  • Information must be clear and simple.
  • The scope of permission must not be left indefinite.
  • Consent record must be provable when necessary.
  • Withdrawal method must be easily accessible.
  • Purposes not actually implemented must not be shown.

These principles strengthen the legal nature of the permission screen. User experience must be kept simple.

4. Distinction Between Mandatory and Optional Transactions

Explicit consent is not the basis for every personal data transaction. Information mandatory for receiving the order may also be evaluated. Delivery address may be used for the purpose of delivering the product. Invoice information may be processed due to legal obligations.

Optional transactions, on the other hand, must be left to the customer's explicit choice. Promotional use of visuals may be an example of this. Reference publication may also require separate permission. Mandatory services must not be linked to optional consents.

The table below separates transaction types from each other. Rows that do not overlap with the actual activity model must be removed.

Transaction Type Example Activity Explicit Consent Approach
Mandatory Order Transaction Using measurement record for product preparation Must not be linked to explicit consent in any case.
Mandatory Delivery Transaction Using address information for transport purposes Evaluated separately within service provision scope.
Mandatory Invoice Transaction Arranging legal documents Examined within legal obligation scope.
Optional Visual Publication Sharing application area photo for promotional purposes Separate explicit consent selection must be used.
Optional Reference Sharing Publishing customer review with name Separate explicit consent selection must be used.
Optional Promotional Content Using post-installation visuals in catalog Separate explicit consent selection must be used.

Mandatory transaction records and optional records must be stored in separate system fields. The basis of each activity must be shown separately.

5. Optional Visual Use

Pleated Blind may want to share application results for promotional purposes. This activity is not mandatory. Images must not be published unless the customer explicitly permits. Photos must be used only in permitted channels.

Application area visuals may contain personal belongings or living space. Unnecessary parts must be cropped out. Anonymization should be applied if possible. Privacy must be protected at every stage.

The table below shows the preference fields that must be managed separately for visual use. Unused channels must be removed from the text.

Visual Use Area Scope Preference
Website Publication as product or application example [APPROVAL / REJECTION]
Social Media Sharing on Pleated Blind accounts [APPROVAL / REJECTION]
Digital Catalog Use as example in product presentations [APPROVAL / REJECTION]
Printed Promotional Material Use in brochures or catalogs [APPROVAL / REJECTION]
Advertising Works Visual use in promotional campaigns [APPROVAL / REJECTION]

A separate selection must be made for each channel. Permission given to one channel does not automatically cover other channels.

6. Customer Review and Reference Sharing

Customer reviews must be published only within the permitted scope. Name, surname or profile information must be evaluated separately. Anonymous sharing may be preferred. Separate permission must be obtained for adding visuals.

The table below shows the different options that can be used in reference sharing. Preference fields must be presented clearly.

Reference Type Sharing Format Preference
Anonymous Review Publication without stating name [APPROVAL / REJECTION]
Review with Name Showing only name information [APPROVAL / REJECTION]
Review with Name and City Using name with general location information [APPROVAL / REJECTION]
Review with Visual Publishing application photo with review [APPROVAL / REJECTION]
Video Reference Using video shared by customer [APPROVAL / REJECTION]

Review text may be confirmed with the customer before publication. New information outside the permission scope must not be added.

7. Preferences Regarding Social Media Shares

Social media platforms are operated by independent organizations. Shared content may reach large audiences. Re-sharing or screenshotting may be possible. For this reason, the permission scope must be shown clearly.

Pleated Blind should share only explicitly permitted content. Unnecessary personal elements must not be present in photos. Location information should be limited if possible. A separate selection must be made for social media publication.

The list below shows the checks that can be applied before social media sharing. The publication process may be recorded.

  1. Determine the image to be shared.
  2. Remove unnecessary personal elements.
  3. Limit location information.
  4. Check the permitted platforms.
  5. Determine whether the customer name will be shown.
  6. Record the approval date.
  7. Store the publication link.
  8. Evaluate withdrawal requests without delay.

Content removal requests may be implemented on channels controlled by Pleated Blind. Third parties' re-shares are evaluated separately.

8. Sample Explicit Consent Selection Fields

The selection fields below may be used on the website or physical form. Each box must be left empty initially. The user should select only the transactions they accept. A single general approval box must not be used.

Sample consent declaration: I have been informed about the personal data processing activities I selected below. I give explicit consent only within the scope of the preferences I have marked. I know that I can withdraw my preferences later.

The list below shows sample selection fields that can be presented separately. Fields not actually implemented must be removed before publication.

  • [ ] I consent to the publication of my application area visuals on the website.
  • [ ] I consent to the sharing of my application area visuals on social media accounts.
  • [ ] I consent to the use of my application area visuals in digital catalogs.
  • [ ] I consent to the use of my application area visuals in printed promotional materials.
  • [ ] I consent to the anonymous publication of my customer review.
  • [ ] I consent to the publication of my customer review with only my name.
  • [ ] I consent to the publication of my customer review with my name and city information.
  • [ ] I consent to the use of the video reference I shared for promotional purposes.

Each box represents a different processing purpose. The user must be able to change their selections separately.

9. Recording of Explicit Consent

Explicit consent records must be stored in a way that can be proven when necessary. The purposes selected by the user must be shown clearly. Date, time and form version must be recorded. The digital transaction source may also be kept separately.

The table below shows the basic record fields that must be stored. Rows that do not overlap with actual infrastructure must be removed.

Record Field Description Purpose of Use
Consenting Person Name and contact information Verification of the data subject
Selected Purpose Permitted processing activities Determination of scope
Approval Date Date and time information Verification of permission history
Text Version Document version shown to the user Proving the consent content
Permission Source Web form, physical form or digital channel Showing the transaction method
Withdrawal Date Permission revocation time if any Stopping subsequent transactions

Records must be kept for the period connected to the purpose. Appropriate measures must be applied against unauthorized access.

10. Withdrawal of Explicit Consent

The data subject may withdraw the explicit consent they gave at any time they wish. The withdrawal transaction produces future-oriented results. Transactions before the request are evaluated separately. New shares must be stopped.

Necessary transactions may be made on internet pages under Pleated Blind's control. Social media shares may be removed to the extent possible. Printed materials are evaluated separately. Right of withdrawal is reserved.

The table below shows the effect of the withdrawal request in different usage areas. Each application is examined with its own conditions.

Usage Area Transaction After Withdrawal Description
Website Content may be removed from publication. Technical processing time is taken into account.
Social Media Account Pleated Blind share may be removed. Third-party re-shares are evaluated separately.
Digital Catalog May be removed from new version. Previous distributions may not be technically withdrawn.
Printed Material Use may be stopped in new prints. Printed materials in circulation are evaluated separately.
Customer Review Visibility may be ended on controlled channels. Request record may be stored.

Withdrawal applications must be submitted by written methods. The scope of the request must be clearly stated.

11. Explicit Consent Withdrawal Application

The data subject may withdraw their permissions completely or partially. Which activity is requested to be stopped must be written clearly. Identity verification may be required. The application may be recorded.

The list below shows the information recommended to be included in the withdrawal request. Unnecessary personal data must not be sent.

  • Name and surname
  • Registered contact information
  • Type of consent to be withdrawn
  • Related usage area
  • Share link if any
  • Order number if any
  • Request date
  • Reachable communication channel

The application may only affect the specified transaction areas. Additional information may be requested for requests with unclear scope.

12. Application and Communication Channels

Requests regarding explicit consent preferences may be submitted via the following channels. Written applications facilitate record creation. Information suitable for identity verification should be shared. Sensitive documents must not be sent unnecessarily.

The table below shows the communication channels that can be used. The method appropriate to the nature of the request must be preferred.

Channel Information Purpose of Use
Brand Pleated Blind Explicit consent preferences
Phone +90 540 336 3873 General information
WhatsApp +90 540 336 3873 Written request and direction
Email info@pliseperde.com Consent withdrawal and written applications
Address Esenyalı Mah. Edebali Cad. No:13/C, 34903 Pendik/Istanbul Written notifications

Phone calls may be used to provide general information. It is recommended that consent withdrawal requests be submitted with written confirmation.

13. Version Management and Entry into Force

Pleated Blind may update explicit consent screens according to activity structure. New transaction purposes may be evaluated separately. Existing permissions cannot be expanded to unexplained purposes. A separate selection must be offered for new activities.

Text changes must be tracked with version number. The version shown to the user must be stored. Withdrawal records must also be preserved separately. The permission scope cannot be unilaterally expanded later.

The table below shows the basic version information regarding the document. Records must be changed when updated.

Document Information Value
Document Name Explicit Consent Text
Brand Pleated Blind
Data Controller [OFFICIAL TRADE TITLE TO BE ADDED]
Entry into Force Date June 12, 2026
Version 1.0
Application Email info@pliseperde.com

This text must contain only actually implemented optional activities. Unused selection fields must be removed before publication.

10.000+

Happy Customers

%98

Satisfaction Score

Custom Size

Custom Production Guarantee

81 Provinces

Delivery Across Turkey

100% Guaranteed

Custom-Size Compatible

Pull to refresh
Chat on WhatsApp