Privacy Policy

Effective date: October 20, 2026

Seam is a Wear OS app developed and operated by Abil Bakhtiyarli (“I,” “me,” or “the developer”). This policy covers the app, its website, and related support and analytics services. For privacy questions or requests, contact support@gameweb.az.

At a glance

Seam processes iPhone notifications and media information on your devices to provide its features. The developer does not automatically receive your notification content, caller details, or sleep/activity information.
Optional automatic device analytics sends only your iPhone model, watch model, iOS version, and Wear OS version in the application payload. The setting is off by default and requires your acceptance before it can be turned on in Settings → Privacy → Share device info.
Email and connection diagnostics are sent to the developer only when you choose to submit them for support. Enabling device analytics does not authorize diagnostic uploads.
Device analytics is aggregated on receipt. Received support reports expire after 90 days; hourly cleanup, recovery-backup timing and deletion of correspondence/local copies are explained below.
Seam does not use your email for marketing, sell your personal information, or use it for targeted advertising.

Information processed on your devices

Seam connects your watch to your iPhone over Bluetooth. Local processing includes the following:

Notifications: App identifiers and display names, notification titles and message bodies, timestamps, dismissal state, and action information are processed to mirror notifications, synchronize supported actions, prevent duplicates, and queue delivery during sleep. Notification content is also saved in local delivery and history databases.
Caller details: Caller information supplied through iPhone notifications is used to display and manage incoming-call alerts. It is not an address-book upload. Depending on the alert and feature, caller information may also appear in locally mirrored notification content.
Media information: Track title, artist, album, playback state, duration, and volume are processed in memory to display and control media playback. Seam does not maintain a listening-history database.
Bluetooth information: Nearby device names and addresses, pairing status, and connection state are processed for discovery, pairing, and reconnection. The last connected iPhone’s Bluetooth address is saved locally.
Sleep/activity signals: With permission, Seam uses Health Services’ awake/asleep information, including the signal’s timing, and the watch’s Do Not Disturb status to decide when to present notifications. These signals are held in memory for that decision; Seam does not maintain a sleep-history database.
Preferences: Notification filters, detected app identifiers and display names, haptic choices, call settings, connection preferences, and the device-analytics preference are saved locally.
Purchase information: Seam receives purchase status and purchase tokens from Google Play to manage Pro access. It saves the entitlement status and tokens awaiting purchase acknowledgment locally.
Local diagnostics: Connection transitions, timestamps, error/status codes, retry information, counters, and call-feature outcomes are recorded to explain connection failures. An exported report can include watch information and connection details.

These local activities do not automatically upload their contents to the developer. The separate analytics and support activities below describe the information intended to be sent off-device.

Optional automatic device analytics

To understand which device and operating-system combinations use Seam and prioritize compatibility work, the intended release sends these four fields:

iPhone model name (Unknown in the current version);
Android/Wear OS watch brand and model name;
iOS version (Unknown in the current version); and
Wear OS version.

The application payload does not include your email address, device name, Bluetooth address, serial number, advertising ID, installation or account identifier, notification content, caller information, media details, sleep/activity signals, or diagnostic logs.

Share device info is off by default. After your first successful connection, the app offers an Accept/Decline explanation when you reach its main menu. Declining or dismissing leaves sharing off. You may enable it later through the same explanation in Privacy settings. Old default-on preferences do not count as consent and do not enable the new uploader. You can turn it off in the app’s Privacy settings without losing Seam’s notification, media, or Pro features. Once disabled, Seam will stop future automatic device-analytics submissions. This preference is saved across app restarts. Acceptance is required before transmission. The current device/OS combination is sent once after enabling, then again only when the combination changes; reopening, reconnecting or updating Seam does not trigger unchanged submissions. Reinstalling or clearing app data resets this local record. Counts are approximate configuration submissions, not unique people.

Individual device-analytics submissions are combined into aggregate model/version statistics on receipt and then discarded. These statistics describe reported device configurations, not a count of uniquely identified people. The four-field limit applies to the application payload; network infrastructure also receives connection metadata as explained below.

Diagnostic reports and email support

If you choose to submit a diagnostic report, the developer receives your submitted email address, device models and operating-system versions, and the technical report. Connection diagnostics may include the app version, connection events and their timestamps, Bluetooth connection status, error codes, retry information, and technical counters. Information you voluntarily include in support correspondence is also received and used to handle your request.

The upload feature shows the actual contact address, device information, diagnostic categories, history coverage, purpose and retention before you explicitly accept each submission. The problem category labels the report and does not filter its permitted history. Unknown iPhone model/iOS values are allowed. Reports are not uploaded automatically, regardless of the device-analytics setting. You can decline to submit a report and continue using Seam. You select an existing Google account on the watch to supply the required support contact address. This does not create a Seam account or grant mailbox access. Seam remembers the address locally and provides change/forget controls. If account selection or submission is declined or unavailable, no report is sent and the app offers manual email support. The address is used for replies, not marketing or compatibility statistics. Manual reports can include the disclosed device information even when automatic sharing is off, because each report requires separate acceptance.

The intended upload report excludes notification titles and message bodies, caller details, device names, Bluetooth addresses, purchase tokens, and other persistent identifiers. The report is built only from permitted technical fields, not raw logcat or arbitrary exception messages. Notification/caller/media content and personal Bluetooth names/addresses are excluded. Legacy local exports are removed by migration. After acceptance, an immutable report may wait for any internet connection, including LTE, and retry automatically for up to seven days. Up to five reports may be pending. You can cancel pending reports; cancellation cannot retract information already received remotely. Changing or forgetting the contact address does not alter accepted reports, and the app offers cancellation of pending reports when forgetting it. Please avoid adding passwords or unrelated personal information to support correspondence.

Website storage and network metadata

The website stores a light/dark theme preference in your browser’s local storage under seam-theme. This stays in the browser and is not an analytics identifier. You can remove it through your browser’s site-data controls. Fonts are served with the website; the website source does not include advertising pixels or visitor-analytics scripts.

When your browser or app contacts a website, email, analytics, or support service, the infrastructure handling the request receives network information such as an IP address and request metadata. That information is separate from the four device-analytics fields. Whether providers log or retain it, and for how long, must be confirmed before launch; this draft does not promise that IP addresses are never received or stored.

Google Play and other service providers

Google Play handles purchases and payment details. Seam uses the purchase result to provide Pro access and does not ask you to enter payment-card details into the app. Google’s bundled components, including the Play Billing library, have their own data handling and diagnostic reporting. The four-field device-analytics limit describes Seam’s planned analytics payload, not every Google service’s practices. See Google’s Privacy Policy.

The developer and service providers needed to operate hosting, email, analytics ingestion, and support storage may process the information relevant to those services. Cloudflare Workers and D1 have been selected for support intake/storage and compatibility aggregates. D1 is intended to be created with EU jurisdiction, while Workers execute globally; this does not mean all provider processing stays in the EU. The developer accesses private reports through authenticated Cloudflare APIs and can download JSON/text copies. See Cloudflare’s Privacy Policy. Actual deployment, provider network/security metadata retention, website/email provider details and applicable transfer arrangements must be verified before this draft becomes effective.

Information may also be disclosed when required by applicable law or a valid legal request. Access to support information is intended to be limited to the developer and providers needed to handle it. Any future expansion of recipients or purposes must be reflected in the policy before it takes effect.

Retention and deletion

Support reports and correspondence: Each received diagnostic report and its contact address expire 90 days after server receipt. Expired records are excluded from developer downloads immediately; hourly cleanup removes stored rows, subject to operational delays. Related correspondence and downloaded copies follow the same report deadline. D1 Free recovery backups can retain deleted information for up to seven further days. Restored backups require expiry/deletion review before access resumes. An unsent accepted report expires locally after seven days. A follow-up submission has its own 90-day period; it does not restart the retention period for older information. Mailbox copies, attachments, support storage, and provider backups must follow the finalized deletion arrangements.
Automatic device analytics: Individual submissions are discarded after aggregation on receipt. Only aggregate statistics that cannot identify a person may be kept indefinitely. Provider access/security logs are separate and require their own disclosed retention period before launch.
Local notification data: The history screen covers the last seven calendar days. Cleanup uses calendar-day cutoffs with additional slack and runs during app activity; delivery storage has separate cleanup and size limits. Data is not guaranteed to disappear at an exact seven-day deadline, particularly while the app is not running.
Other local data: Settings and the detected-app registry remain until changed or app data is removed. Local diagnostic events have bounded history, while some counters persist. Media and sleep/activity state are temporary in-memory state. Accepted unsent report payloads are kept privately for up to seven days, and removed after receipt, cancellation, permanent failure or expiry. Saved contact email remains until forgotten or app data is cleared.
Backups: Seam’s backup rules exclude its notification-content databases and cached Pro entitlement from Android cloud backup and device transfer. Contact email, pending report payloads, device-sharing consent, and connection/call diagnostic stores are excluded from app cloud backup and device transfer. Other settings may remain eligible depending on device support and settings. Restoring app data must not grant sharing consent.

You can request earlier deletion of identifiable support information using the contact address below. If a specific legal obligation requires retention, the developer will explain the applicable limitation where permitted. Uninstalling stops the app from operating but does not delete reports already submitted, copies you shared, or data held under providers’ backup arrangements. Clearing app data removes local app-managed data; clipboard contents, separately saved copies, and backups may require their own controls.

Your choices and privacy rights

You can disable automatic device analytics, choose whether to send a support report, manage permissions in watch settings, and remove local app data. Disabling analytics does not remove aggregate statistics already created or automatically delete a support request. Local data that has never been sent to the developer must be managed on your devices.

Depending on the law applicable to you and the processing involved, you may have rights to access, correct, delete, restrict, object to, or obtain a portable copy of personal information, withdraw consent where consent is the basis for processing, and complain to a data-protection authority. California rights, where applicable, may also include opting out of sale or sharing for cross-context behavioral advertising and receiving equal treatment when exercising rights. Seam does not sell personal information or share it for that advertising purpose.

Contact support@gameweb.az to make a request. Provide enough information to locate the support submission, such as the sending email address and approximate submission date; do not send passwords. The developer may request proportionate verification before disclosing or deleting information. Aggregate statistics that can no longer be linked to you cannot be searched or removed as an individual record.

The legal basis and any additional consent or in-app disclosure needed for each planned activity must be finalized before launch. A default-on preference must not be represented as affirmative consent. Where consent is required, the release must obtain it before the relevant processing begins; withdrawing it does not affect earlier lawful processing.

Security and international processing

The intended release requires encrypted network connections for uploads and access controls for support information. The specific storage, access, deletion, and incident-response arrangements remain subject to the launch review below. This draft does not certify safeguards that have not yet been implemented, and no system can promise absolute security.

Providers may process information outside your country. The actual processing locations and any required international-transfer arrangements must be identified before this policy becomes effective. This draft does not claim that a particular adequacy decision, contractual clause, or consent mechanism has already been established. Any required breach notifications will follow applicable law.

Children

Seam is not intended for children under 16, or a higher age where applicable law requires it. The developer does not knowingly seek personal information from children under that age. If you believe a child has submitted personal information, contact support@gameweb.az so it can be investigated and deleted where appropriate. The intended audience and any age-related requirements must be confirmed for release.

Changes and contact

The effective policy will be updated when practices change, with a revised update date and effective date. Material changes will receive any additional notice or consent required by applicable law. This page is the authoritative policy draft; root reference documents are not the published policy.

For privacy questions, support-data deletion, or other requests, contact us at support@gameweb.az.