Yirla Data Privacy & Security Architecture

Overview: Security by Design

Yirla is engineered to provide enterprise-grade ad intelligence while minimizing data exposure. Our architecture is built on minimal, time-bound retention: we keep only the advertising performance data needed to deliver insights, for 90 days by default, and then it is deleted.

Design Principles

1. Complete Coverage

Every meaningful action—user, system, admin, or cloud—is logged.

2. Centralization

All application and audit logs flow through a single aggregation layer for visibility and alerting.

3. Immutability

Final audit logs are stored in WORM storage (S3 Object Lock). Even admins cannot alter history.

4. Least Privilege Access

Only a small, audited group can view logs. No write/delete permissions.

5. Separation of Concerns

Production systems, logging, and long-term audit archives live in separate trust zones.

Core Security Pillars

To protect $250k+ monthly ad portfolios, Yirla implements multi-layered security protocols across the entire data lifecycle.

1. Time-Bound Retention Analysis Engine

Unlike traditional reporting tools that warehouse your data indefinitely, Yirla generates insights at runtime and retains data for 90 days by default.

Time-Bound Storage: Raw campaign data is stored immutably for audit and debugging, and transformed/aggregated datasets are used for analytics. Default retention is 90 days, configurable per customer. Customers can request deletion at any time, and deletes propagate across raw, derived, and backup layers.
Stored Results: Analysis results and recommendations are stored with the customer’s data under the same 90-day default retention, so insights stay available in Yirla over time.

* Reduced Blast Radius: By storing data only for 90 days by default, we materially reduce the risk and compliance overhead for enterprise IT teams.

2. Encryption & Data Handling

All data handled by Yirla is protected using industry-standard cryptographic protocols:

* Encryption at Rest: Any temporary operational data is secured using AES-256 encryption.

* Encryption in Transit: All communication between Yirla, ad platforms (LinkedIn, Google), and the end-user is encrypted via TLS 1.2+.

* Secure API Integration: Yirla connects to ad platforms via secure, permissioned Oauth2 APIs with read-only access.

3. AI Governance & Privacy

Yirla ensures that your proprietary ad strategy is never used to train third-party models:

* Data Isolation: Customer data is processed in isolated environments and is not transmitted to third-party models for training purposes.

* Non-PII Processing: Our AI analyzes campaign-level signals (spend, impressions, hooks) and does not access user identity data, contact records, or CRM-level PII.

Access Control & Governance

* Permission-Based Access: Access is logged and fully controlled by the customer. You can revoke Yirla’s access at any time through the underlying ad platform.

* Organization Isolation: Designed with strict account isolation to support individual teams, enterprises, and agencies without data leakage.

* Role-Based Access Control (RBAC): Supports enterprise identity providers for secure authentication and internal permission management.

Compliance Readiness

Yirla's "minimal data" architecture is designed to simplify compliance with global regulations:

GDPR & CCPA: By avoiding the collection of PII and storing only advertising performance metadata, Yirla aligns with privacy-first data handling standards.

* Audit Readiness: Permission-based access and activity logging provide the transparency required for internal security reviews.