问候工作室(Greeting Studio)隐私政策
上次根据应用源代码核对:2026年10月21日。公开网址:https://greeting-studio-privacy.web.app/privacy/
本政策说明 MACELLERIA MASNAOUI SAS DI MASNAOUI ABDERRAHMANE(Google Play 开发者名称:oubaidaAPS)运营的 美好祝福 · 早安晚安贺卡(Greeting Studio) 如何处理信息。Android 应用包名 com.greetingstudio.greeting_studio;iOS Bundle Identifier com.greetingstudio.greetingStudio。应用以离线贺卡与文字内容为主,并展示由 Google AdMob 提供的广告,同时使用 Google 用户消息平台(UMP)征求广告同意。
1. 运营方收集的数据
根据当前应用代码,问候工作室不提供账号注册,也不把贺卡、收藏或编辑内容上传到运营方自有服务器。下列信息保存在您的设备上:
- 外观与语言偏好(如深色模式、简体/繁体),使用设备本地存储(SharedPreferences)。
- 收藏与最近浏览的贺卡标识,使用设备本地数据库(Drift / SQLite)。
- 通知开关状态。应用可能请求通知权限,以便在您开启时显示本地通知(
flutter_local_notifications、flutter_timezone);源代码中未见 Firebase Cloud Messaging 或其他推送服务。 - 您保存的贺卡文件写入应用自己的文档目录,而不是系统相册。
您使用系统分享功能时,所选图片或文字会交给您选择的第三方应用;那些应用有各自的隐私政策。应用内评分会调用系统/商店评价界面(in_app_review),不会由问候工作室另行收集评论内容。
应用内有离线生成的氛围/天气风格文案模块;源代码未申请精确或大致位置权限,也未见调用在线天气 API 或 GPS。
2. 广告与第三方 SDK(AdMob)
应用集成 google_mobile_ads(Google Mobile Ads / AdMob)以及 Google 用户消息平台(UMP)同意表单。广告形式包括横幅、原生广告、插屏;iOS 工程还配置了 App Open 广告单元。Android 合并清单还会引入广告标识符(AD_ID)、网络访问、唤醒锁以及广告服务相关权限。iOS 配置了 App Tracking Transparency 使用说明和 SKAdNetwork 项。应用源代码未直接调用 ATT API;在需要时,Google UMP 可能展示同意与跟踪提示。
Google 及其广告合作伙伴可能收集或接收例如:设备与应用信息、IP 地址、广告标识符(Android AD_ID;在 iOS 上仅在允许跟踪时可能使用 IDFA)、粗略位置(例如基于 IP,源代码无法证实是否发生)、广告互动、诊断数据,以及用于频次控制和防欺诈的标识。精确范围、保留期限和跨境传输由 Google 的政策决定,不由问候工作室服务器控制。
应用将 DELAY_APP_MEASUREMENT_INIT 设为 true,以便在同意流程完成前延迟广告测量初始化。若设备所在地区需要同意,您可通过设置中的「广告与隐私」(当系统要求显示时)管理广告个性化。
调试构建可能使用 Google 示例广告单元,以便开发测试;正式发布使用运营方在 AdMob 控制台中的正式广告单元。
Google 广告隐私说明:https://policies.google.com/privacy 与 https://policies.google.com/technologies/ads。
3. 其他第三方库
应用还使用(均在设备侧或通过系统界面,而非问候工作室自建后台):url_launcher、share_plus、permission_handler、path_provider、in_app_review、flutter_local_notifications、flutter_timezone。源代码中未见 Firebase Analytics、Crashlytics 或运营方自有分析服务。公开政策页托管于 Firebase Hosting;在浏览器中打开该页与应用安装包分开,主机可能会记录访问。
4. 使用目的
- 在设备上显示、编辑、收藏、保存和分享贺卡。
- 记住您的显示与通知偏好。
- 展示广告,为应用运营提供支持。
- 遵守适用的同意与广告披露要求。
5. 数据保留与删除
设备本地偏好、收藏和已保存文件会保留到您卸载应用、清除应用数据,或在应用内删除对应内容为止。问候工作室运营方没有可从自有服务器删除您贺卡内容的账户系统,因为这些内容未上传到运营方服务器。广告合作伙伴按其自身期限保留其收集的数据。
6. 儿童
本应用面向一般用户制作贺卡,源代码未将其配置为儿童应用。广告 SDK 的儿童定向选项必须由运营方在 AdMob / Play 控制台中设置;无法仅从代码确认线上配置。若您是家长并认为儿童不应看到个性化广告,请使用系统限制或卸载应用。
7. 您的权利
您可以:在设置中关闭通知;通过系统设置撤销通知或(在 iOS 上)跟踪许可;卸载应用以删除本地数据;在 UMP 表单可用时管理广告个性化;联系下方邮箱行使适用法律(例如访问、删除、反对)下的权利。因多数数据仅存于设备,部分请求需要您在本机操作。
8. 国际传输
应用本身不把贺卡内容发往运营方服务器。广告与商店 SDK 可能将数据传输到运营方所在地以外的国家,包括由 Google 处理的传输。
9. 联系方式
运营方:MACELLERIA MASNAOUI SAS DI MASNAOUI ABDERRAHMANE(Google Play 开发者名称:oubaidaAPS)
电子邮件:masnaouikamal@gmail.com
运营方的其他商家信息以 Google Play 应用详情页显示的内容为准。
10. 变更
政策更新后会修改本页日期。重大变更应通过应用更新或公开网页提示。公开网址:https://greeting-studio-privacy.web.app/privacy/。
Greeting Studio Privacy Policy
Last checked against application source: 21 October 2026. Public URL: https://greeting-studio-privacy.web.app/privacy/
This policy describes how 美好祝福 · 早安晚安贺卡 (Greeting Studio), operated by MACELLERIA MASNAOUI SAS DI MASNAOUI ABDERRAHMANE (Google Play developer name: oubaidaAPS), handles information. Android application id com.greetingstudio.greeting_studio; iOS bundle identifier com.greetingstudio.greetingStudio. The app is an offline-first greeting-card product. It shows ads served by Google AdMob and uses Google’s User Messaging Platform (UMP) for advertising consent where required.
1. Data processed by the app operator
Based on the current source, Greeting Studio does not offer accounts and does not upload cards, favorites, or editor content to an operator-owned server. The following stays on the device:
- Appearance and language preferences (for example theme and Simplified/Traditional script) in on-device storage (SharedPreferences).
- Favorite and recent greeting identifiers in an on-device database (Drift / SQLite).
- Notification preference. The app may request notification permission so local notifications can be shown if you enable them (
flutter_local_notifications,flutter_timezone). The source does not include Firebase Cloud Messaging or another push provider. - Saved cards are written to the app’s own documents directory, not the system photo gallery.
If you use the system share sheet, the chosen image or text is delivered to the app you pick; those apps have their own policies. In-app rating uses the store review UI (in_app_review). Greeting Studio does not separately collect review text.
The app includes offline atmosphere/weather-style copy. The source does not request fine or coarse location permission and does not call a live weather API or GPS.
2. Advertising and third-party SDKs (AdMob)
The app embeds google_mobile_ads (Google Mobile Ads / AdMob) and Google’s User Messaging Platform (UMP) consent form. Formats include banner, native, and interstitial ads; the iOS project also configures an app-open ad unit. The merged Android manifest also brings in the advertising ID permission (AD_ID), network access, wake lock, and ads-services related permissions. iOS includes an App Tracking Transparency usage string and SKAdNetwork items. The app source does not call App Tracking Transparency APIs directly; Google UMP may present consent and tracking prompts where required.
Google and its advertising partners may collect or receive information such as: device and app data, IP address, advertising identifiers (Android AD_ID; on iOS, the IDFA only if tracking is allowed), coarse location (for example from IP — not confirmable from this app’s source), ad interactions, diagnostics, and identifiers used for frequency capping and fraud prevention. Exact scope, retention, and international transfers are governed by Google’s policies, not by a Greeting Studio backend.
The app sets DELAY_APP_MEASUREMENT_INIT so ads measurement can wait for the consent flow. Where consent is required, you can manage ad personalization from Settings → Ads & privacy when that row is shown.
Debug builds may use Google sample ad units for development. Release builds use the operator’s production AdMob units.
Google’s policies: https://policies.google.com/privacy and https://policies.google.com/technologies/ads.
3. Other third-party libraries
The app also uses (on-device or via system UI, not an operator backend): url_launcher, share_plus, permission_handler, path_provider, in_app_review, flutter_local_notifications, and flutter_timezone. The Greeting Studio source does not include Firebase Analytics, Crashlytics, or an operator-owned analytics service. The public policy page is hosted on Firebase Hosting; opening that page in a browser is separate from the app binary and may be logged by the host.
4. Purposes
- Show, edit, favorite, save, and share greeting cards on the device.
- Remember display and notification preferences.
- Show ads that support the app.
- Honor applicable consent and ad-disclosure rules.
5. Retention and deletion
On-device preferences, favorites, and saved files remain until you uninstall the app, clear app data, or delete the corresponding items in the app. The operator has no account-based deletion flow for card content on its own servers because that content is not uploaded there. Advertising partners retain data according to their own periods.
6. Children
The app is built as a general greeting-card product and is not configured in source as a children’s app. Child-directed ad treatment must be set by the operator in AdMob / Play Console; live console settings cannot be confirmed from code alone. Parents who do not want children to see personalized ads should use device restrictions or uninstall the app.
7. Your rights
You may turn notifications off in Settings; revoke notification or (on iOS) tracking permission in system settings; uninstall the app to remove local data; manage ad personalization when the UMP form is available; and contact the email below to exercise rights available under applicable law (for example access, deletion, objection). Because most app data stays on the device, some requests require action on the device itself.
8. International transfers
The app does not send card content to an operator server. Ads and store SDKs may transfer data to countries other than yours, including processing by Google.
9. Contact
Operator: MACELLERIA MASNAOUI SAS DI MASNAOUI ABDERRAHMANE (Google Play developer name: oubaidaAPS)
Email: masnaouikamal@gmail.com
Other trader details of the Operator are as shown on the App’s Google Play listing.
10. Changes
When this policy is updated, the date above will change. Material changes should be noted in an app update or on the public page. Public URL: https://greeting-studio-privacy.web.app/privacy/.
Google Play Data safety mapping (operator checklist)
This mapping is based on current Greeting Studio source and typical AdMob behavior. Items marked “cannot confirm from code” must be verified in Play Console, AdMob, and Google’s disclosures before you submit Data safety.
- Privacy policy URL: Play Console and App Store Connect should use
https://greeting-studio-privacy.web.app/privacy/. - Does this app contain ads? Yes.
- Collected by the app operator: no account data, no operator analytics in source, no uploaded photos or contacts. Local-only preferences/favorites are not “collected” by the operator unless a future backend is added.
- Advertising ID: likely collected by Google Mobile Ads (Android
AD_ID; iOS IDFA only if tracking is allowed). Declare as collected by a third party for advertising if AdMob is enabled. Cannot confirm every partner from this repo. - Approximate location: the app does not request location permission. AdMob may infer coarse location from IP — cannot confirm from code. Do not declare precise location based on this source.
- App interactions / diagnostics: may be processed by Google ads SDKs; not by an operator analytics SDK in this repo.
- Photos and videos: created/saved locally; sharing is user-initiated via the system share sheet. Do not declare operator collection of photos unless you add upload.
- Data encrypted in transit / deletion request: operator has no card backend. Ads traffic encryption and deletion are Google’s. User-facing deletion of operator-held data is limited to email contact for requests the operator can fulfill.
- Sold / shared for advertising: follow Play’s definitions for AdMob personalization. UMP consent may apply in some regions. Confirm in AdMob and Play forms; cannot confirm live serving from source.