App Privacy

1. Overview

Sammes AS publishes three applications on a shared platform: Connect (connected devices and IoT control), Intel (the intelligence layer that produces insights from connected data) and Social (profiles, user-generated content and other social features). All three are covered by our Privacy Policy, which sets out the purposes, legal bases, retention and your rights. This page adds the store-level detail: what each app declares in the App Store and in its privacy manifest.

Apple requires every app on the App Store to complete the App Privacy section in App Store Connect, which Apple displays as the "App Privacy" card on the app's product page. The labels are a summary of data the app and its third-party partners collect. The labels shown on the App Store are the authoritative public summary, and this page mirrors them. If this page and a store label ever disagree, the store label is the summary Apple displays and we will correct this page promptly. Where this page describes a fuller picture than the label, the label remains the summary and this page and the Privacy Policy give the underlying detail.

2. How Apple's data types map to our collection

Apple groups data into a fixed set of types. Our apps use the following ones:

Contact Info covers data such as name, email address and phone number. We use it for accounts, authentication and support.
Location covers coarse and fine location. Coarse means approximate, such as a city or region; fine means precise coordinates. We request location only through the operating-system permission prompt.
User Content covers content you create, such as photos, videos, audio, text and messages. Other User Content covers profile-level content such as a bio, avatar, follows and other material that is not a post or a message.
Identifiers covers account identifiers such as a user ID, and device identifiers such as a device ID. We use a random app-instance identifier rather than a hardware identifier wherever we can.
Purchases covers purchase history and subscription status. Payment instruments are handled by Apple, not by us.
Usage Data covers product interaction, such as which features you use and how you move through the app.
Diagnostics covers crash data, performance data and other technical measurements used to keep the app working.
Other Data covers device telemetry and derived values that do not fit the categories above, such as sensor readings from connected hardware and insight values produced by Intel.

Two of Apple's attributes appear in each table below. Linked to identity means the data can be tied to your account or device. Used for tracking means the data is linked with data from other companies' apps or websites for targeted advertising or advertising measurement. Where a data type is optional, we mark it as "Yes (optional)" and it is collected only if you use the feature that needs it and, where required, grant permission.

3. Connect

Connect pairs your account with connected hardware and lets you monitor and control it from one place.

Data type	Collected?	Linked to identity?	Used for tracking?	Purposes
Contact Info (name, email address)	Yes	Yes	No	Create and secure your account; authentication; support
Identifiers (user ID)	Yes	Yes	No	Keep your devices and settings associated with your account
Identifiers (device ID)	Yes	Yes	No	Recognise the device you sign in from; account security; abuse prevention
Location (coarse)	Yes (optional)	Yes	No	Discover and set up nearby devices; grouping devices by place
Purchases (purchase history)	Yes	Yes	No	Manage subscriptions and feature entitlements
Usage Data (product interaction)	Yes	Yes	No	Understand feature use; improve reliability and performance
Diagnostics (crash data, performance)	Yes	No	No	Detect and fix crashes and performance problems
User Content (device names, groups, configuration)	Yes	Yes	No	Label, organise and operate your connected devices
Other Data (device telemetry, sensor readings, device state)	Yes	Yes	No	Monitoring and control; supplying connected data to Intel

4. Intel

Intel turns data from connected devices into insights, alerts and recommendations.

Data type	Collected?	Linked to identity?	Used for tracking?	Purposes
Contact Info (name, email address)	Yes	Yes	No	Account, authentication and support
Identifiers (user ID)	Yes	Yes	No	Associate insights with the correct account and devices
Location (coarse)	Yes (optional)	Yes	No	Contextualise insights, for example by region or time zone
Purchases (purchase history)	Yes	Yes	No	Manage subscriptions and feature entitlements
Usage Data (product interaction)	Yes	Yes	No	Improve the relevance and quality of insights
Diagnostics (crash data, performance)	Yes	No	No	Keep the app stable and responsive
User Content (queries, saved insights, notes)	Yes	Yes	No	Produce, save and display the insights you request
Other Data (derived insight values and scores)	Yes	Yes	No	Deliver the intelligence features and improve their accuracy

Social adds profiles, user-generated content and messaging. Because you can publish content to other users, it collects a wider set of data types than Connect or Intel.

Data type	Collected?	Linked to identity?	Used for tracking?	Purposes
Contact Info (name, email address, optional phone number)	Yes	Yes	No	Account, authentication, support; optional contact discovery with your permission
Identifiers (user ID, device ID)	Yes	Yes	No	Account, session security and abuse prevention
Location (coarse and fine)	Yes (optional)	Yes	No	Attaching a place to a post; showing nearby content, only with your permission
Purchases (purchase history)	Yes	Yes	No	Manage subscriptions and feature entitlements
Usage Data (product interaction)	Yes	Yes	No	Feeds, recommendations, moderation and abuse detection
Diagnostics (crash data, performance)	Yes	No	No	Keep the app stable and responsive
User Content (posts, photos, videos, audio, comments)	Yes	Yes	No	Publish and display the content you choose to share
User Content (direct messages)	Yes	Yes	No	Deliver private messages between users
Other User Content (profile, bio, avatar, follows)	Yes	Yes	No	Build your profile and your social graph

6. Tracking and third-party advertising

None of Connect, Intel or Social uses your data for third-party advertising, and none of them uses your data for cross-app tracking as Apple defines it. We do not combine data from our apps with data from other companies' apps or websites for advertising, we do not share data with data brokers, and we do not allow advertising networks to place tracking technology in our apps. Every "Used for tracking?" value in the tables above is "No".

Our iOS privacy manifests declare NSPrivacyTracking as false and leave the NSPrivacyTrackingDomains list empty. Because we do not track, we do not display Apple's App Tracking Transparency prompt for advertising. If we ever introduce a feature that counts as tracking, we will request permission through App Tracking Transparency before any tracking begins, update the App Store labels, and update this page. You can read the position we take in our Privacy Policy.

7. Privacy manifests and required-reason APIs

Each of our iOS apps ships a privacy manifest named PrivacyInfo.xcprivacy, and every third-party SDK we use ships its own. The manifest is a machine-readable file that declares the data the app or SDK collects, whether it uses tracking, the tracking domains it contacts, and the APIs it calls that Apple designates as requiring a declared reason.

Apple requires a declared reason for certain APIs because they can be used to fingerprint a device. The required-reason API categories our apps declare are:

User defaults (NSPrivacyAccessedAPICategoryUserDefaults, reason CA92.1): to read and write your app preferences inside the app's own container.
File timestamp (NSPrivacyAccessedAPICategoryFileTimestamp, reason C617.1): to determine when app files were last modified, for caching and sync.
System boot time (NSPrivacyAccessedAPICategorySystemBootTime, reason 35F9.1): to measure elapsed time such as a session duration, without reading a device clock.
Disk space (NSPrivacyAccessedAPICategoryDiskSpace, reason E174.1): to check available storage before writing media or telemetry.

We verify the privacy manifest of every third-party SDK before we ship it, and we require our SDK providers to declare their own data collection and tracking accurately. The combined declarations for an app determine the App Privacy label Apple displays, which is why section 1 treats the store label as the authoritative public summary. A list of the SDKs included in each app is available on request from [email protected].

Data handled inside the apps is subject to the retention periods, security measures and rights set out in the Privacy Policy. You can request deletion at any time using our account deletion page, and the Cookie Policy explains SDK-based processing in the apps by contrast with the website.

8. Changes to this page

We review this page with every app release that changes what we collect, how we use it, or the permissions we request. The effective date and version at the top show the current version. When a change affects the App Privacy labels, we update the labels in App Store Connect and this page together, so that the two continue to mirror each other. Material changes are announced in the app and, where required, we ask for your consent before the change takes effect.

9. Contact

For questions about the data an app collects, contact our data-protection contact at [email protected], or write to SAMMES AS, Øvrehusvegen 37E, 4054 Tjelta, Norway. For general help, use [email protected] or our support page. If you are not satisfied with our response, you can complain to Datatilsynet, the Norwegian Data Protection Authority, at datatilsynet.no.