隐私政策
生效日期：2026 年 9 月 1 日 · 适用于 iOS 与 Android 版 FlashAura
- 你的照片和视频不会离开你的设备。滤镜与调色全部在本机 GPU 上完成，应用里没有任何上传通道。
- 没有账号系统。不需要注册、不需要登录，我们不收集你的姓名、邮箱、手机号、通讯录或精确位置。
- 没有广告，不使用广告标识符，不出售数据。两个平台都不取广告 ID，也没有任何归因组件。
- iOS 与 Android 都会通过 Google Firebase 收集匿名的使用统计与崩溃报告，用来知道哪些功能真的被用到、哪里会崩。下面说明收集的是哪些。
一、两个平台收集的是同一套东西
iOS 版和 Android 版使用同一套埋点：同样的事件、同样的字段名，发往同一个 Google Firebase 项目。下表列出全部差异——差异都在权限上，不在收集的数据上。
| | iOS（App Store） | Android（Google Play） |
|---|
| 使用统计 | Firebase Analytics | 相同 |
|---|
| 崩溃报告 | Firebase Crashlytics | 相同 |
|---|
| 广告标识符 | 不取（从不请求跟踪授权） | 不取（见下） |
|---|
| 我们自己的服务器 | 无 | 无 |
|---|
| 麦克风 | 录像时录入声音 | 不申请（录像无声音） |
|---|
| 相册权限 | 读取 + 写入 | 一条都不申请 |
|---|
1.1 关于广告标识符
这一点值得单独说，因为它不是默认状态：Android 上的 Firebase Analytics 默认会采集广告 ID，还会带上安装归因。我们把这些全部关掉了——从安装包里移除了相关权限，并显式关闭了采集开关。
这么做是为了和 iOS 一致：iOS 上取广告标识符需要弹出"允许跟踪"授权，而这个应用从来没有集成那套东西。既然一端不取，另一端也不该取。
二、具体收集什么
2.1 使用统计（Firebase Analytics）
为了知道哪些功能真的被用到、哪些流程会失败，我们记录应用内的基本操作——启动应用、使用相机、套用滤镜、调整参数、导出成功或失败、权限被拒绝——以及随之而来的技术信息，例如应用版本、所用的滤镜与渲染效果、本次处理的图片数量、失败时的错误类型。
Firebase 自身还会自动采集一个匿名的应用实例标识、设备型号、系统版本、系统语言，以及由 IP 地址推断出的大致国家或地区。
2.2 崩溃报告（Firebase Crashlytics）
应用崩溃或遇到可恢复的错误时，会上报崩溃堆栈、当时的设备状态、一个匿名的安装标识，以及我们附加的诊断上下文（比如当时在哪个页面、用的哪个滤镜）——没有这些，一条渲染相关的崩溃堆栈几乎无法定位。
2.3 这些数据里没有什么
- 没有任何照片、视频、缩略图或像素数据。上报的只有「用了哪个滤镜」这类标识，不包含被处理的内容本身。
- 没有广告标识符（IDFA）。应用不请求「允许跟踪」授权，也没有集成任何广告或归因组件。
- 没有姓名、邮箱、手机号、通讯录、日历、健康数据或精确位置。
2.4 关于关闭统计
坦白说：两个平台目前都没有提供应用内的统计开关。如果你不希望这些数据被收集，可以卸载应用；也可以通过下方邮箱联系我们，我们会协助处理。我们正在考虑在后续版本中加入开关。
三、权限，以及为什么需要它
| 权限 | 平台 | 用途 |
|---|
| 相机 | iOS、Android | 取景、实时滤镜预览、拍照与录像 |
|---|
| 麦克风 | 仅 iOS | 录制视频时同步录入声音。Android 版录像不含声音，因此不申请这项权限 |
|---|
| 读取相册 | 仅 iOS | 浏览并选择要编辑的照片 |
|---|
| 写入相册 | 仅 iOS | 把编辑结果保存回相册 |
|---|
| 网络访问 | iOS、Android | 仅用于上报上面那些统计与崩溃数据。不需要你授权，安装时也不会展示 |
|---|
Android 版一条相册权限都没有申请，这是刻意的：选图走系统自带的照片选择器（系统只把你挑中的那张交给应用），保存走系统媒体库接口，两者都不需要授予应用访问整个相册的权限。
四、你的照片和视频是怎么被处理的
- 拍摄：画面从相机直接进入设备 GPU 完成滤镜渲染，再保存到系统相册。
- 编辑：从系统选择器读取你指定的图片，在本机完成渲染，导出结果写回相册。
- 配方与偏好设置：存在设备本地，不同步、不上传。
- 卸载应用即清除这些本地数据。
应用没有连接我们自己的服务器——我们没有为 FlashAura 运行任何接收用户内容的后端。
五、第三方
两个平台都使用 Google 提供的 Firebase Analytics、Firebase Crashlytics 及其依赖的基础组件。这些数据由 Google 按其条款处理，详见 Google 隐私政策 与 Firebase 隐私与安全说明。
除此之外，两个平台都没有集成会向外发送数据的第三方组件，也没有任何广告或归因组件。
六、数据保留与删除
- 卸载应用后，我们不再收到你设备的任何新数据。
- 已收集的统计与崩溃数据按我们在 Firebase 控制台设置的保留期限自动删除。
- 如果你希望我们删除与你的设备相关的数据，请通过下方邮箱联系。由于我们没有账号体系，这些数据只能通过匿名的设备标识定位，我们可能需要你配合提供必要信息。
七、儿童
FlashAura 不面向 13 岁以下儿童，我们不会有意收集儿童的个人信息。如果你认为孩子向我们提供了信息，请联系我们。
八、你的权利
根据你所在地区的法律，你可能享有访问、更正、删除或反对处理个人数据的权利。请通过下方邮箱提出，我们会在合理时间内答复。
九、本政策的变更
本政策更新时，我们会修改页面顶部的生效日期。涉及数据收集方式的实质性变更，会在应用更新说明中一并告知。
十、联系我们
爻爻科技（YaoyaoLabs）
电子邮件：1569485690@qq.com
Privacy Policy
Effective 1 September 2026 · Applies to FlashAura for iOS and Android
- Your photos and videos never leave your device. All filtering and color work happens on your device's GPU. The app has no upload path.
- There are no accounts. No sign-up, no login. We do not collect your name, email address, phone number, contacts, or precise location.
- No ads, no advertising identifier, no data sales. Neither platform reads an advertising ID, and there is no attribution component.
- Both iOS and Android collect anonymous usage statistics and crash reports through Google Firebase, so we can tell which features are actually used and where things break. What that covers is described below.
1. Both platforms collect the same things
iOS and Android use one shared set of instrumentation: the same events, the same field names, sent to the same Google Firebase project. The table below lists every difference between them — and all of them are about permissions, not about what is collected.
| | iOS (App Store) | Android (Google Play) |
|---|
| Usage analytics | Firebase Analytics | Same |
|---|
| Crash reporting | Firebase Crashlytics | Same |
|---|
| Advertising ID | Not read (never asks for tracking permission) | Not read (see below) |
|---|
| Servers of our own | None | None |
|---|
| Microphone | Records sound with video | Not requested (video has no audio) |
|---|
| Photo library permission | Read + write | None at all |
|---|
1.1 About the advertising identifier
This deserves its own note, because it is not the default state: Firebase Analytics on Android collects the advertising ID by default, and brings install attribution along with it. We turned all of that off — the relevant permissions are stripped from the shipped package, and collection is explicitly disabled.
We did this to match iOS: reading the advertising identifier there requires the "allow tracking" prompt, and this app has never integrated that. If one platform does not read it, neither should the other.
2. What is collected
2.1 Usage analytics (Firebase Analytics)
So we can tell which features are actually used and where things fail, we record basic in-app actions — opening the app, using the camera, applying a filter, changing an adjustment, an export succeeding or failing, a permission being denied — along with the technical details that go with them, such as the app version, the filter and render effect used, how many images were processed, and the error type on failure.
Firebase itself also collects an anonymous app-instance identifier, device model, OS version, system language, and an approximate country or region inferred from your IP address.
2.2 Crash reporting (Firebase Crashlytics)
When the app crashes or hits a recoverable error, it reports the crash stack, device state at the time, an anonymous installation identifier, and the diagnostic context we attach (such as which screen you were on and which filter was in use) — without that, a rendering crash stack is close to impossible to place.
2.3 What is not in that data
- No photos, videos, thumbnails, or pixel data of any kind. We send identifiers like "which filter was used", never the content being processed.
- No advertising identifier (IDFA). The app never asks for tracking permission and integrates no advertising or attribution component.
- No name, email, phone number, contacts, calendar, health data, or precise location.
2.4 About turning analytics off
Candidly: neither platform currently has an in-app switch for analytics. If you would rather this data were not collected, you can uninstall the app, or contact us at the address below and we will help. We are considering adding a switch in a future release.
3. Permissions, and why each is needed
| Permission | Platform | Purpose |
|---|
| Camera | iOS, Android | Framing, live filter preview, taking photos and video |
|---|
| Microphone | iOS only | Recording sound alongside video. The Android version records video without audio, so it does not request this |
|---|
| Photo library (read) | iOS only | Browsing and choosing photos to edit |
|---|
| Photo library (add) | iOS only | Saving edited results back to your library |
|---|
| Network access | iOS, Android | Used only to send the statistics and crash reports described above. It needs no approval from you and is not shown at install time |
|---|
The Android version requests no photo-library permission at all, deliberately: picking images goes through the system photo picker (which hands the app only the image you chose), and saving goes through the system media store. Neither requires granting the app access to your whole library.
4. How your photos and videos are handled
- Capture: frames go from the camera straight to the device GPU for filter rendering, then to your system photo library.
- Editing: the image you pick is read through the system picker, rendered on-device, and the result is written back to your library.
- Recipes and preferences: stored locally on the device. Not synced, not uploaded.
- Uninstalling the app removes this local data.
The app does not talk to servers of ours — we run no backend for FlashAura that receives user content.
5. Third parties
Both platforms use Google's Firebase Analytics and Firebase Crashlytics, together with the base components they depend on. That data is handled by Google under its own terms; see the Google Privacy Policy and Firebase privacy and security information.
Beyond that, neither platform integrates any third-party component that sends data outward, and neither has any advertising or attribution component.
6. Retention and deletion
- Once you uninstall the app, we receive no further data from your device.
- Analytics and crash data already collected is deleted automatically according to the retention period we have configured in the Firebase console.
- To have data associated with your device deleted, contact us at the address below. Because we operate no account system, that data can only be located through an anonymous device identifier, so we may need your help to identify it.
7. Children
FlashAura is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us with information, please contact us.
8. Your rights
Depending on where you live, you may have the right to access, correct, delete, or object to the processing of your personal data. Write to the address below and we will respond within a reasonable time.
9. Changes to this policy
When this policy is updated we will change the effective date at the top of this page. Material changes to how data is collected will also be noted in the app's release notes.
10. Contact us
YaoyaoLabs (爻爻科技)
Email: 1569485690@qq.com
