1. Who is who
The data controller is the company using the Solk installation (for example, the employer who invited you): it decides what data is entered, who can access it and how long it is kept. Solk is the data processor that hosts the data and operates the software on that company's instructions. Turkish Law No. 6698 on the Protection of Personal Data (KVKK) and, where applicable, the GDPR follow this distinction.
Your user account is created by your company's administrator, not by Solk. There is no sign-up or membership on Solk's website (solk.app).
2. Data we process
| Data | Source | Examples |
|---|---|---|
| User account | Your company's administrator | name, username, e-mail, role, assigned modules, password hash (the password itself is not stored) |
| CRM records | Entered by you and your team | customer company details; contacts' names, titles, phone numbers and e-mail addresses; visit, call and trial notes; quotes, orders, contracts and support tickets; files attached to records (data sheets, photos, signed documents); calendar events; trade-fair leads |
| Call recordings | If the Call Recording module is enabled, when a user starts a recording | the audio file of the meeting or call (video too for the meeting bot), the transcript and speaker names; if AI is turned on, the summary, sections and suggested action items. Recordings are stored in your company's installation and deleted according to the installation's retention setting |
| Usage records | System | sign-in time and IP address (security), audit trail of deletions and blocked edit attempts, which user used which module (licence metering) |
| Visit location | If turned on in your workspace; only at "I'm here" and when an on-site visit is saved (with the browser's permission on the web, the app's on the phone) | latitude, longitude, accuracy and time; the distance to the company and the visit duration calculated from them; the reason picked when no location was left. No all-day tracking; only the person who logged the visit and admins see the coordinates (details: section 5) |
| Calendar sync | Optional | if you add a calendar account on your iPhone / Mac, CRM events appear on your phone and events you create on the phone are brought into the CRM |
| E-mail sync | Optional, connected by the user | if you connect your mailbox (with an IMAP/SMTP app password, or by granting access with your Google / Microsoft account), only your two-way correspondence with contacts in the CRM, with customer companies' domains or with business addresses (sender, recipients, subject, date, body) is brought into the CRM; public webmail addresses (Gmail, Hotmail, etc.), newsletters, auto-replies, delivery reports and addresses your company has excluded are not stored, and your other e-mails are read and discarded. You choose whether the body is shared with your team; you can remove the connection at any time. Section 7 describes Google user data in detail |
| Automatic company and contact records from e-mail | Turned on or off by your company's administrator (on by default) | when there is two-way correspondence with an unknown business domain (at least one e-mail sent from you to that domain), the company is created as a "prospect" and the correspondent as a contact: name, e-mail address, and the title, phone number and company name from the e-mail signature. For this, the number of incoming / outgoing messages per address is kept (not the content). Generic addresses (info@, sales@ …), public and educational institutions, banks, couriers and software services are never created as companies or contacts. A wrongly created company can be deactivated with one click and its domain excluded for good |
| E-mail sequences, scheduled and bulk sending | The user | recipient's name and e-mail address, which step was sent when, whether a reply arrived or the recipient unsubscribed; drafts waiting to be sent and their attachments |
| Trial sign-up and billing details | The solk.app "Start free" form and the plan selection in your installation | name, work email, company, phone and the requested installation address (to open the trial installation and contact you); billing name, tax office and tax number (national ID number for individual invoices), billing address, billing email and phone; subscription and payment history (plan, seats, amount, date) |
| Ask Solk (assistant) questions | The user | the question you asked, a summary of the answer and the records linked in it (for chat history and usage limits) |
| Digital business card | Published by the user (off by default) | the details you choose to show on the card: name, company and optionally photo, title, department, e-mail, phone, mobile, website, address (hidden by default), about. Anyone who has a published card's link or QR code can see it. How often the card was viewed, saved to contacts, had details left on it or was added to a wallet is kept as a daily count per card; these counters store no visitor identity, IP address or device (to avoid counting the same visitor twice and to limit form attempts, the IP address is held only temporarily in server memory and is not written to the database) |
| Details left on a business card | The visitor who scans the card, voluntarily (the "Leave your details" form) | full name, company, e-mail, phone and note; the date and time the consent box was ticked and the IP address (in the prospect company's note, as evidence of consent). The details are saved in the CRM of the workspace the card belongs to as a prospect company and contact (as a fair lead while a fair is running), and a task is opened for the card owner. The controller for this data is the company that owns that workspace; the visitor sends deletion requests to the address given in the form or to that company |
Solk does not ask for or store card details, location history or your phone's contacts; card details are entered directly on the page of the payment institution iyzico. A national ID number is requested only as billing information when an individual invoice is needed. Your company decides what is written in free-text fields and sets guidance to avoid entering sensitive data.
3. What it is used for
- Sales tracking: keeping company, contact, visit, opportunity, quote and order records; generating reminders and tasks.
- Management: team dashboard, forecasts and reports (only on your company's own data).
- Security and accountability: sign-in checks, lockout after failed password attempts, audit trail.
- Linking e-mail correspondence to the right records: conversations are linked to the company and project, and to quotes, contracts, visits and similar records through the quote / contract / record number in the subject or body; recent visits and tasks are only shown as suggestions and are not linked without the user's confirmation.
- Licensing and billing: how many user-days each module was used — counts only, never record content.
- Digital business card: letting users share their own contact details, and getting back to people who voluntarily leave their details after scanning a card.
- E-mail sequences: sending follow-up e-mails started by the user on time; sending stops automatically when the recipient replies, unsubscribes or a meeting with the company is logged. Every sequence e-mail contains a one-click unsubscribe link. Sending in line with commercial electronic message law (Law No. 6563, İYS) and obtaining the required consents is the responsibility of the data controller company.
No profiling, ad targeting or third-party analytics is performed. The website and app use no tracking cookies; only the essential cookie that keeps you signed in is used.
4. Where it is stored
Each company's installation runs on its own subdomain with its own database; no tables are shared with another company. Data is kept on servers managed by Solk and backed up daily; backups are also per company. Data in transit is always encrypted (HTTPS; .app domains do not open without encryption).
The server location and any cross-border transfer terms are set out in the service agreement with your company; you can ask for details at info@solk.app.
5. Mobile app (iOS / Android)
The Solk mobile app is a client that connects to your company's installation (the address you enter on the sign-in screen). The app itself collects no data; everything you see comes from your installation.
- Stored on the device: the sign-in token, in the device's secure storage; the server address; a copy of the most recently viewed lists so screens open instantly (in the app's data, removed when you sign out). Your password is not stored on the device.
- Microphone (Call Recording module only): permission is requested only the first time you start "Record conversation"; audio is recorded only between your start and stop, uploaded to your installation's server (transcript and summary are prepared as described in section 6) and the temporary file on the device is deleted after upload. The app never records in the background or on its own.
- Phone notifications (optional): notification permission is requested only if you accept the app's "Shall we notify your phone about important updates?" prompt. If you allow it, the device's notification token (Firebase Cloud Messaging) is registered with the workspaces you are signed in to and used only to send you notifications. A notification consists of a short title and text (e.g. "Ayşe mentioned you: …", "A task was assigned to you: …", the subject of an e-mail from a customer); it is delivered to your device through Solk's relay server and Google Firebase Cloud Messaging (on iOS also the Apple Push Notification service), and the relay server does not store the content. You choose which types arrive and quiet hours in Menu › Phone notifications, and you can turn notifications off there or in your phone's settings; signing out deactivates the device.
- Camera and photos — business card reading (Advanced / Enterprise): permission is requested only when you tap "Business card" and take or pick a photo. The text on the card is read on the phone (Apple Vision on iPhone, Google ML Kit on Android); only the recognised text goes to your installation, where it is split into fields such as name, title, company, phone and e-mail. If AI is turned on for your company, this text (not the image) is sent to the AI service provider in section 6 for correction. The card photo is added to the company's files only while "Add the card photo to the company" is on (the default).
- QR code reading (Advanced / Enterprise): QR, Aztec, PDF417 and Data Matrix codes in a business card photo, and the code in the "Scan QR code" scanner, are decoded on the phone (Apple Vision / VisionKit on iPhone, Google ML Kit and the Google code scanner on Android). Only the code's content (text) goes to your installation, where it is split into fields such as name, title, company, phone and e-mail. If the code holds a web address, your installation's server opens that page to read the contact details (internal network addresses are never contacted); if AI is turned on for your company, the page text may be sent to the AI service provider in section 6 for correction. On iPhone the live scanner asks for camera permission the first time. On Android the Google code scanner opens the camera inside Google Play services; the Solk app needs no camera permission for it and receives only the decoded content.
- Location — visit location (if turned on in your workspace): location permission ("While using the app") is requested only when you tap "I'm here" at a company or save an on-site visit, and the location is taken at these two moments only. There is no all-day tracking, background location or route recording. The point taken (latitude, longitude, accuracy) and the time go to your installation's server, where the distance to the company and the visit duration are calculated. Only the person who logged the visit and your workspace's admins see the coordinates and the duration. At a company with no known location, the first point with good accuracy may be saved as the company's location. A workspace admin can turn visit location off, make it optional or required for face-to-face visits; when required and you can't leave a location, you pick a reason.
- Profile photo (optional): camera / photo access is requested only when you tap "Take photo" or "Choose from photos" in Profile. The photo is cropped square, downsized (256 pixels) and uploaded only to your workspace's server; users in your workspace see it as your avatar on the web and in the app. You can remove it at any time; removing it deletes it from the server.
- Sharing from the phone (Advanced / Enterprise): when you choose "Share → Solk" in another app, the shared files and text are kept temporarily on the device; they are uploaded to your installation when you pick a record and tap "Save", then removed from the device; if you cancel they are removed without upload. Solk never accesses other apps' content on its own.
- Caller ID (optional — Advanced / Enterprise): if you turn on "Caller ID", the phone numbers and names (company · contact) of CRM companies and contacts you can see are loaded onto the device; an incoming call's number is matched against this list on the device (Call Blocking & Identification on iPhone, the caller ID app role on Android). Incoming call details (caller number, time) are not sent to Solk or any third party and are not stored. The list is updated daily and removed from the device when you turn it off, sign out or your company's administrator disables the feature. Contacts and call log permissions are not requested.
- Widgets, controls and Siri (iPhone): for the home and lock screen widgets a short summary — overdue / today's task and meeting counts, the titles of up to 4 tasks, your name, the workspace name and your business card link — is kept in the app's shared container on the device (App Group); the widget reads it only from there. Siri, Shortcuts, Spotlight and Control Center controls only open Solk on the relevant screen and carry no data. This summary is not sent separately to Solk or Apple and is removed when you sign out.
- Show in Contacts (optional — iOS 18, Advanced / Enterprise): if you turn it on, the company and contact names and phone numbers from the caller ID list are written to the app's shared container on the device and handed to the iOS Contacts app as a separate "Solk" list; incoming calls show the name and company. The list is not copied into your personal contacts and Solk does not read your contacts; iOS may ask for confirmation to add the list. Turning it off or deleting the app removes the list from the phone.
- Permissions not requested: location, contacts and call log are not requested. The "Call", "WhatsApp" and "Directions" buttons pass the number or address to the relevant app only when you tap them.
- E-mail and Ask Solk: e-mails you write in the app are sent through your installation from the e-mail account you connected on the web, and saved in the CRM (section 2). Questions on the "Ask Solk" screen go to your installation; if AI is turned on, the answer is prepared as described in section 6. The app never sees or stores your e-mail account's password or access token.
- Third-party SDKs: Firebase Cloud Messaging (to deliver notifications) and, on Android, Google ML Kit text recognition and barcode scanning and the Google code scanner (read business card text and QR codes on the device; neither the image nor the decoded content is sent to Google, and ML Kit and Google Play services may send anonymous usage and diagnostic information to improve the service). There is no analytics, crash-reporting or advertising library.
- Sign-out: signing out revokes the token on the server; tokens also expire automatically after at most 90 days.
- Account deletion: because your account was created by your company, send your request to close it to your company's administrator, who can deactivate or delete the user. If you cannot reach them, write to info@solk.app; we will forward the request to your company and follow it up.
6. Who it is shared with
- Your company's users: according to their permissions (sales users edit their own records, administrators see everything).
- Solk: only for operations and support, when needed and with your company's knowledge; only licence status and usage counts go to the vendor panel.
- Infrastructure providers: server hosting and, if your company has configured one, an e-mail delivery service. They process data only on Solk's instructions.
- The digital business card's public page — if you published your card: the details you chose to show (including the photo) are open to anyone who has the link or QR code; the page is closed to search engines. You can unpublish the card or renew the link at any time (the old link and QR codes stop working); your company's administrator can turn business cards off entirely. The page loads no external resources (fonts, analytics, ads); only an essential session cookie is used for form security.
- Apple Wallet and Google Wallet — if the card is added to a wallet: the card's visible details, its link and (when visible) the photo are added to the Apple Wallet, or the Google Wallet in the Google account, of the person who adds it. The Apple Wallet pass is signed on Solk's relay server; only hash values of the pass files reach the relay, not their content. To keep the pass current, the wallet device identifier and notification token of the device that added it are stored in the card's workspace; update notifications are sent as an empty notification through Solk's relay server and the Apple Push Notification service. The registration is deleted when the pass is removed from the wallet or Apple reports that the device is no longer registered. For Google Wallet, the card details go to the relay server to sign the "Save to Google Wallet" link; the browser of the person adding the card is then redirected to Google with that signed link. The relay server does not store wallet content; it keeps only call counts (and any error message) for 30 days. A card saved to Google Wallet is subject to Google's own terms.
- Map images (web): when the Visits map, the small map on a visit's detail or the company location window opens: if the workspace uses Google Maps, your browser loads the map from Google (Maps JavaScript API) — Google sees your IP address, browser details and the area viewed, and the Google Privacy Policy applies; otherwise the map library (Leaflet) comes from cdnjs and the images from OpenStreetMap's servers, which see only your IP address and the area viewed. The visit points shown on the map come from the Solk server; no record data is sent to the map provider. The mobile app has no in-app map; "Open in Maps" opens the location in your phone's maps app.
- Location from a company's address (server): when a visit distance is calculated for a company with no saved location, the company's address and city text is sent to be turned into coordinates: to the Google Geocoding API if Google Maps is selected (through the Solk panel with Solk's account, or with the workspace's own Google key), otherwise to OpenStreetMap Nominatim. This is a business address; no personal data, visit data or your location is sent. Coordinates from Google are kept for at most 30 days (Google's terms; only the place ID remains); OpenStreetMap results are kept until the address changes.
- Notification delivery — if you turned on phone notifications: the notification's title, short text and the device token go to Google (Firebase Cloud Messaging) and, on iOS, to Apple (Apple Push Notification service) for delivery. These services process the data only to deliver the notification to your device; your CRM records are not shared.
- Your own e-mail provider: if you connected your e-mail account, e-mails you write in the CRM are sent from your own account (Gmail, Yandex, Outlook or your company mail). If you connected with "Sign in with Google" or "Sign in with Microsoft", Google / Microsoft grant your Solk installation only the mailbox access (read and send) you approved; your password never reaches Solk. You can revoke this access at any time from your Google account's Security → Third-party connections page or your Microsoft account's Apps and services page. Details for Google accounts are in section 7.
- AI assistant — optional, off by default: the "Assistant" on the opportunity page normally runs rule-based on the server and no data leaves it. If your company's administrator turns on AI text in the Security settings, when a user opens the Assistant only the CRM summary of that opportunity and company (stage, amount, recent activities, notes; excluding contacts' phone numbers and e-mail addresses) is sent to the AI service provider to generate the answer. With the same setting on, using "draft from description" on the workflow screen sends only the description you wrote and the field list. When you ask a question in the Ask Solk panel (Ctrl+J), the question and the CRM record summaries needed to answer it (name, stage, amount, date, meeting notes, e-mail subjects; excluding contacts' phone numbers and e-mail addresses) are sent; the AI can access only data within your own permissions. With the setting off, Ask Solk answers rule-based on the server and no data leaves it. Depending on the model the user picks, the answer is generated by Anthropic (Claude), OpenAI (GPT) or Google (Gemini); these providers are Solk's sub-processors, do not use data under their paid API terms for model training, and their servers are outside Turkey (mainly in the USA). AI requests are forwarded to the provider through Solk's relay server (the vendor panel); the relay does not store request or response content and only keeps the company's monthly request and token counts per model (for billing and limits). If your company's administrator enters its own API key, requests go directly from the installation to that provider without passing through Solk's relay; in that case the agreement and data processing terms are between your company and the provider. The setting can be turned off at any time.
- Call recording — if the Call Recording module is enabled: the audio file is sent for transcription to Solk's transcription server (with Deepgram as a fallback if it is unreachable); the note-taker bot that joins meetings connects from Solk's bot server (fallback: Recall.ai). If AI is turned on, the transcript is sent to the AI provider for the summary and action items. These providers process the data only for this purpose; recordings are kept in your installation.
- Payment institution (iyzico): for plan subscriptions and invoice payments, name, email, phone, billing address and ID / tax number are sent to iyzico so it can process the payment. iyzico collects and stores card details directly; they never reach Solk. Your CRM records are not shared with iyzico.
- Legal obligation: upon a lawful request from competent authorities.
Data is never sold, rented or shared for advertising.
7. Signing in with Google (Google user data)
This section describes the data received from Google when a user connects a Gmail or Google Workspace account with "Sign in with Google" on the E-mail account page. Connecting is optional; if a user does not connect, no data in their Google account is accessed.
| Permission requested | Why |
|---|---|
| openid email | To learn the e-mail address of the connected Google account and match the mailbox to the right address. |
| https://mail.google.com/ | To connect to Gmail over IMAP and SMTP: read incoming and sent correspondence and save the messages that match contacts and companies in the CRM, and send e-mails the user writes in the CRM from their own Gmail account. Gmail grants IMAP / SMTP access only with this permission. |
- Data accessed: the account's e-mail address; the headers (sender, recipients, subject, date, message ID) and body of messages in the Inbox and Sent folders. Attachments are not downloaded. On first connection, the app looks back over the period the user chooses (by default, the last 30 days).
- How it is used: only for user-facing CRM features: linking two-way correspondence with contacts and customer companies in the CRM to the related company, project and records (sections 2 and 3); where the company leaves the setting on, creating a prospect company and contact from two-way correspondence with a new business domain; and sending the e-mails the user writes in the CRM. Messages that do not match the CRM are read and discarded without being stored.
- Sharing: the data is kept only in the Solk installation belonging to the user's company. Depending on the user's choice, teammates see either the full message or only its subject and participants. Data received from Google is not sold, not used for advertising, and not transferred to data brokers or other apps. If the AI feature turned on by the company is used (off by default, section 6), the record summary needed to answer a user's question may include only an e-mail's subject and date; message bodies and e-mail addresses are never sent. This summary is sent only to generate that answer and is not used by the provider to train models.
- Human access: Solk staff do not read e-mail content received from Google. The only exceptions are: with the user's explicit consent for specific messages (for example, in a support request); for security purposes (investigating abuse or a vulnerability); to comply with applicable law; and for internal operations using aggregated, de-identified statistics.
- No AI training: data received from Google is not used to develop, improve or train generalised artificial intelligence or machine-learning models.
- Protection: Google access and refresh tokens are stored encrypted on the server, used only for syncing and sending, and never sent to the user's browser or the mobile app. All connections are encrypted with TLS. Each company's installation runs on a separate database, and access is limited by role, module and record permissions (section 10).
- Retention and deletion: correspondence saved in the CRM becomes part of the company's records and is kept for as long as the installation exists. When the user clicks "Remove connection" on the E-mail account page, the Google access and refresh tokens are deleted from the installation immediately and no new data is fetched. You can also revoke access from your Google account's Third-party connections page. You can ask your company's administrator or info@solk.app to delete correspondence saved in the CRM: the request is fulfilled within 30 days, and deleted data drops out of backups within 60 days at the latest. When the company's agreement ends, the installation and its backups are deleted as described in section 8.
8. How long it is kept
Records are kept for as long as your company's installation exists; customer company records are not deleted but deactivated (history is preserved), and permanent deletion is done only by an administrator, after a backup. When the agreement ends, your company can export its data within 30 days; the installation is then deleted, and the archive backup taken before deletion is destroyed within 90 days at the latest. For a trial installation, if no plan is chosen the data is kept for 30 days after the trial ends; the installation, calendar data and sign-up record are then permanently deleted without an archive backup, and the administrator is e-mailed 3 days before deletion. Security records (sign-ins, IP addresses) are kept for a limited, reasonable period. E-mail addresses that have unsubscribed are kept on a "do not send" list for as long as the installation exists, so they are not sent sequence e-mails again.
9. Your rights
Under Article 11 of KVKK you have the right to learn whether your data is processed, request information, learn whether it is used for its intended purpose, request correction if it is incomplete or inaccurate, request its deletion or destruction, object, and claim compensation if you suffer damage. Because your company is the data controller, you should first apply to your company; Solk technically assists your company in responding. You can also write to us and we will forward the request to the company concerned.
10. Security
- TLS in transit; passwords stored as one-way hashes; temporary lockout after repeated failed sign-ins.
- A separate database and backups per installation; permission-based access (role + module + record ownership). If your company's administrator chooses team visibility, a sales user sees only their own customer records, those of colleagues in the same department, and companies without an assigned owner; this restriction applies equally on the web, in the mobile app, in reports and in the AI assistant.
- All deletions and blocked edit attempts are recorded in the audit trail.
- Optional two-step verification (authenticator-app code, on web and mobile) and access restricted to IP addresses set by the company.
- Files attached to records are served only to authorised users through a session- and permission-checked address; no public links are created.
- Mobile tokens are stored only as hashes and are valid for a limited time.
- Digital business card links carry an unguessable random token; hidden fields are never served from any public address (page, vCard, QR, wallet pass); the profile photo is served from the card's address only if the user chooses to show it. The "Leave your details" form is protected by a trap field, a signed timestamp and hourly / daily submission limits; the Apple Wallet web service requires a separate authorisation token for each card.
- The connected mailbox's app password or Google / Microsoft access tokens are stored encrypted on the server and used only for syncing and sending; when the mail server's certificate cannot be verified, the connection is made only to a certificate the user has explicitly trusted. Unsubscribe links are signed (nobody can unsubscribe on someone else's behalf); team invitation links are single-use, expire after 7 days and are stored only as hashes.
11. Children
Solk is a business application and is not intended for anyone under 18; we do not knowingly collect data from children.
12. Changes
When this policy changes, the effective date and version number are updated, and material changes are also announced to installation administrators. The current version is always at solk.app/en/privacy.html; the Turkish version at solk.app/gizlilik.html prevails in case of a discrepancy.