keep up the conversation
Privacy.
Cards are recognised on your device. You choose what to save to Contacts, connect to calendar services or share.
Who is responsible and how to contact us
kutc is provided by Summit Vision Media GmbH. For privacy questions or requests about your rights, contact hello@summitvisionmedia.ch.
Längimoosstrasse 17
3075 Rüfenacht
Schweiz
Cards, contacts and your archive
The app processes card images you capture or select, recognised text and contact details derived from it, such as a name, company, telephone number, email address, postal address, website and profile links. It also processes details you add: lists, the date and place you met, and personal notes. Places are entered manually; kutc does not request location access.
Text recognition uses Apple Vision on your device. Suggested portrait crops are also processed locally: if exactly one face is found across the captured pages, kutc can crop a separate contact photo. This does not identify the person. You can choose a different photo. Card images, recognised text, contact drafts and additional details are stored in the app's archive on your device. Image files may be reoriented or compressed.
You do not need a kutc account for these features. The app does not operate its own upload service for your cards or address book. It contains no advertising, tracking or analytics SDKs.
Your own digital business cards
You can store several of your own cards on your device, with contact details, a private role label and an optional photo or logo. If you capture your own paper card with the camera or import a photo, Apple Vision recognises its text locally. The images are stored with your own card. You review the details before saving. This does not read contacts from your address book.
The displayed QR code contains the contact details as a contact file directly in the code, without a photo, logo or scan images. It does not link to a public profile website. Sharing a VCF file passes your entered contact details and any separate photo or logo to the app or recipient you choose. Private role labels, encounter notes and scan images are not included. Someone who scans the code or receives the file can save and forward its contents. Changes to your local card do not update copies you have already shared.
Contacts, Photos and Camera access
The camera is used for captures only with your permission. When importing photos, kutc receives the images you select in Apple's photo picker; it does not request blanket access to your photo library.
With your Contacts permission, kutc compares phone numbers and email addresses against accessible contacts to find existing entries. You choose whether to save a new contact or add to an existing one. Reviewed contact details and, where applicable, the separate contact photo are saved. In this version, personal encounter notes remain in the kutc archive. Contacts may be synchronised by your configured address book account, such as iCloud or another provider.
Dictating notes
kutc's own dictation feature requests microphone and speech recognition permission. It uses Apple's Speech framework with on-device processing required. If your device cannot process the selected language locally, this feature does not start; it does not fall back to server-based recognition. Audio is processed during dictation and is not saved by kutc as an audio file. Recognised note text becomes part of your archive.
If you instead use dictation in the system keyboard, Apple's own features, settings and privacy information apply. That keyboard feature is not controlled by kutc's requirement for local dictation.
Calendars and reminders
You can create an event in Apple's calendar editor or ask kutc to save a reminder. The details you confirm, such as a title, date, time and any existing meeting link, are passed to the system. Reminder text may include the person's name, the date you met and assigned lists. Personal encounter notes are not automatically attached to these events or reminders.
Entries are stored in the calendar you choose or your default reminders list. These accounts may synchronise data with Apple, Google or other configured providers. Necessary system permissions are requested when you use the feature. kutc does not upload your complete calendar or reminder history to its own servers. The additional, optional direct Google connection is described below. Microsoft/Teams is disabled in the store build.
Editing and reconciling follow-ups
With automatic reconciliation enabled, kutc checks locally linked events and reminders while the app is in use. Changes to titles, dates or duration and confirmed deletions are reflected in the local follow-up; the contact card is retained. Network failures and denied permissions are not treated as deletions. You can disable reconciliation in Settings.
Device calendar reconciliation and editing request full Calendar access; Reminders require read access. Saved identifiers are used. For legacy events without an identifier, you can explicitly link an event from a local list covering 30 days before and after the planned date. This calendar data is not sent to kutc servers. Without read access, the separate system editor remains available to add an event.
After confirmation, you can edit, reschedule or delete a linked Google event in kutc. The known event ID and, for edits, the title and start/end times are sent to Google. Google may notify invited guests of changes or cancellations. Editing preserves an existing Meet link. Remove only from kutc clears the local link instead, leaving the calendar event intact.
Optional morning summary and notifications
The morning summary is off by default. If you enable it, kutc asks for notification permission and schedules summaries on your device at your chosen time. The app uses follow-up plans saved in your kutc archive for this. When calendar reconciliation is enabled, saved plans are updated from linked events while the app is in use. The morning summary sends no data to a notification server operated by kutc.
A notification may include the number of follow-ups, names or company names, and times. Personal notes, email addresses and phone numbers are not used for it. Notifications may be visible on the lock screen depending on your system settings. You can change the time; turning the feature off removes kutc’s scheduled and already delivered summary notifications. Calendar reminders are managed separately.
Profile searches, links and sharing
kutc recognises supported profile links from card details locally. Only when you tap an additional profile search does it open a Google search for the person's name and, where applicable, company, restricted to the selected platform. Those search terms are then sent to Google. Opening a link passes the request to your chosen browser or the relevant platform. There is no automatic background search, connection request or follow action.
The share sheet lets you pass selected card images, a VCF contact file or an ICS event suggestion to an app or person. The receiving app handles those contents according to its own policies. Sharing an ICS event suggestion does not automatically send an invitation.
Storage, deletion and backups
Archive entries and your own digital business cards, including scan images, remain on the device until you delete them or remove the app together with its data. This does not delete entries already saved to Contacts or Calendar; manage those in their respective apps or through the separate, confirmed Delete follow-up action in kutc. Depending on your system settings, app data may be included in device or iCloud backups. kutc does not provide its own cloud synchronisation for the archive. You may need to delete exports and backups separately. Storage and transfers through your chosen system accounts depend on their settings.
You can change permissions in your device settings at any time. A feature may be unavailable without its permission; other features can remain available.
Support and this website
If you email us, we receive your email address, message and any attachments you choose to send. We use them to handle your request and retain them only as long as necessary for that purpose or to meet legal obligations. Please avoid sending unnecessary personal information about other people.
The kutc website plugin adds no cookies, analytics tools, third-party fonts or tracking pixels. Other parts of this WordPress website may use their own services or cookies. Loading a page necessarily transmits connection data, such as an IP address and browser information, to the hosting provider.
Hosting and technical infrastructure are provided by Infomaniak Network SA. Page requests may be recorded in server logs, including IP address, browser, operating system, requested page, access time and referrer, to maintain secure and stable operation. Further information about cookies, analytics and marketing services is available in our general website privacy notice: https://www.summitvisionmedia.ch/datenschutzerklaerung/
Your questions and rights
You can use the app's editing, export and deletion features for locally stored app data. Summit Vision Media GmbH cannot remotely access or delete your local archive. For personal data we receive, for example through a support request, you may ask us for access, correction or deletion and exercise other applicable privacy rights. Contact the email address above. You may also raise privacy concerns with the relevant supervisory authority.
Addendum: direct Google connection
This section applies to optional Google connectivity in the prepared first store build and prerelease versions. The feature is optional. Public approval and a release date have not yet been confirmed.
Access and use
Only when you choose to connect Google does kutc open Google's sign-in. You enter credentials with Google; kutc receives access tokens, not your Google password. The calendar.events.owned permission allows access to events in calendars you own. kutc uses it only for follow-up events you confirm in your primary Google Calendar. It does not search other or existing calendars or retrieve general event lists.
After your explicit send confirmation, kutc sends the meeting title, start and end times, the email address of exactly one invitee, your selected reminder lead time and technical operation identifiers to the Google Calendar API. Google creates the event, sends the invitation and processes the request for a Google Meet link. kutc retrieves only events whose operation identifiers are already known locally, to resolve an interrupted save, retrieve the Meet link and reconcile changes or deletions while the app is in use. It processes the event ID, status, title, times, version identifiers, calendar/Meet links and technical association data returned for those events.
Card images, portraits, the complete recognised card text, your address book and personal encounter notes are not sent to Google. This feature requests no access to Google Contacts, Drive or your general calendar history.
Recipients and sharing of Google user data
Google, as the provider of Google Calendar and Google Meet, receives sign-in information and API requests. Google processes and stores the data according to its terms and your account settings. The invitee you explicitly confirm receives the associated event information and, where available, the Meet link through Google. Other people may see data where you share your calendar or event with them or where your Google Workspace organisation has configured relevant access.
kutc does not transmit user data received from Google APIs to Summit Vision Media GmbH's own servers, the website host, advertising networks, data brokers or analytics providers. Summit Vision Media GmbH has no automatic remote access to that data. It is not sold or used for advertising, credit assessment or training general-purpose AI/ML models. If you voluntarily include data in a support email to us or share a link using another app, the recipient you choose receives it; this is not done automatically by the Google integration.
See Google's Privacy Policy. kutc's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Protection of sensitive data
Communication with Google's sign-in, token and Calendar services uses HTTPS with TLS encryption in transit. Sign-in uses OAuth 2.0 with PKCE, a random state value and validation of the redirect address. The API connection uses no persistent HTTP cache and does not forward access tokens to redirect destinations.
Access and refresh tokens are stored in the encrypted iOS Keychain, accessible only while the device is unlocked. They are not synchronised through iCloud Keychain or transferred to other devices. Local archive files containing follow-up data use Apple's file protection and the app sandbox. Archive files may remain accessible to the app after the first unlock following a device restart; this is not an additional app-specific password lock. Your device passcode, operating system and backup settings form part of this protection.
Storage, disconnecting and deletion
kutc keeps tokens locally until you disconnect or need to sign in again. Your follow-up, operation/event ID, status and available meeting links remain in the local contact archive until you delete the entry. Depending on system settings, those archive files may be included in device or iCloud backups; device-bound tokens do not transfer to another device.
Disconnecting in kutc removes the local Google connection and its tokens. Events already stored at Google and invitations already sent remain. You can additionally revoke Google's access permission under Connections in your Google Account. Manage events, calendar sharing and recipients' copies separately. Delete local archive entries and any exports or backups separately as needed.
Addendum: direct Microsoft connection
The optional Microsoft/Teams connection is a development feature and is disabled in the public base release currently being prepared. It supports work and school accounts with a suitable Exchange calendar and Teams entitlement. Personal Outlook/Hotmail accounts are not supported by this implementation.
After you sign in with Microsoft and consent, kutc uses the delegated Calendars.ReadWrite permission plus openid, email and offline_access. It processes a stable account identifier, an email address if Microsoft supplies one, access tokens and the default calendar's Teams capability. After your explicit send confirmation, it sends the title, times, exactly one invitee address, reminder lead time and a technical operation identifier to Microsoft Graph to create an event with a Teams meeting request. Known event IDs and links are stored locally. The address book, card images and personal encounter notes are not transmitted.
Recipients are Microsoft and your chosen invitee; organisational policies and calendar sharing may give others access. kutc does not transmit this API data to its own servers, advertising or analytics providers. HTTPS/TLS, OAuth with PKCE and device-bound Keychain storage protect transport and tokens. Disconnecting removes local tokens; technical operation records may remain on the device to prevent duplicate invitations. Existing invitations and external events remain. Manage access permissions additionally with Microsoft or your organisation. See Microsoft's Privacy Statement.