Zipy
  • Welcome to Zipy ai
  • Getting Started
    • Install Zipy
    • Installing with Google Tag Manager
    • Supported frameworks
    • Security Overview
    • Sensitive User Data
    • SOC2 Type II
  • Zipy For Mobile
    • React Native Setup
      • Install React Native
      • Input Masking
      • Session Replay
      • Screen Transition Capture
      • Gesture Capturing
      • Unhandled Exception Capture
      • Custom Logging
      • Fetch and XHR Network Calls
      • Profiling
      • Device Information Capture
      • Session URL Retrieval
      • Identify Users
      • Firebase Integration
    • Flutter Setup
      • Install Flutter
      • Session Replay
      • Input Masking & Custom Masking
      • Screen Transition Capture
      • Gesture Capturing
      • Unhandled Exception Capture
      • Custom Logging
      • Http Network Calls
      • Dio Network Calls
      • Profiling
      • Device Information Capture
      • Session URL Retrieval
      • Identify Users
      • Firebase Integration
      • Session Recording Control
      • Data Sanitization
  • iOS Setup
    • Install in an iOS app
    • Identify Users
    • Screen Tracking & Tagging
    • Custom Logging
    • Session URL Retrieval
    • Session Recording Control
    • Input Masking & Custom Masking
  • Chrome Extension
    • Zipy Plug and Play Support
  • Configure
    • Zipy Recording Control
    • Release Version
    • Identifying Users
    • Adding Custom Identifiers
    • Anonymize Users
    • Source Maps
    • Blocking PII data
    • Ignoring Errors/Noise
    • npm Update
    • Support Integration
    • Session Stitching (rootDomain)
  • Product Features
    • Custom Events
    • Session Replay
    • Errors
    • Analytics
    • Time Filters
    • Multiple Filters
    • Clicked Element Filters
    • Manage Teams
    • Stack Trace
    • Console Logs
    • Network Requests
    • Network Headers and Payload
    • Custom Logs
    • Live Users
    • Alerts
      • Slack Alerts
      • Email Alerts
      • Live Alerts
      • Custom Alerts
    • Auto Resolve Errors
    • Zipy Labels Plugin
    • iFrame Support
    • API Performance
    • Heatmaps
    • Page Performance
    • Seen/Unseen Sessions
    • Public Session URL
  • FAQs
    • Install Zipy
    • Session Replay Definition
    • Error Tracking
    • Error Classification
    • Environment Support
    • Impact on your App
    • Performance Impact
    • Mobile Support
    • Network Data Capture
    • API Performance Diagnostic Help
      • High DNS Time
      • High SSL Connection Time
      • High Connection Setup Time
      • Large API Response Size
      • High Response Time
      • Compression Not Enabled
      • Server side API Failures
      • Client side API Failures
      • Insecure Connections
  • Troubleshooting
    • Errors in npm
    • Network header missing in Zipy
    • Can't see user data in sessions
    • No recordings or errors visible
    • No network timing split available
  • Product Videos
    • Ask AI
    • Getting Started
    • Session Replay
    • Multiple Project Creation
    • Team Management
    • Alerting on Slack
    • Time Filters and Daily Alerts
    • Custom Identifiers
    • Ignore Errors
    • Identify Users
    • Dashboard
    • Resolve Errors
    • New Error Digest
    • Jira and Slack
    • Online/Offline Network Status
    • Zipy on Zipy
      • Zipy Product Roadmap
  • Whats new
    • Product Updates
  • Legal & Policy
    • Terms of Service
    • Privacy Policy
    • Fulfillment Policy
    • Cookie Policy
    • Acceptable Usage Policy
    • Zipy Sub Processor List
  • Integration
    • Azure DevOps
    • Factors
    • RB2B
    • Webflow
    • WordPress
    • Amplitude
    • Coralogix
    • DevRev
    • Drift
    • Errorception
    • Freshchat
    • Google Analytics
    • Heap
    • HelpScout
    • Honeybadger
    • Hubspot
    • Intercom
    • Mixpanel
    • New Relic
    • Pendo
    • Raygun
    • Rollbar
    • Segment
    • Sentry
    • Shopify
    • Sumo Logic
    • TrackJS
    • Zendesk
Powered by GitBook
On this page
  • Data Collection
  • Data Types
  1. Legal & Policy

Apple's privacy guidelines

Last updated 5 months ago

At Zipy, we prioritize user privacy and adhere to industry-standard privacy guidelines to ensure data security and transparency. Our infrastructure complies with SOC 2 Type II, GDPR, and we adhere to Apple’s App Store guidelines.

Data Collection

Zipy captures session replays to assist in debugging and improving product performance. We only capture data sent from our users. We do not sell or transfer any data shared by the users.

Sensitive Data

Sensitive user data, such as personally identifiable information (PII), by default masked or excluded. Additionally, Zipy also provides an any content from recording.

App Store Privacy Policies

All apps submitted to the App Store are reviewed based on various technical, design, and content criteria. It is important to ensure that your app complies with Apple’s requirements. For more details, refer to .

Zipy is designed to work seamlessly and should not interfere with your app submission or review process. We kindly recommend including the use of Zipy in your app’s privacy policy and ensuring to specify the types of data collected, as outlined by Apple.

Data Types

If you are using Zipy, here are the data types you should select when submitting your app:

Data Type
Collected (Yes/No/Not by default)

Contact Info

Yes

Financial Info

No

Location*

Yes

Sensitive Info

No

Contacts

No

User Content

Yes

Search History

No

Identifiers*

Not by default

Purchases

No

Usage Data

Yes

Diagnostics

Yes

Other Data

No

Note:

  1. Location* - Zipy collects coarse Location information - City, Region, and Country by default, we do not collect any real-time geolocation.

Zipy only collects the above marked (Yes) data by default, as defined by Apple. Where it is possible to send additional information as well to Zipy through our SDK which is customizable by the customer. If you choose to send additional information, please ensure that you select all applicable data type options.

App Tracking

Post the iOS 14.5 update, all the apps should adhere to the AppTracking Transparency framework for requesting tracking permission from users to access the iOS advertising identifier (IDFA).

Zipy does not use IDFA, hence we do not need to opt-in dialog in our SDK

As per Apple’s , companies submitting their apps to the App Store must fully understand and accurately indicate the data types they collect. This includes data gathered directly within your application as well as through any third-party tools you use.

Identifiers* - We capture this data only if the user passes to Zipy.

Any question? - Email us at

privacy policy
identifiers
support@zipy.ai
API to block
Apple's guidelines