Review the complete legal packet in the current site language. The documents are grouped into four clear sections so teams can find the right policy without scanning a long footer list.
Download one PDF file that contains the full legal packet in the current language.
Use this contact point for legal notices, privacy requests, and document-related questions.
The main contractual rules for using the product, workspace, and related support channels.
How personal data is handled, what cookies are used, and how processor commitments are described.
Where users can review privacy rights and the channels available for submitting requests.
Turkey-specific notices and optional explicit consent texts that apply when Turkish rules are relevant.
We use personal data to operate the ERP and the surrounding service relationship.
Depending on the context, we process data because it is necessary to perform a contract, meet a legal obligation, protect legitimate business interests, establish or defend legal claims, or because a user has given an optional consent.
We may share personal data only with parties that need it for the relevant purpose and under appropriate safeguards.
If a transfer outside the relevant jurisdiction requires an additional legal mechanism or explicit consent, we rely on that mechanism separately rather than assuming a general acceptance.
We retain data only for as long as needed for the stated purpose, the contract, support obligations, security review, and legal or accounting retention duties. We use access controls, least-privilege practices, authentication safeguards, logging, and provider-level security measures to reduce unauthorized access, misuse, or loss.
You may ask to access, correct, update, delete, restrict, or object to relevant processing where the law gives you that right. You may also withdraw any optional consent previously given. Requests can be sent to our contact channels described in the Privacy Rights page and the Turkish KVKK request flow, where applicable.
Last updated
April 10, 2026
These terms govern access to SINAD WholesaleERP, related support channels, demos, onboarding, and the public site provided by the service operator identified in the contact details below.
By accessing the service, requesting a demo, signing in, or using a workspace, you agree to these terms, the privacy documents, and any commercial order form or implementation statement that applies to your account.
Users must provide accurate work information, keep credentials confidential, use only authorized accounts, and follow password, session, and access-control rules defined by the operator and the customer's workspace administrators.
The service may be used only for lawful business operations and approved internal or commercial workflows.
Last updated
April 10, 2026
SINAD WholesaleERP uses cookies and similar local storage to keep the product secure, remember preferences, and support reliable operation across visits.
In this policy, 'cookies' includes browser cookies, local storage, and comparable identifiers used by the site or app shell to keep sessions, language, theme, and product preferences working correctly.
These items are required for core service operation and security.
We use local storage or cookies to remember workspace language, theme, numbering choices, and sign-in conveniences such as the last work e-mail on the device.
Last updated
April 10, 2026
This policy defines prohibited and restricted uses of SINAD WholesaleERP and applies together with the User Agreement, security controls, and any order form or onboarding scope.
The service is designed for legitimate commercial, operational, accounting, logistics, communication, and support workflows. You must use the platform only for lawful activity and only within the permissions, roles, and business scope granted to your workspace.
The following uses are prohibited:
Last updated
April 10, 2026
This addendum applies when a customer organization uses SINAD WholesaleERP to process personal data under the customer's instructions and data protection law requires controller-processor terms.
For customer data submitted to the ERP workspace, the customer generally acts as the controller or equivalent business customer, and the operator acts as the processor or service provider for the hosted service. For account administration, billing, security logging, fraud prevention, and direct legal compliance data, the operator may act under its own independent legal obligations as described in the Privacy Policy.
We process customer data only to provide, secure, support, maintain, and improve the contracted service in line with documented customer instructions, the product configuration chosen by the customer, and mandatory legal obligations.
Last updated
April 10, 2026
This page identifies core third-party processors or infrastructure providers that may handle personal data for the hosted service, depending on the tenant's enabled features.
The following providers may process limited categories of personal data on our behalf as part of the hosted service:
Some tenants may enable optional channels or external business workflows that depend on customer-configured providers. Where the customer selects, controls, or connects such a provider, the customer is also responsible for validating that provider's legal suitability for its own use case and obtaining any required permissions or notices.
Last updated
April 10, 2026
This clarification text is prepared under Law No. 6698 on the Protection of Personal Data and the Communique on the Procedures and Principles for Fulfilling the Obligation to Inform.
SINAD WholesaleERP is provided by the service operator identified in the contact details below.
Your personal data may be processed to establish and manage the business relationship, operate the ERP, fulfill support and onboarding activities, maintain accounting and legal records, manage security and authorization, and deliver operational communications.
Last updated
April 10, 2026
This text covers only optional processing activities that legally require explicit consent. It is separate from the clarification obligation and is not bundled into a general blanket approval.
Explicit consent must relate to a specific subject, be based on information, and be given freely. Refusing this optional consent does not prevent access to the core ERP functions needed for the contractual service.
Where required by law, we may request explicit consent for optional processing activities such as:
This consent does not authorize every possible future processing activity. If a new optional activity needs consent, it should be described clearly and requested separately.
Last updated
April 10, 2026
This page explains how individuals can submit privacy-related requests, including KVKK applications where Turkish law applies.
Subject to the applicable law and the role in which we process the data, you may request access, correction, completion, deletion, restriction, objection, portability where available, or withdrawal of optional consent.
You can contact us through the operator contact channels below.
To protect other users and company records, please include enough information for us to verify your identity and understand the request.
Last updated
June 6, 2026
This public page is the Data Deletion Instructions URL for Meta, Facebook, Instagram, and WhatsApp integrations connected to SINAD WholesaleERP.
If you connected a Meta account, Facebook Page, Instagram professional account, or WhatsApp Business asset to SINAD ERP, you can revoke the connection from Meta's own account settings.
You can also send a deletion request directly to the operator contact below. To protect account security, send the request from the e-mail address or business contact associated with the workspace or Meta connection.
Customers remain responsible for the legality, accuracy, and authority behind the business data they upload or process through the ERP, including customer, supplier, employee, and communication records.
Features that depend on external providers, such as authentication, e-mail, phone, WhatsApp, storage, or payment services, may also be subject to those providers' technical and legal requirements. Availability of such features can depend on configuration, verification, quotas, or provider policy changes.
Subscription fees, implementation scope, support windows, and rollout commitments are defined in the commercial agreement. We may suspend or limit access where necessary to protect security, investigate misuse, enforce payment obligations, or comply with law. Termination does not erase obligations that survive by nature, including confidentiality, payment, audit, and lawful retention duties.
The service, code, interface design, brand assets, and operator documentation remain the property of the operator or its licensors. Each party must protect confidential business information received from the other. We may update features, workflows, and legal documents over time; continued use after an effective update means the updated terms apply to future use.
Where we use optional performance diagnostics or product analytics, we do so under the legal basis required for the relevant jurisdiction. For Turkish users, optional analytics or personalization should not be bundled into mandatory acceptance if consent is legally required.
You can control cookies and local storage through your browser settings. Blocking essential cookies may prevent sign-in, security validation, language retention, or reliable workspace navigation.
You may not test, overload, or attack the service without written authorization. Automated access, imports, API-like traffic, or external tools must stay within the supported product flows and must not degrade availability, integrity, or security for others.
If you process personal data or business data belonging to customers, suppliers, employees, or contacts through the ERP, you are responsible for ensuring that your collection, notices, permissions, and communications are lawful. Where a communication channel requires opt-in, proof of consent, or channel-specific rules, you must satisfy those obligations before use.
We may investigate suspected misuse, suspend affected features, reject abusive transactions, remove unlawful content where necessary, or terminate access for serious or repeated violations. Security preservation, legal compliance, and protection of other customers take priority over uninterrupted access when abuse is suspected.
Personnel acting on our behalf must be subject to confidentiality obligations. We apply role-based access controls, authentication safeguards, logging, and commercially reasonable technical and organizational measures appropriate to the service. Where we use subprocessors, they must be engaged for legitimate service purposes and bound to protect relevant data under appropriate contractual obligations.
Taking into account the nature of the processing and the information available to us, we provide reasonable assistance for privacy requests, security issues, and legally required notifications that relate to the hosted service. Upon termination or valid customer instruction, customer data should be returned, exported, deleted, or placed beyond active use according to the product capabilities, retention schedule, and overriding legal obligations.
If a transfer mechanism is required for a restricted cross-border transfer, it must be handled through the appropriate legal mechanism for that transfer. Reasonable compliance information may be provided upon legitimate request, subject to confidentiality, security, and scope limits. If a signed commercial agreement or statutory addendum imposes stricter data protection terms, that signed document controls over this public summary to the extent of the conflict.
Not every subprocessor applies to every tenant or every user. Data shared with a provider should be limited to what is reasonably necessary for the feature being used, such as authentication, storage, billing, or WhatsApp delivery.
We may update this list when service architecture, billing flows, or communication channels materially change. The effective version and update date shown on this page should be used for legal reference and version tracking.
Questions about this list may be sent to info@larateks.com. Contractual customers who require a stricter signed processor schedule should address that requirement through their commercial onboarding or data-processing addendum workflow.
Your personal data may be transferred, limited to the relevant purpose, to authorized personnel, technology and infrastructure suppliers, communication and support providers, professional advisers, auditors, and legally authorized public institutions or authorities.
Where an international transfer requires an additional mechanism under applicable law, that mechanism is handled separately and is not assumed from this clarification alone.
Personal data may be collected through website forms, sign-in screens, cookies and local storage, support requests, direct communications, document uploads, onboarding channels, integrations, and records entered by authorized users into the ERP.
Data is retained for the duration required by the processing purpose, contract, support needs, and legal retention obligations. Access is restricted according to role and need-to-know principles, with technical and organizational measures designed to support confidentiality, integrity, and availability.
Under KVKK, you may learn whether your data is processed, request information about the processing, learn the purpose and whether it is used accordingly, know third parties to whom it is transferred, request correction, request deletion or destruction where legal conditions are met, request notification of those actions to third parties, object to an adverse result arising from automated analysis, and request compensation where you suffer damage due to unlawful processing.
Applications regarding these rights can be sent to info@larateks.com or by post to OSB Mah. 23 Nolu Cad. No: 20, Kilis, Turkiye. Detailed steps are described in the Privacy Rights page.
You may withdraw an optional consent at any time with future effect. Once withdrawal reaches the operator, the processing that depended only on that consent should stop for future activities to the extent required by law.
Questions or withdrawal requests can be sent to info@larateks.com. We may keep the minimum record needed to demonstrate that a consent was given, updated, or withdrawn.
We review each request according to the applicable legal framework, the role in which the data is processed, and any security or accounting obligations that require retention. We may ask for additional information before completing the request and respond within the legally applicable period.
For requests under Turkish law, the data subject should first apply to the data controller. If the statutory conditions are met after that application stage, the person may then use the complaint mechanisms available before the Personal Data Protection Authority.
After verification, we delete or disconnect personal data that we hold because of the Meta connection, unless a legal, security, accounting, or dispute-retention obligation requires a limited record to remain.
Business records entered by a customer workspace, such as invoices, customer ledgers, accounting entries, or messages controlled by that customer, may require a workspace-owner or company-level request and may be retained where law requires it.
We review deletion requests according to the applicable legal framework and the role in which we process the data. We may ask for additional verification before deleting or disconnecting records. Once the request is completed, we confirm the result through the contact channel used for the request.
Removing SINAD ERP from Meta disconnects our app from your Meta account. It does not delete data that Meta keeps under its own policies, and it does not automatically delete records controlled by a separate customer company inside SINAD ERP. For those records, contact the relevant workspace owner or submit a company-level privacy request using the channels above.
