Privacy Policy
This policy explains how personal data is processed when you use the intordia.com website and the intordia.app platform (together, the “Service”). It is our notice under the Turkish Personal Data Protection Law No. 6698 (KVKK), Article 10, and the EU General Data Protection Regulation (GDPR), Articles 13–14. If the Turkish and English versions differ, the Turkish version prevails.
In short
- Intordia is a brand of Serkan Ceylan, sole proprietorship. We are the controller for our own user accounts.
- Data a business enters into or connects to the platform belongs to that business; we process it only to provide the service.
- We do not sell your data, we do not use it for our own advertising, and we do not use tracking or advertising cookies.
- Data from Google is used only for the feature you connect; it is never sold, never used for any advertising, and never used to train or improve AI models. Data from Meta is never used to train AI either.
- We do not read your Gmail or any other mailbox through your Google or Microsoft account.
- Our servers are in Germany (European Union).
- You can delete your account and data, and write to info@intordia.com about your rights.
1. Data controller
SERKAN CEYLAN (sole proprietorship, Türkiye) — owner of the “Intordia” brand.
Location: Kırıkkale, Türkiye
E-mail: info@intordia.com · Web: https://intordia.com · Platform: https://intordia.app
“We”, “us” and “Intordia” in this policy refer to the data controller above.
2. Our two roles
intordia.app is a platform that businesses (“Customers”) use to run their work. It is made of separate apps (Sales, Inbox, Outreach, Digital marketing, AI, Stock and warehouse, Marketplaces, Finance, Field, Projects, Foreign trade), and every Customer also gets a common base (contacts and companies, calendar, tasks, approvals, workflows, notes, files, team, notifications). We therefore act in two roles:
- As controller for the account data of people who use the platform (name, e-mail, login and security records), our correspondence with you, app requests and billing data.
- As processor for the data a Customer enters into the platform or receives through channels it connects — for example its contact records, WhatsApp/Instagram/Messenger conversations, e-mail archive, calendar entries, forms and bookings, field checklists and photos. The Customer is the controller of this data; we process it only on the Customer’s instructions and to provide the Service.
If you are a customer, employee or visitor of one of our Customers (for example, you messaged a business on WhatsApp or reported a problem through a QR code in a building), please contact that business first about your data. If you write to us, we will forward your request to the business and help it respond.
3. Data we process
| Category | Examples | Source |
|---|---|---|
| Identity and contact | Name, e-mail, phone, profile photo, company name, job title | You or the admin who invited you; Google if you use “Sign in with Google” |
| Account security | One-way password hash, two-step verification data, sessions, IP address, browser details, login attempts | Collected automatically when you use the Service |
| Activity records | Who changed which record and when (audit log); access logs; AI connection (MCP) and API calls | Automatic |
| Usage information | How often screens are used | Automatic |
| App requests and billing | Which apps you request, billing name, tax details, address, payment status | You |
| Correspondence | Support and contact e-mails | You |
| Customer data (as processor) | The Customer’s contact and lead records, message content and media, e-mail archive, calendar events and attendees, form and booking data, sales and quote records, ad source information (ad click IDs, campaign tags) and ad-sharing consent records, stock and order records, project tasks, field checklists, photos and signatures, advertising and web analytics reports | The Customer, its staff and the services it connects |
We do not aim to collect special categories of data (health, religion, biometrics, etc.); the platform has no face or fingerprint recognition. Customers are responsible for not entering such data, or for meeting the legal conditions if they do.
4. Purposes and legal bases
| Purpose | KVKK Art. 5(2) | GDPR Art. 6(1) |
|---|---|---|
| Creating your account, signing you in, providing the Service, turning on requested apps, running the channels you connect | (c) performance of a contract | (b) contract |
| Account and system security, abuse prevention, debugging, audit log | (f) legitimate interest | (f) legitimate interest |
| Invoicing, tax and accounting duties, requests from authorities | (ç) legal obligation | (c) legal obligation |
| Establishing, exercising or defending legal claims | (e) establishment or protection of a right | (f) legitimate interest |
| Usage measurement to improve the Service (not for personalised advertising) | (f) legitimate interest | (f) legitimate interest |
| Answering support requests | (c) contract / (f) legitimate interest | (b) / (f) |
| Account, security and service e-mails (invitations, alerts, invoices), sent from system@intordia.com | (c) contract / (f) legitimate interest | (b) / (f) |
| Product news and marketing e-mails to people who use the platform (section 13) | explicit consent (Art. 5(1)) or, where permitted, (f) legitimate interest | (a) consent / (f) |
We do not sell personal data, we do not share it with third parties for our own advertising, and we do not make decisions with legal effects about you based solely on automated processing.
5. Meta services (WhatsApp, Instagram, Messenger, Facebook)
A Customer can connect its own WhatsApp Business account, Instagram professional account or Facebook Page to intordia.app. A connection is made only with the approval of the Customer’s authorised person and can be removed at any time.
| Service | What we use it for | What we store |
|---|---|---|
| WhatsApp Business Platform (Cloud API) | Showing messages sent to the business in its inbox, sending the business’s replies and template messages, tracking message status (delivered, read), and handling calls where the business enables them | Phone number or the user ID provided by Meta, profile name, message content, media files, message status. Calls are not recorded. |
| Instagram messaging | Showing and replying to messages sent to the business’s Instagram account | Instagram user ID, username, name, profile picture link, messages and media |
| Messenger and Facebook Pages | Showing and replying to messages sent to the Page; if the business chooses, importing Facebook Lead Ads form submissions into its leads | Page-scoped user ID, name, profile picture link, messages and media; lead form fields and which ad/form they came from |
| Meta ads reporting | Reporting the business’s aggregate ad results such as spend, impressions and clicks (read-only) | Campaign-level aggregate numbers; no person-level data |
The Meta permissions we request are used only for the purposes above: whatsapp_business_management, whatsapp_business_messaging, business_management, instagram_business_basic, instagram_business_manage_messages, pages_show_list, pages_manage_metadata, pages_messaging, pages_read_engagement, leads_retrieval, pages_manage_ads, ads_read. We do not use data received from Meta for ad targeting, we do not sell it, and we do not use it to train any AI model. We share it only with the sub-processors that run the Service (section 14), with our AI provider if the Customer has turned on the AI app (section 11), if a user of the Customer connects their own AI assistant, with that assistant to the extent the user asks (section 12), and, if the Customer turns it on for its own advertising, as feedback to Meta on the Customer’s instruction (section 13). WhatsApp messages are delivered through Meta’s infrastructure (WhatsApp Cloud API) and are also processed in Meta’s own data centres, under Meta’s own terms. Access tokens are stored encrypted. For deletion requests see Data deletion.
6. Google services
Users can sign in with their Google account and, if they choose, connect the Google services below. For each connection Google shows you the permissions we request and asks for your consent. Permissions are requested only when you choose them.
| Connection and scope | What we use it for | What we store |
|---|---|---|
Sign in with Googleopenid, email, profile | Identifying your account and signing you in | Name, e-mail, Google account ID, profile picture |
Google Calendarcalendar.events, calendar.calendarlist.readonly (optional) | Showing your calendar events to you in the platform; creating, updating and cancelling the meetings and bookings you schedule in the platform; checking busy times in other calendars you select to find free slots | A copy of events from the last 30 days to the next 120 days (title, description, location, meeting link, time, attendees’ names and e-mails). Events marked “private” are not linked to customer records. Your teammates do not see the content of your Google events, only “busy” times. |
Google Contactscontacts.readonly, contacts (write optional) | Importing contacts from your address book into the business’s customer records; if you grant write access, sending the customer records you own to your address book | Name, e-mail, phone, company, address; sync mapping. Records imported from Google are marked as “from Google”. |
Google Drivedrive.file | Linking only the file you pick to a record; saving documents such as quotes to your Drive when you ask | The picked file’s name, type, size and link. File content is not stored; no other Drive files are accessed; the Drive access token is not stored. |
Google Analyticsanalytics.readonly | Showing website traffic reports for the business | Daily aggregate numbers (visitors, sessions, page views, aggregate age and gender ranges) |
Google Search Consolewebmasters.readonly | Reporting how the business’s website appears in search | Search queries, pages, clicks, impressions, position |
Google Adsadwords | Reporting campaign spend and results and showing keyword ideas. Although this scope is technically broad, we use it read-only; we never change campaigns. | Campaign-level aggregate numbers |
Google Business Profilebusiness.manage (when enabled) | Reporting the business’s profile locations and performance numbers. This connection is not generally available yet; when it is, the permission is requested only when you choose this connection. | Location names and daily aggregate numbers |
Permissions we do not request: we do not request access to read your Gmail (gmail.readonly or similar), and we do not access your Gmail messages through Google APIs. A business’s e-mail archive works with copies sent from the business’s own mail server (section 8).
Google API Services User Data Policy disclosure. Intordia’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- We use Google user data only to provide and improve the user-facing features described above.
- We do not sell this data, and we do not use it for any advertising (including personalised or retargeted advertising) or for credit decisions. Data received from Google APIs is not included in what a Customer sends for its own advertising (section 13).
- If the Customer has turned on the AI app (section 11) or a user connects their own AI assistant (section 12), this data may be processed only to provide that user-facing feature; it goes to the assistant only at that user’s own instruction.
- We do not use this data to develop, improve or train generalised AI or machine-learning models, ours or anyone else’s, and we do not transfer it to anyone for that purpose.
- We transfer this data to others only on your instruction (for example, writing a record back to your Google account, a report sharing link your business creates, or a request your connected AI assistant makes on your behalf), for security purposes, or to comply with the law.
- Our staff can view this data only with your explicit consent, for security investigations, or where required by law.
You can revoke Google access at any time by removing the connection in the platform or from your Google Account permissions page.
7. Microsoft services
Microsoft connections are not available yet. The platform is built to support sign-in with Microsoft, Outlook calendar, Outlook contacts and picking files from OneDrive/SharePoint. When these connections are enabled, the same rules as for Google apply: permissions are requested only when you choose them, on Microsoft’s consent screen (openid, email, profile, User.Read, offline_access, Calendars.ReadWrite, Contacts.Read/Contacts.ReadWrite, Files.Read/Files.ReadWrite, and for the file picker OneDrive.ReadOnly or .default for the business’s SharePoint address), and are used only for the related feature. We do not request access to read your Outlook mailbox (Mail.Read).
8. E-mail archive and sending mailboxes
E-mail archive. If a business chooses, it keeps a read-only copy of its business e-mail and matches it to the related customer records. The business gets its own hard-to-guess archive address, and e-mails arrive there as copies sent from the business’s own mail server:
- Google Workspace: the business’s admin adds an “also deliver to” routing rule in the admin console.
- Microsoft 365: the business’s admin adds a journal rule.
- Other mail services: automatic forwarding from the mailbox to the archive address.
None of these require your e-mail password or access to your Google or Microsoft account. The archive is read-only: the platform never sends, deletes or changes e-mails from it. Before the archive address is created, the business confirms it has informed its employees. The archive is encrypted with a separate key for each business; an encrypted copy of the files is kept in our file storage in the EU. The archive is deleted according to the business’s retention setting.
Outreach sending mailboxes. In the Outreach app, a business connects mailboxes on its own domain with a username and app password (SMTP/IMAP). We send the business’s e-mails from these mailboxes and regularly read the mailbox inbox to detect replies and bounces. Mailbox passwords are stored encrypted.
9. Field app
The Field app helps a business manage the inspection rounds and work of its field team (its own staff or contractor teams). The Customer is the controller of this data.
- Sites and checkpoints: names of buildings, zones, checkpoints and equipment, and their QR codes; the customer and contractor company a site belongs to.
- Field users: people the business invites with the “field user” role see only the rounds and work assigned to them or their team; they cannot access customer records, the inbox or settings.
- Checklists: who completed which checklist, where and when, the answers, notes, photos and signatures. Photos are resized on the phone and stored in the business’s encrypted file storage.
- Location: off by default. If the business turns it on and the phone allows it, location is taken once, only at the moment a QR code is scanned or a checklist is submitted, and stored only with that submission. There is no continuous or background location tracking.
- Camera: the browser asks for camera permission to scan QR codes and take photos; QR codes are decoded on the phone and the camera image is not sent to us. Only the photos the person takes are uploaded.
- Work items: reported problems, who they are assigned to, their status, closing note and photo.
- Visitor reports: anyone can report a problem without signing in through a public page opened by a QR code on site. The page takes a description and up to 3 photos; name and contact details are optional and stored only if entered. To prevent abuse, the IP address is turned into a one-way hash and used for short-term rate limits.
- No biometrics: there is no sign-in or attendance by face recognition, fingerprint or similar means.
Field data is kept while the Customer’s account exists and is deleted with it. Photos never attached to a submission are deleted automatically after 1 day. A visitor who wants their report details deleted can contact the business or us.
10. Other services a Customer connects
A Customer can also connect other services with its own credentials, such as payments (iyzico), shipping (Geliver), SMS and messaging consent (Netgsm, İYS), cloud telephony (Verimor), e-invoicing and accounting (Nilvera, Paraşüt), marketplaces and e-commerce sites, Slack and Microsoft Teams notifications, enterprise sign-in (SAML/OIDC) and bot protection on its own web forms (Cloudflare Turnstile). Data is exchanged with these services on the Customer’s instructions and only to run that feature; credentials are stored encrypted. Those services’ own privacy terms also apply.
11. AI app
AI features are off by default. If a Customer’s admin turns on the app and accepts its notice, authorised users can press a button to get a summary of a conversation, a reply draft, a sales analysis or a quote draft. With a separate consent, the admin can also turn on automatic reading of conversations: new WhatsApp, Instagram and Messenger messages are then read after a short quiet period, voice messages are transcribed, and the resulting suggestions go to the Approvals screen. This setting is off by default. In every case:
- The conversation (WhatsApp, Instagram, Messenger or an e-mail in the business’s e-mail archive) is sent to our AI provider, Google’s Gemini service. E-mail addresses, phone numbers, IBANs, national ID and card numbers are masked before text is sent. The person’s name is not sent. Voice messages are sent as audio files to be transcribed.
- By default, AI suggestions are not written to records until a person approves them. The admin can separately choose certain suggestion types to be applied without waiting for approval; each one is written to the audit log.
- We use Google’s paid Gemini service. Google does not use the text sent or the responses to train its models or improve its products; it keeps these records for a limited time only to detect abuse. We do not use this data to train any AI model either.
- The (masked) text sent to the model and the response are kept for 90 days for audit, then deleted. A voice message’s transcript is kept with the message.
- Along with the conversation, short record details may be sent (for example the company name, sector or the stage of an open deal); these may have come from Google, Microsoft or Meta services the Customer has connected. They are processed only to provide the feature the Customer turned on; they are never sold, used for advertising or used to train models.
- Processing takes place on Google’s infrastructure and is not guaranteed to stay within the EU. This is shown to the Customer when the app is turned on.
12. Connecting your own AI assistant (MCP)
Any user of the platform can, if they choose, connect an AI assistant of their own choice (for example ChatGPT, Claude or Gemini) to their company’s data. The connection is made either on a consent screen in the platform where the user picks the company and permissions (OAuth), or with an access key the user creates; it is never turned on automatically.
- The assistant works with the permissions of the user who connected it and only with the permissions selected; it cannot see any record the user cannot see in the platform. Customer-data permissions (customer records, inbox, calendar) stay off unless selected.
- Connecting an assistant is entirely the user’s choice. The data the assistant asks for goes, on the user’s instruction, to the provider the user chose, under that provider’s terms. This data may include information synced from services the Customer has connected: for example Google Calendar events and busy times, contacts imported from Google Contacts, and records from Microsoft or Meta (WhatsApp, Instagram, Messenger).
- The relationship with that provider is the user’s or their company’s own. Whether the provider uses the data for model training depends on the user’s settings with that provider; we never give this data to anyone to train models, we do not sell it and we do not use it for advertising.
- Every call is logged, and changes made by the assistant can be undone for 30 days. The user can remove the connection at any time under Settings › Integrations › API › AI connection (MCP).
13. Advertising and marketing
A Customer’s own advertising. A Customer may use its own customers’ data for its own advertising through the platform’s integrations. For example, reporting a conversation that turned into a sale back to an ad network (Meta and Google conversion reporting), or sending its own customer list to Meta Ads or Google Ads as an audience. These transfers are not switched on yet; when they are, they work like this:
- The Customer is the controller for this processing. Having the legal basis and the required consent (KVKK, GDPR, İYS where relevant) is the Customer’s responsibility; we act only as processor on the Customer’s instruction.
- Only people with an ad-sharing consent on the Customer’s record are sent; for audiences, people marked “do not contact” are also left out. If a person withdraws consent, they are left out of later transfers. When, with which text and through which channel consent was given is kept on the record.
- Details such as e-mail and phone are turned into one-way hashes before they are sent to the ad network.
- Data received from Google APIs (for example contacts imported from Google Contacts) is not included in these transfers.
- The Customer must follow the ad network’s rules (Meta Business Tools Terms, Google Ads customer data policies).
For the Customer’s reports, the platform keeps ad click IDs and campaign tags (for example gclid, fbclid, utm) on the person’s record. The Customer’s web forms set no cookies for this; a form embedded on the Customer’s website keeps the landing page address only for that browser session.
Our own advertising and marketing. We do not use Customers’ data, or the data of their customers, for our own advertising or marketing, and we do not sell it. We never use data received from Google APIs for any advertising. We may send product news and marketing e-mails to people who use the platform, with their consent where required; every such e-mail has a one-click opt-out. We use no tracking or advertising cookies on our website or in the platform.
14. Who we share data with
We use the following service providers (sub-processors) to run the Service. Each can access only the data it needs for its task.
| Provider | Purpose | Data location |
|---|---|---|
| Hetzner Online GmbH | Server running the platform (database, e-mail archive, application) | Nuremberg, Germany (European Union) |
| Cloudflare, Inc. | Storing files uploaded to the platform and encrypted database backups (R2); domain name (DNS) service; hosting intordia.com | Files and backups in the EU; website traffic on Cloudflare’s global network |
| Google Ireland Ltd. / Google LLC | Gemini, if the Customer has turned on the AI app; our e-mail (Google Workspace): correspondence with you (info@intordia.com) and system e-mails (invitations, notifications — system@intordia.com) | Google infrastructure; not guaranteed to stay within the EU |
The platform also sends lookups that contain no or very limited personal data: only the first 5 characters of a password hash, to check whether your password appears in breach lists (Have I Been Pwned); tax or company number checks when you ask for them (EU VIES, UK HMRC and Companies House); and exchange rates (Central Bank of the Republic of Türkiye, European Central Bank). If you turn on browser notifications, they are delivered encrypted through your browser vendor’s push service (Google, Mozilla, Apple).
Beyond these, data may be transferred to services the Customer connects on its own instructions (Meta, Google, e-mail, payments, shipping, etc.), to an AI assistant a user connects (section 12), to ad networks for the Customer’s own advertising (section 13), to competent authorities where legally required, and to lawyers and courts in legal disputes. If our list of sub-processors changes, we will update this page.
15. International transfers
The platform’s servers are in Germany (European Union); some of the providers above are based in the United States, and Gemini processing may take place outside the EU. Personal data is therefore transferred outside Türkiye. These transfers rely on the appropriate safeguards provided in KVKK Article 9 (standard contracts) and, under the GDPR, on the European Commission’s standard contractual clauses. Signing the standard contracts with our providers and notifying the Turkish Personal Data Protection Authority is in progress; we will update this section when it is complete.
16. Retention
| Data | Period |
|---|---|
| User account | While the account exists. When you delete your account, your name, e-mail, photo, sign-in methods (password, Google, two-step verification), sessions, notification subscriptions and personal connections are deleted immediately. Business records you created belong to the business and stay with it under the name “Deleted user”; they cannot be linked back to you. |
| Customer data | While the Customer’s account exists. Customers can set automatic deletion between 30 days and 10 years for messages, the e-mail archive, activity logs and web form submissions; these settings are off by default. When a Customer asks to delete its account, all of its data, including the audit log, is permanently deleted after a 14-day grace period; only a record proving the deletion took place remains. |
| Login attempts | 180 days |
| Audit log | At least 365 days while the Customer’s account exists (Customers can extend it up to 10 years); deleted with the Customer’s account |
| AI request logs | 90 days |
| API and webhook delivery logs | 30 days |
| AI connection (MCP) call logs and notifications | The period the Customer sets for activity logs; if none is set, while the Customer’s account exists. Undo records 30 days. |
| Usage metrics | 25 months |
| Export files | 7 days |
| Quarantined e-mails | 30 days |
| Deleted files (trash) | 30 days |
| Field photos and visitor reports | While the Customer’s account exists; photos never attached to a submission 1 day |
| Backups | Encrypted daily backups 40 days, monthly backups 190 days; nightly backups on the server 14 days. Deleted data leaves the backups when these periods end. |
| Invoices and accounting records | As required by tax and commercial law (at least 5 years) |
When a person’s data is deleted, we keep an encrypted record proving the deletion took place, which does not directly identify the person.
17. Security
- All connections are encrypted (HTTPS/TLS).
- Access tokens and passwords for connected services are stored encrypted (AES-256-GCM).
- The e-mail archive and uploaded files are encrypted with a separate key for each Customer.
- Each Customer’s data is separated from other Customers at database level; one Customer cannot see another’s data.
- Passwords are stored as one-way hashes, and known breached passwords are rejected. Two-step verification is supported.
- Important actions are written to a tamper-evident audit log.
- We access a Customer’s data only at the Customer’s request for support, for security investigations or where required by law, and only as much as needed.
- Database backups are encrypted and stored in a separate location in the EU, and restores are tested regularly.
No system is perfectly secure. If a personal data breach occurs, we will notify the competent authority and affected people or Customers within the time limits required by KVKK and the GDPR.
18. Cookies
intordia.com uses no cookies. intordia.app uses only strictly necessary cookies and cookies that remember choices you make; we do not use analytics, advertising or tracking cookies, so no cookie consent is requested.
| Cookie | Purpose | Duration |
|---|---|---|
__Secure-better-auth.session_token | Keeps you signed in | 30 days if “remember me” is chosen (renewed while you use it); otherwise until the browser closes |
__Secure-better-auth.dont_remember | Marks that “remember me” was not chosen | Until the browser closes |
__Secure-better-auth.state, __Secure-better-auth.relay_state | Confirms that a Google or enterprise (SSO) sign-in is a request you started | 5 minutes |
__Secure-better-auth.two_factor, __Secure-better-auth.trust_device | Completes two-step sign-in; remembers “trust this device” | 10 minutes / 30 days |
__Secure-better-auth.better-auth-passkey | One-time check during passkey sign-in | 5 minutes |
predator_fb_pages | Completes the page selection step when connecting a Facebook Page (encrypted) | 15 minutes |
NEXT_LOCALE, ui_look, predator-acik-menuler, predator_firmasiz | Language, appearance and menu preferences; the “continue without a company” choice | 1 year |
Your browser’s local storage also keeps preferences such as theme, screen settings and unsaved drafts; these are not sent to our servers. In the Field app, checklists filled in while offline wait on the phone until the connection returns.
19. Your rights
Under KVKK Article 11 you have the right to learn whether your personal data is processed and to request information about it; to learn the purpose of processing and whether it is used accordingly; to know the third parties in Türkiye or abroad to whom it is transferred; to request correction of incomplete or inaccurate data; to request deletion or destruction when the conditions of KVKK Article 7 are met, and to have these actions notified to third parties; to object to an outcome against you resulting solely from automated analysis; and to claim compensation for damage caused by unlawful processing.
If the GDPR applies to you, you also have the rights of access, rectification, erasure, restriction, data portability and objection.
How to make a request: e-mail info@intordia.com from the address registered to your account. We may ask for additional information to verify your identity. We will respond free of charge within 30 days at the latest. You can also delete your account or your company account inside the platform.
If you are not satisfied with our response, you can complain to the Turkish Personal Data Protection Board (KVKK) or, if you live in the EU, to the data protection authority of your country.
20. Children
The Service is designed for businesses and is not directed at anyone under 18. If we learn that someone under 18 has opened an account, we will close it.
21. Changes
We update this policy when the Service or the law changes. The current version is always on this page; we announce important changes inside the platform or by e-mail.