Terms of Use
Last updated: 9 August 2026
This is a courtesy translation of the Turkish original (“YazBunu Kullanım Koşulları”). In case of any discrepancy, the Turkish text prevails.
1. Scope and Formation of the Agreement
These Terms of Use (“Terms”) govern the terms and conditions applicable to the use of the YazBunu service offered by Peracom Yazılım Danışmanlık A.Ş. (“Peracom” or the “Company”).
YazBunu is currently a mobile application distributed in Türkiye only. The service runs on iPhone and Android phones; on iPhone it additionally offers extra recording channels through the Apple Watch and CarPlay extensions. Desktop and web applications are not within the current scope of the service.
By downloading, installing, opening or continuing to access the YazBunu application, creating an account or using any feature within the application, the user declares that they have read, understood and accepted these Terms.
If the user does not accept these Terms, the user must not use the application and must remove it from their device.
These Terms apply together with the Privacy Policy, the Information Notice, the Explicit Consent Text and the Personal Data Retention and Destruction Policy. Mandatory provisions of the applicable legislation take precedence in respect of the processing, transfer, retention, erasure and destruction of personal data.
The Information Notice explains for which purposes and on which legal grounds personal data are processed. The Explicit Consent Text relates to features for which explicit consent is obtained separately and independently. Acceptance of these Terms does not by itself constitute the giving of explicit consent.
2. Nature and Scope of the Service
YazBunu is a digital note-taking and transcription service that allows voice notes to be created on iPhone, Android phones, Apple Watch and CarPlay, audio to be converted to text in certain types of recording, notes to be edited, summaries, decisions, tasks, titles and tags to be generated from transcripts, follow-up e-mail drafts to be prepared from meeting results, and selected text content to be optionally backed up in end-to-end encrypted form.
YazBunu’s basic note-taking and local storage functions are designed to run on the device as far as possible. However, in Meeting Mode, CarPlay and Apple Watch recordings, and in all recordings made on Android phones, the audio file may be uploaded temporarily to the YazBunu server for transcription purposes.
The temporary audio file uploaded to the server:
- is processed solely for transcription purposes,
- may be held on Supabase Storage in the Frankfurt/European Union region,
- may be converted to text via AssemblyAI’s European region endpoint
api.eu.assemblyai.com, - is deleted once processing is complete and in any event within 24 hours at the latest from its upload to the server,
- is not included in the end-to-end encrypted cloud backup.
No audio file is sent when summaries, decisions, tasks, classifications or similar structuring is carried out with artificial intelligence. Only the transcript or the text content selected by the user is processed at that stage.
Some features of the service may depend on the user separately enabling them, on device permissions, on subscription status, on the availability of third-party services, on the internet connection and on the operating system version used.
3. Definitions
In these Terms:
- YazBunu: the iOS and Android mobile application offered by Peracom and the services provided through that application,
- Company or Peracom: Peracom Yazılım Danışmanlık A.Ş.,
- User: the natural person who downloads, uses, creates an account in or benefits from YazBunu,
- Account: the user profile created so that the user can access YazBunu services,
- Content: the audio, m4a recordings, notes, transcripts, summaries, decisions, tasks, titles, tags, e-mail drafts and other data created, recorded, entered, uploaded, edited, stored or produced through the application by the user,
- User Content: the content the user records in or creates through the application,
- Meeting Mode: the feature that allows audio to be recorded in an environment where more than one person is speaking, the recording to be transcribed, and summaries, decisions, tasks and similar outputs to be generated,
- Transcription: the conversion of audio content into text,
- Structuring with Artificial Intelligence: the generation of summaries, decisions, tasks, titles, tags and similar outputs from transcripts or text content,
- Cloud Backup: the end-to-end encrypted backup of note texts, transcripts and other appropriate text content selected by the user,
- Synchronisation: the matching of text content selected by the user across authorised devices,
- Information Notice: the notice regarding the processing of personal data,
- Explicit Consent Text: the text relating to processing activities that require explicit consent,
- Privacy Policy: the general policy on the processing of personal data and user content,
- Retention and Destruction Policy: the policy governing the periods for which personal data are retained and how they are erased, destroyed or anonymised.
4. Eligibility and Age Declaration
The user must be at least 13 years old in order to use YazBunu.
Persons under 13 may not use YazBunu without the necessary permission and supervision of their legal representatives. Where the applicable legislation provides for a higher age limit, the higher age limit applies.
The user declares that the information provided when creating an account is accurate, current and belongs to them. Where it is understood that the user does not meet the age requirement, the account may be restricted or closed, or deletion of the relevant data may be considered.
YazBunu is not a service designed specifically for children. Where children’s personal data are recorded in the application, the necessary notices, permissions and legal assessments must be made separately by the user.
5. Account Creation and Account Security
A user account may be required in order to benefit from certain features of YazBunu.
The user must:
- keep account details accurate and current,
- keep account access details confidential,
- not allow third parties to use their account,
- immediately notify Peracom where they believe there has been unauthorised access to their account,
- ensure the security of their device and operating system,
- protect the encryption password and recovery information.
Transactions carried out through the user’s account may be deemed to have been carried out by the user until proven otherwise. Without prejudice to Peracom’s own fault and its liabilities arising from mandatory legislation, the user may be liable for consequences arising from sharing account details with third parties or from failing to ensure device security.
The password or recovery information used in the end-to-end encrypted cloud backup cannot be viewed, stored or regenerated on the user’s behalf by Peracom. The user accepts that if this information is lost, it may be technically impossible to restore the encrypted backup.
6. User Content and Intellectual Property
Subject to the provisions of the applicable legislation, the rights in the audio, m4a files, notes, transcripts, meeting summaries, decisions, tasks and e-mail drafts recorded in YazBunu by the user belong to the user.
The user grants Peracom only the limited right of use necessary to provide and operate the YazBunu service, ensure its security, carry out transcription or text structuring operations, generate the outputs requested by the user and provide technical support.
This right of use:
- is limited to the operations necessary to provide the service,
- does not mean that ownership of user content passes to Peracom,
- does not carry any purpose of building advertising profiles,
- does not permit user content to be sold or published outside the purpose of the service,
- does not cover the use of user content to train artificial intelligence models outside the purpose of the service.
The intellectual property rights in Peracom’s YazBunu application, application interface, software code, design, brand, logo, texts, database structure, technical architecture and other elements relating to the service belong to Peracom or the relevant rights holders.
The user is granted a limited, non-exclusive, non-transferable and revocable right to use the YazBunu application in accordance with these Terms. This right does not mean that the application is sold or assigned or that the source code is provided to the user.
The user may not:
- copy the application,
- attempt to obtain its source code,
- carry out reverse engineering,
- circumvent the application’s security mechanisms,
- use the application’s brand and design elements without permission,
- rent, sell or transfer the application to third parties.
7. Lawfulness of User Content
The user is responsible for the lawfulness of the content they create, record, upload, edit, share or send through YazBunu.
In particular, the user must:
- not unlawfully record the audio or images of third parties,
- inform meeting participants about the recording,
- where necessary, provide explicit consent or another legal ground,
- not use meeting recordings outside their purpose,
- not record special categories of personal data unless necessary,
- review transcripts, summaries, task lists and e-mail drafts before sharing them,
- delete or mask incorrect, unnecessary or disproportionate personal data,
- not infringe the private life, personality rights, confidentiality of communications or personal data of others.
YazBunu does not automatically and completely verify the lawfulness of the content created by the user. The fact that YazBunu provides a technical tool does not authorise the user to give explicit consent on behalf of third parties.
8. Use of Meeting Mode, CarPlay and Apple Watch
Meeting Mode, CarPlay and Apple Watch are recording channels that allow audio to be captured in different usage scenarios.
Where these channels are used, the following may be processed:
- the user’s voice,
- the voices of other participants,
- the content of conversations,
- meeting date, time, duration and title,
- participant information,
- data relating to persons mentioned in the meeting,
- transcripts,
- meeting summaries,
- decisions,
- task and action items,
- follow-up e-mail drafts.
Before recording starts, the user is obliged to inform participants, in a manner appropriate to the nature of the meeting and in clear and timely terms, that:
- a recording will be made,
- conversations may be converted to text,
- in certain types of recording the audio file may be transferred temporarily to the server,
- a meeting summary, decisions and task outputs may be generated,
- data may be transferred to technical service providers,
- cross-border transfers may take place where necessary,
- meeting outputs may be shared by the user.
The user is not authorised to give explicit consent on behalf of other participants. Depending on the nature of the meeting, providing the necessary legal ground, giving notice and, where required, obtaining explicit consent may be the responsibility of the user or of the corporate user.
Where a participant objects to the recording, the user must, as far as possible, stop the recording, continue the meeting without recording, or offer a suitable alternative to the objecting person.
The user must subject the transcript, summary, decisions, task list and e-mail draft generated after the meeting to human review before sharing them.
9. Audio Recordings and Transcription
In YazBunu, audio processing differs according to the platform used and the type of recording.
In live recognition of daily or work notes on iPhone, audio may be processed using Apple’s on-device or Apple speech recognition services. In this type of recording the m4a audio file remains on the device.
In Meeting Mode, CarPlay and Apple Watch recordings, the audio file may be uploaded temporarily to the YazBunu server for transcription purposes. This temporary audio file:
- may be held on Supabase Storage in the Frankfurt/European Union region,
- may be converted to text via AssemblyAI’s European region endpoint,
- is deleted once processing is complete and in any event within 24 hours at the latest from the date of upload,
- is not included in the end-to-end encrypted cloud backup,
- is not used to create a voiceprint or biometric voice profile.
No audio file is sent at the artificial intelligence structuring stage. Only the transcript or the text content selected by the user is processed at that stage.
Because on-device Turkish speech recognition is not available on Android phones, in all recordings and regardless of the type of recording the audio file is uploaded temporarily to the server for transcription purposes and is subject to the same rules as the meeting flow: it is held in the Frankfurt/European Union region, converted to text via AssemblyAI’s European region endpoint, deleted once processing is complete and in any event within 24 hours at the latest, is not included in the end-to-end encrypted cloud backup, and no voiceprint is created. Because on Android phones the temporary upload of the audio file to the server for transcription is technically necessary for the service to be provided, this processing does not rely on explicit consent but on the performance of a contract under Article 5/2-c of the KVKK (processing of the personal data of the parties to a contract being necessary, provided that it is directly related to the establishment or performance of that contract); no separate explicit consent is sought for this operation.
10. Structuring with Artificial Intelligence
By processing the transcript or text content selected by the user with artificial intelligence supported systems, YazBunu may generate:
- summaries,
- decisions,
- action items,
- to-do lists,
- task assignments,
- titles,
- tags,
- classified text,
- follow-up e-mail drafts.
No audio file is sent at this stage. Only the transcript, text written directly by the user or text excerpts selected by the user are processed.
Google Gemini may be used in the text structuring service. Depending on the product configuration or technical requirements, alternative providers such as OpenAI or Anthropic may also be used.
Because artificial intelligence outputs are generated automatically, they may not be accurate, complete or fully appropriate to the context. The user must review these outputs before sharing them or using them in an important transaction.
Artificial intelligence outputs do not replace legal, medical, financial or professional advice.
11. Cloud Backup and Synchronisation
The user may separately enable the optional end-to-end encrypted cloud backup and cross-device synchronisation feature.
Only the following, as selected by the user, may be backed up or synchronised under this feature:
- note texts,
- transcripts,
- folders,
- tags,
- other appropriate text content.
Audio files, m4a recordings and raw audio files are not included in the end-to-end encrypted cloud backup.
If the user loses the end-to-end encryption password or recovery information, Peracom may be unable to read or restore the encrypted backup technically.
Supabase’s authentication, encrypted backup and storage services may be used for the cloud backup service. This feature is not a mandatory part of the basic local note-taking function.
12. Explicit Consent and Separate User Preferences
Depending on the technical structure of the product and the legal nature of the processing activity, the following features may require a separate user preference or separate explicit consent:
- transcription of Meeting Mode, CarPlay and Apple Watch recordings,
- text structuring with artificial intelligence,
- optional end-to-end encrypted cloud backup,
- cross-device synchronisation,
- certain services requiring cross-border data transfers,
- optional personalisation and usage analysis,
- sharing of meeting results by e-mail.
The temporary upload of recordings created on Android phones to the server for transcription is not within this scope. Because on Android phones the temporary upload of the audio file to the server for transcription is technically necessary for the service to be provided, this processing does not rely on explicit consent but on the performance of a contract under Article 5/2-c of the KVKK (processing of the personal data of the parties to a contract being necessary, provided that it is directly related to the establishment or performance of that contract); no separate explicit consent is sought for this operation.
Where the user gives consent or expresses a preference in respect of one feature, this does not mean that consent or preferences in respect of other features have also been accepted.
Not giving explicit consent does not, as a rule, prevent the user from benefiting from the basic local note-taking and local storage functions. However, the relevant feature may be technically unusable or restricted.
The user may withdraw explicit consent at any time through in-app settings, the relevant permission screens or by applying to Peracom.
13. Third-Party Service Providers
The following service providers may be used in order to operate YazBunu technically:
- Supabase: Authentication, end-to-end encrypted cloud backup and temporary audio file storage services,
- AssemblyAI: Transcription of meeting, CarPlay and Apple Watch recordings, and of Android recordings,
- Google Gemini: Structuring of transcripts or selected text content with artificial intelligence,
- OpenAI or Anthropic: Alternative artificial intelligence services depending on the product configuration or technical requirements,
- RevenueCat: Management of subscription status and in-app purchase information,
- Railway: Server hosting and application infrastructure,
- Resend: Sending of account e-mails,
- The user’s own SMTP account: E-mail sending where the user chooses to use the in-app e-mail sending feature.
The presence of a provider in this list does not mean that all of the user’s data is transferred to every provider. Transfers are limited to the feature used and the processing purpose.
14. Cross-Border Data Transfers
Certain technical services of YazBunu may be provided through infrastructure located abroad or operated by companies abroad.
Operations that may give rise to cross-border transfers are:
- transcription of audio,
- text structuring with artificial intelligence,
- cloud storage,
- authentication,
- server hosting,
- subscription management,
- e-mail sending,
- technical support and security services.
Cross-border transfers are carried out in accordance with the applicable personal data protection legislation, limited to data that is connected to the purpose, necessary and proportionate.
In Meeting Mode, CarPlay and Apple Watch recordings, and in all recordings made on Android phones, the audio file may be transferred temporarily for transcription purposes only. No audio file is sent at the artificial intelligence structuring stage; only the transcript or the selected text is processed.
15. Sharing of User Content and E-mail Sending
YazBunu may generate meeting summaries, transcripts, decisions, task lists or follow-up e-mail drafts.
This content may be:
- viewed,
- edited,
- deleted,
- checked before sending
by the user.
YazBunu does not automatically send meeting outputs or e-mail drafts to recipients unless the user expressly approves.
Before an e-mail is sent, the user must check:
- the recipients,
- the subject line,
- the e-mail body,
- attachments,
- the personal data contained in the content.
Where the user expressly approves before sending, the e-mail is sent through the user’s own e-mail (SMTP) account configured in the application. When sending through the user’s own e-mail account, the recipient, subject and body of the e-mail and the connection details of the user’s e-mail account pass through the YazBunu server so that the sending can be carried out. This information is not stored on the server; the e-mail account details are kept in an encrypted area on the user’s device.
Without prejudice to Peracom’s liabilities arising from mandatory legislation and from its own fault, the user is responsible for the lawfulness of any sharing carried out by the user.
16. Retention, Erasure and Destruction
Personal data and user content are retained for the period required by the processing purpose and in accordance with the principles set out in the Personal Data Retention and Destruction Policy.
In particular:
- the temporary audio file on the server is deleted once processing is complete and in any event within 24 hours at the latest,
- error and crash records are kept for a maximum of 90 days,
- support and feedback records together with attached screenshots are kept for a maximum of 90 days,
- the on-device
diag.logandcarplay.loglogs are kept within a limit of approximately 1.5 MB; when the limit is reached, the oldest records are deleted, - audio files, m4a recordings and raw audio files are not included in the cloud backup,
- notes, transcripts, meeting summaries, decisions, tasks and e-mail drafts are placed in the deletion process when deleted by the user or when the retention purpose ends,
- where there is an ongoing dispute, official investigation or statutory retention obligation, the relevant records may be kept for a limited period.
Data whose retention period has expired are deleted, destroyed or anonymised. Destruction operations may be documented with records containing, where necessary, the date, data category, system, method and result of the operation.
17. Account Deletion
The user may delete their account immediately through the in-app account deletion function.
Upon an account deletion request, and within the framework of the applicable technical structure and legal obligations, the following are placed in the deletion process:
- the user account,
- user information linked to the account,
- selected cloud backups,
- synchronisation records,
- notes created by the user,
- transcripts,
- meeting summaries,
- decisions,
- task lists,
- appropriate e-mail drafts.
Deletion of m4a audio files present on the device must be carried out through the device or the in-app deletion function, separately from the account deletion process.
Subscription and transaction records kept by the Apple App Store, Google Play or RevenueCat may be outside Peracom’s direct control or may be kept for the necessary period due to accounting, consumer and legal obligations.
Account deletion may not automatically cancel a store subscription. The user must separately cancel any active subscription from the account settings of the relevant store (Apple App Store or Google Play).
18. The User’s Data Security Obligations
The user must:
- keep account details confidential,
- ensure device security,
- use the device lock and operating system security features,
- protect the end-to-end encryption password and recovery information,
- not share their account with third parties,
- inform meeting participants about the recording,
- review user content before sharing it,
- delete or mask unnecessary or special categories of personal data,
- not use the application for unlawful purposes,
- report any suspected security vulnerability or unauthorised access to Peracom.
Audio files, notes or transcripts stored locally on the device may be seen by third parties who gain access to the device. For this reason the physical and digital security of the device must be ensured by the user.
19. On-Device Diagnostic Logs
YazBunu may keep the following on the device in order to allow recording and connection errors to be examined technically:
diag.logfor the application,carplay.logfor CarPlay and vehicle connection.
These logs:
- do not leave the device by themselves,
- are not uploaded to the server,
- are not included in the cloud backup,
- are not sent in the background,
- are not transferred to Peracom unless the user separately shares them.
If the user wishes to share the logs:
- the log is masked on the device,
- the masked version is displayed in full,
- separate approval is obtained for each act of sharing,
- the user chooses the application through which it will be sent.
No “do not ask again” option is offered. If the user does not approve, the log does not leave the device.
20. Subscription and Payment
Sales and subscription transactions in YazBunu are carried out only through the in-app purchase system of the store from which the application was downloaded (Apple App Store or Google Play).
YazBunu does not take payment directly from the user by:
- credit card,
- debit card,
- digital wallet,
- bank transfer,
- FAST.
Payment card and payment account details are not collected or stored directly by YazBunu. Payment transactions are carried out through the relevant application store’s (Apple’s or Google’s) own payment infrastructure.
Subscription status and in-app purchase information may be managed through RevenueCat. In this context, limited information such as subscription type, purchase status, renewal, cancellation, refund and transaction identifiers may be processed.
The scope of paid features, their price, the subscription period, renewal conditions, any trial period and cancellation information are shown on the purchase screen.
Subscriptions are cancelled through the account settings of the store from which the application was downloaded (Apple App Store or Google Play). The user accepts that deleting the application may not automatically cancel the subscription.
21. Restriction and Suspension of the Service
Peracom may temporarily restrict all or part of the service in the following cases:
- maintenance or updates,
- technical failure,
- internet or third-party service interruption,
- information security risk,
- misuse,
- suspicion of unauthorised access,
- payment or subscription problems,
- breach of these Terms,
- a request from a legal or administrative authority,
- where continuation of the service is not legally or technically possible.
Peracom informs the user in advance as far as possible. In cases of urgent security or legal necessity, technical measures may be taken without prior notice.
The temporary unavailability of the service does not mean that content stored locally on the user’s device is automatically deleted.
22. Limits of Artificial Intelligence and Automated Outputs
Transcripts, summaries, decisions, tasks, titles, tags or e-mail drafts generated by YazBunu may be produced by automated or semi-automated methods.
These outputs:
- may be incomplete,
- may be inaccurate,
- may misinterpret the context of a conversation,
- may misstate person, date, task or decision information,
- may not reflect the entire meeting.
The user must review these outputs before using them in an important legal, commercial, financial, administrative or personal transaction.
YazBunu’s artificial intelligence outputs do not constitute legal, medical, financial or professional advice. The user must not take decisions with significant consequences solely on the basis of an automated output.
23. Prohibitions Relating to Use of the Service
The user may not:
- use YazBunu for unlawful purposes,
- make covert or unlawful audio recordings,
- process the personal data of others without the necessary legal ground,
- circumvent the application’s security mechanisms,
- use code, software or methods that would disrupt the operation of the application,
- carry out reverse engineering,
- upload malicious software or harmful content,
- re-offer the application to third parties as a service,
- use Peracom’s brand, software and design elements without permission,
- attempt to gain unauthorised access to the application’s infrastructure,
- access other users’ accounts or content.
In the event of a breach of these prohibitions, Peracom may suspend or close the account, restrict access, preserve the necessary evidence and pursue the applicable legal remedies.
24. Third-Party Services
Some features of YazBunu may depend on third-party services such as Apple, Google, Supabase, AssemblyAI, Google Gemini, OpenAI, Anthropic, Railway, Resend, RevenueCat or the user’s own SMTP service.
Where a third-party service:
- becomes temporarily or permanently unavailable,
- changes its terms of service,
- introduces technical limitations,
- changes its data transfer or retention practices,
- experiences a security incident,
the relevant YazBunu feature may be temporarily restricted or offered by a different technical method.
When selecting third-party service providers, Peracom aims to take into account criteria such as security, data minimisation, retention, access, service continuity and technical competence. However, matters arising from a third-party provider’s own independent operations and services are assessed separately within the framework of the relevant agreements and applicable legislation.
25. Data Protection Rights and Applications
Under the applicable personal data protection legislation, users and data subjects may have the right to:
- learn whether their personal data are processed,
- request information if their data have been processed,
- learn the purpose of processing,
- know the third parties to whom data are transferred,
- request the correction of incomplete or incorrect data,
- request erasure or destruction where the legal conditions are met,
- object to the outcome of analysis carried out by automated systems,
- claim compensation for damage arising from unlawful processing.
Applications may be made via:
E-mail: destek@peracom.net
or through the appropriate application channels within the application.
Identity verification may be requested during the application. Applications are assessed within the procedures and time limits set out in the applicable legislation.
26. Limits of Liability
Peracom does not interpret these Terms in a way that would remove or limit its liabilities arising from mandatory legislation.
However, Peracom cannot control on the user’s behalf:
- the security of the user’s device,
- the user’s sharing of account details with third parties,
- content created unlawfully by the user,
- e-mails sent by the user to the wrong recipient,
- meeting recordings made by the user without giving notice,
- backups that cannot be recovered because the user lost the end-to-end encryption password,
- the retention and security practices of the user’s own SMTP account.
Where the user loses control over their device or account, where local content on the device is seen by third parties, or where the user fails to protect their own account, Peracom cannot be held liable to the extent that it is not at fault.
No provision may be interpreted in a way that removes rights arising from consumer legislation, personal data protection legislation or other mandatory rules of law.
27. Governing Law and Competent Courts
Turkish law applies to the application of these Terms of Use.
In disputes arising from consumer transactions, the mandatory provisions of legislation concerning the jurisdiction and competence of consumer arbitration committees and consumer courts at the consumer’s place of residence or at the place where the transaction was carried out are reserved.
In disputes that are not consumer transactions and where the parties may freely determine jurisdiction, the courts and enforcement offices within the jurisdiction of the İstanbul Courthouse are competent.
The user’s statutory rights of application arising from their status as a consumer cannot be limited by this provision.
28. Corporate Services
The service currently offered by YazBunu falls within the scope of an individual mobile application; corporate services, corporate accounts or service level agreements are not a mandatory part of the current product.
Where corporate services are offered in the future, additional documents such as:
- a corporate supplementary agreement,
- a data processing agreement
may be executed.
Where there is a conflict between special provisions relating to corporate services and these Terms, the special provision set out in the relevant corporate document may apply. Mandatory provisions of personal data protection legislation are reserved.
29. Changes
Peracom may update these Terms in the following cases:
- a change in legislation,
- a change in the technical infrastructure,
- the addition of a new feature,
- a change of third-party service provider,
- an update to retention periods,
- a change to the subscription model or pricing,
- a change in security requirements.
Changes that materially affect users’ rights or obligations are announced by in-app notification, e-mail or another appropriate method.
Where the purposes of processing personal data, the categories of data, the recipients of transfers or the processes requiring explicit consent change, a further information notice is provided and, where necessary, explicit consent is obtained again.
The updated Terms enter into force on the stated effective date. The user’s continued use of the application after an update may mean that the new Terms have been accepted; however, a separate explicit consent process is operated for transactions requiring explicit consent.
30. Entirety, Severability and Waiver
These Terms constitute the entire agreement between the parties regarding the use of YazBunu and are assessed together with the Privacy Policy, the Information Notice, the Explicit Consent Text and the Retention and Destruction Policy.
If any provision of these Terms becomes invalid or unenforceable, this does not affect the validity of the other provisions. An invalid or unenforceable provision is replaced, as far as possible, by a valid provision closest to its purpose.
Peracom’s failure to exercise a right in a particular case does not mean that it has waived that right or the power to exercise it in subsequent cases.
31. Effective Date and Data Controller Details
These Terms of Use enter into force on the date stated below.
Effective Date: 9 September 2026
Last Updated: 9 September 2026
Service Provider and Data Controller: Peracom Yazılım Danışmanlık A.Ş.
Address: Gülbahar Mahallesi, Avni Dilligil Sokak, Çelik İş Blokları A Blok, No: 11 Floor: 4 Office: 417, Şişli / İstanbul, Türkiye
E-mail: destek@peracom.net
Telephone: +90 212 243 10 80