Snapshot 10634

Document
Trust center
URL
https://trust.embrace.io/
Fetched
HTTP status
200
Content type
text/html
Fetch mode
browser
Size
101156 bytes
SHA-256 (raw)
84c2bdb21edb03764d2527f71884848142af2dfa56593d24e62332d03c8f0540
SHA-256 (normalized text)
9c24521d6abbbc6cb0e5bfca7476e4c5e913c88f6fd412cfa0efae8e9c82fb4b

Raw (normalized text)

Scripts and page chrome removed; this is what change detection compares.

Skip to navigationSkip to main content
Embrace
Embrace bridges the gap for SRE and DevOps teams struggling to integrate insights from user-facing apps due to outdated tools. Built with a user-first focus and powered by OpenTelemetry, Embrace's mobile and web observability solution enables teams to capture essential data and understand real customer impact across systems.
support@embrace.io
Privacy PolicyOpens in new tab
Philosophy
At Embrace, we believe there is a wealth of actionable, nonintrusive data that, if collected responsibly and presented well, provides a wonderful opportunity for mobile teams to identify and solve the issues that lead to poor user experiences.
We collect data because mobile is a vast field of ever-changing variables. Without understanding exactly how users experienced an app across every session, it is impossible to discover every issue that affects them.
PII Policy
Embrace does not store user information. We are not in the business of collecting user information for the purpose of selling targeted advertising or data. We are 100% aligned to the interests of mobile teams and their users.
Embrace exists for one purpose — to provide mobile teams the data and enhanced support they need to ship the best apps possible. This data includes only what is necessary to monitor and debug mobile apps.
Device environment information. Examples include OS, region, app version, CPU, memory, battery, and network connectivity.
In-app technical events. Examples include views/activities, network calls, logs, and web views.
In-app user actions. Examples include taps, button presses, swipes, and user flows.
Compliance
SOC 2 Type II
GDPR
CCPA
Resources
View all
Documents
Architecture Diagram
SOC 2 Type II
Information Security Policy
Secure Development Policy
Legal
Terms of Service
Opens in new tab
Data Processing Addendum
Opens in new tab
Privacy Policy
Opens in new tab
Links
System Status
Opens in new tab
Documentation
Opens in new tab
GitHub
Opens in new tab
Controls
View all
Infrastructure security
Encryption key access restricted
Unique account authentication enforced
Production application access restricted
View 17 more Infrastructure security controls
Organizational security
Asset disposal procedures utilized
Portable media encrypted
Anti-malware technology utilized
View 8 more Organizational security controls
Product security
Data encryption utilized
Control self-assessments conducted
Penetration testing performed
View 2 more Product security controls
Internal security procedures
Continuity and Disaster Recovery plans established
Cybersecurity insurance maintained
Configuration management system established
View 27 more Internal security procedures controls
Data and privacy
Data retention procedures established
Customer data deleted upon leaving
Data classification policy established
Data collected
Device environment information. Examples include OS, region, app version, CPU, memory, battery, and network connectivity.
In-app technical events. Examples include views/activities, network calls, logs, and web views.
In-app user actions. Examples include taps, button presses, swipes, and user flows.
Customer personally identifiable information
Credit card information
Personal health information
Subprocessors
View all
Amazon Web Services
•
Cloud provider
United States, European Union
FAQ
Media
View all
Solve every mobile app issue with Embrace Opens in new tab