Pagerly Data Processing & Subprocessor Information

‍

Effective Date: 25th September, 2024
Company: Sassly Technologies Private Limited (Pagerly)

1. Data Handling Clarifications

Slack and Microsoft Teams Messages

Pagerly does not store, retain, or archive any Slack or Microsoft Teams messages.

Pagerly only processes limited metadata required to provide the Services, such as:

  • User identifiers
  • Email-to-username mapping
  • Workspace metadata obtained via platform APIs

No message content from collaboration platforms is persisted in Pagerly systems.

This approach minimizes data exposure and supports privacy-by-design principles.

Data Retention and Deletion

Upon account deactivation or removal of the Pagerly application from a workspace, Customer Personal Data is retained for up to 30 days to allow for:

  • Account reactivation
  • Recovery requests
  • Operational continuity

After this period:

  • Personal Data is permanently deleted, or
  • Irreversibly anonymized from active systems

Encrypted backup copies may persist temporarily until automatically overwritten according to backup lifecycle policies.

2. Subprocessors

Pagerly, operated by Sassly Technologies Private Limited, uses trusted third-party service providers (“Subprocessors”) to support the delivery of our services.

We carefully select subprocessors that implement strong security and privacy protections.

Infrastructure & Hosting
Amazon Web Services, Inc. (AWS)

Purpose:

  • Cloud infrastructure hosting
  • Database storage
  • Backup and disaster recovery
  • Networking and security services

Data Location: United States and other AWS regions as required.

Collaboration Platform Integrations
Slack Technologies, LLC (a Salesforce company)

Purpose:

  • Integration with Slack APIs
  • Retrieval of workspace metadata (user identifiers, email mapping, channel metadata)
  • Bot functionality delivery

Pagerly does not store Slack message content.

Microsoft Corporation (Microsoft Teams)

Purpose:

  • Integration with Microsoft Teams platform
  • Retrieval of user and workspace metadata necessary for service functionality

Pagerly does not store Microsoft Teams message content.

Payment Processing

Stripe, Inc.

Purpose:

  • Payment processing
  • Subscription management
  • Billing operations

Pagerly does not store credit card information.
All payment data is processed directly by Stripe.

Optional Customer-Enabled Integrations

Pagerly supports integrations that customers may enable voluntarily. Examples include:

  • PagerDuty
  • Opsgenie
  • Ticketing and incident management tools

Data shared depends entirely on customer configuration and authorization.

3. Subprocessor Security Requirements

All subprocessors are required to:

  • Maintain appropriate technical and organizational security measures
  • Process Personal Data only for authorized purposes
  • Comply with applicable data protection regulations
  • Maintain confidentiality obligations

4. Subprocessor Changes

Pagerly may update this subprocessor list from time to time as services evolve.

Customers may request the latest list by contacting:

📧 hello@pagerly.io

5. Security Commitment

Pagerly maintains an information security program aligned with ISO 27001 standards and follows industry-recognized security practices, including:

  • Encryption in transit (TLS 1.2+)
  • Encryption at rest
  • Access controls and least-privilege policies
  • Monitoring and logging
  • Backup and recovery procedures
  • Vulnerability management and patching

6. Contact Information

For privacy or data protection inquiries:

Pagerly / Sassly Technologies Private Limited
📧 hello@pagerly.io

‍

‍