Privacy.

Who is responsible and how to contact us

metat is provided by Summit Vision Media GmbH. For privacy questions or requests about your rights, contact metat@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; metat 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, metat 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 metat 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, metat receives the images you select in Apple's photo picker; it does not request blanket access to your photo library.

With your Contacts permission, metat 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 metat archive. Contacts may be synchronised by your configured address book account, such as iCloud or another provider.

Dictating notes

metat'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 metat 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 metat's requirement for local dictation.

Calendars and reminders

You can create an event in Apple's calendar editor or ask metat 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. metat does not upload your complete calendar or reminder history to its own servers. Version 1.0 does not sign you in directly to Google or Microsoft and does not generate new Meet or Teams links.

Optional morning summary and notifications

The morning summary is off by default. If you enable it, metat asks for notification permission and schedules summaries on your device at your chosen time. The app uses follow-up plans saved in your metat archive for this. It does not read calendar events for the summary or send data to its own notification server.

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 metat’s scheduled and already delivered summary notifications. Calendar reminders are managed separately.

Profile searches, links and sharing

metat 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. Depending on your system settings, app data may be included in device or iCloud backups. metat 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 metat 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 addendum applies to prerelease versions with Google connectivity and the planned future update. The public version 1.0 does not include a direct Google connection. The following details describe this optional feature so prerelease users and Google can understand its data processing. A release date for the update has not been set.

Only when you choose to connect Google does metat open Google's sign-in and request access to calendar events. You enter your credentials with Google; metat receives access tokens, not your Google password. Tokens are stored in the device's protected Keychain and are not intended to transfer to other devices.

After your explicit confirmation, metat sends the meeting title, start and end times, the invited contact's email address and technical operation identifiers to the Google Calendar API. Google uses these details to create an event, send the invitation and process the request for a Meet link. metat may retrieve an event to check the outcome of an operation already started. Card images, the complete recognised card text, your address book and personal encounter notes are not sent for this purpose.

Google processes and stores event data according to its terms and your account settings. Invitees receive the associated event information. See Google's Privacy Policy. Information received from Google APIs is used only for the calendar features you choose, in compliance with the Google API Services User Data Policy, including its Limited Use requirements.

Disconnecting removes the local connection and tokens from metat. Previously created events and invitations already sent remain. You can also revoke the permission in your Google account.

This notice applies to metat 1.0. The separately labelled Google addendum applies only to prerelease versions with that feature and the planned future update. The notice will be updated when data processing changes.