Privacy

Privacy Policy

 

Effective Date: March 5, 2026

 

This Privacy Policy describes how Playlog and its founding team ("we," "us," "our") collect, use, store, and protect information in connection with the Playlog platform, including our website, SDKs, APIs, dashboards, and related services (the "Service"). We take your trust seriously, and this Policy is designed to be transparent about our practices while reflecting the realities of building a modern, AI-powered analytics platform.

 

Playlog is a business-to-business (B2B) service. Our primary relationship is with you, the developer or organization integrating our SDKs ("Customer"). When your end users interact with applications that use Playlog, we process data on your behalf. This Policy addresses both our practices with respect to Customers and the data we process about their end users.

 

1. Information We Collect

 

1.1 Account Information

When you register for Playlog, we collect your name, email address, and authentication credentials (either directly or through Google OAuth). If you join through an invite code, we also record that association.

 

1.2 Event and Telemetry Data

When you integrate our SDKs into your applications, the Service collects event data generated by your end users' interactions. This includes:

• Behavioral events such as session starts, level completions, progression milestones, in-app purchases, ad interactions, and custom events you define

• Performance telemetry including frame rate, memory usage, boot time, and web vitals

• Device metadata such as operating system, device model, screen resolution, browser version, and network type

• Session information including session identifiers, timestamps, duration, and heartbeat signals

• Error and crash data including error types, stack traces, and contextual system state at the time of failure

 

1.3 Approximate Location Data

We derive approximate geographic information (country and region level) from IP addresses using third-party geolocation services. We do not collect precise GPS coordinates. Our SDKs respect the Do Not Track (DNT) browser signal, and we offer IP anonymization options that Customers can enable at their discretion.

 

1.4 Monetization Data

If you configure monetization tracking, the Service may collect metadata about in-app purchases, subscription events, and ad impressions. This includes product identifiers, price points, currencies, and transaction metadata. Playlog does not process or store payment card numbers, bank account details, or other financial instrument data.

 

1.5 Usage Data

We collect information about how you interact with the Playlog dashboard, including pages viewed, features used, queries submitted through our natural language interface, and analytical workflows performed.

 

2. How We Use Your Information

We use the information we collect for the following purposes:

Providing the Service. Processing events, generating analytics, producing dashboards, and delivering AI-powered insights including funnel analysis, cohort segmentation, error diagnostics, and revenue intelligence.

Improving the Service. Understanding usage patterns, diagnosing technical issues, optimizing performance, and enhancing our analytics capabilities.

 

Advancing our AI capabilities. This is worth explaining in detail. Our AI models — which power funnel discovery, error clustering, cohort analysis, revenue forecasting, and natural language querying — learn and improve through exposure to diverse analytical patterns. We use aggregated, de-identified signals derived from how the Service is used to refine these models.

 

The goal is simple: the more our platform understands about game analytics patterns in general, the better and more precise the insights we can deliver to each individual customer from day one. Your raw data is never shared with other customers, and model training relies on aggregate patterns rather than individual datasets.

 

Security and integrity. Detecting and preventing fraud, abuse, and unauthorized access to the Service.

Communications. Sending you service-related notices, responding to your inquiries, and providing product updates.

 

3. Data Storage and Security

 

3.1 Infrastructure

Your Data is stored on infrastructure provided by reputable cloud service providers, including Amazon Web Services (AWS) (compute and object storage), Supabase (managed PostgreSQL database, authentication, and edge functions), Upstash (managed Redis for real-time processing), and Render (API hosting). These providers maintain their own robust security certifications and compliance programs.

 

3.2 Security Measures

We implement industry-standard security measures to protect Your Data, including:

• Authentication via secure token-based systems (including OAuth 2.0) and API key validation on all SDK request

• Row-Level Security (RLS) policies that enforce strict project-level data isolation, ensuring you can only access data belonging to your projects

• Rate limiting, input validation, CORS enforcement, and domain verification on all API endpoints

• Query execution safeguards including statement timeouts and scope restrictions to prevent unauthorized data access

 

3.3 A Note on Encryption

 

We want to be upfront: while data is protected in transit using TLS/SSL encryption, event data at rest is not currently encrypted at the application level. This is a deliberate architectural decision. Playlog's AI agents need to process, query, and analyze your event data in real time and in batch — including natural language SQL generation, funnel computation, and error clustering — and application-level encryption would introduce latency and complexity that would meaningfully degrade the analytical experience. Data is protected through access controls, network-level security, and the infrastructure-level encryption offered by our cloud providers. As Playlog matures, we will continue to evaluate and enhance our encryption posture.

 

4. Data Sharing and Disclosure

We do not sell Your Data. We may share information in the following limited circumstances:

Service providers. We share data with the third-party infrastructure providers identified in Section 3.1, strictly as necessary to operate the Service. These providers are contractually obligated to protect the data they process on our behalf.

 

AI processing partners. Our AI features are powered by third-party large language model providers (currently Anthropic's Claude). When our AI agents process Your Data, relevant portions may be transmitted to these providers' APIs for inference. This processing is performed under our contractual terms with these providers, and your data is not used by them for their own model training.

 

Legal compliance.

We may disclose information if required by law, regulation, legal process, or governmental request, or if we believe in good faith that disclosure is necessary to protect our rights, your safety, or the safety of others.

 

Business transfers.

If Playlog is incorporated, acquired, merged, or restructured, Your Data will be transferred as part of that transaction. We will provide notice before Your Data becomes subject to a different privacy policy.

 

5. Your Rights and Choices

 

5.1 Customer Controls

As a Customer, you have control over the data collected through your integration:

• You can configure privacy settings in our SDKs, including enabling Do Not Track respect, IP anonymization, and text masking

• You can define which events are tracked and which elements are excluded from data collection

• You can request deletion of Your Data by contacting us, subject to our data retention obligations

 

5.2 End User Rights

If you are an end user of an application that uses Playlog, your relationship is primarily with the application developer (our Customer). Please contact the developer directly to exercise your privacy rights. We will cooperate with our Customers to fulfill valid data subject requests.

 

5.3 Data Portability

You may request an export of Your Data in a machine-readable format. We will fulfill such requests within a commercially reasonable timeframe.

 

6. International Data Transfers

Our infrastructure is primarily hosted in the United States. If you are accessing the Service from outside the United States, you acknowledge that Your Data may be transferred to, stored, and processed in the United States and other jurisdictions where our service providers operate. We rely on the data protection measures described in this Policy and in our service provider agreements to safeguard data during international transfers.

 

7. Children's Privacy

Playlog is a B2B service intended for use by professional developers and organizations. We do not knowingly collect personal information directly from children under 13 (or other age thresholds under applicable law, such as 16 under GDPR). If a Customer integrates Playlog into an application directed at children, the Customer is responsible for ensuring compliance with applicable children's privacy laws, including COPPA and equivalent regulations.

 

8. Cookies and Tracking Technologies

The Playlog dashboard may use session cookies and similar technologies for authentication and functionality purposes. Our SDKs use session identifiers and local storage mechanisms to maintain session state within your applications. We do not use third-party advertising cookies or cross-site tracking technologies.

 

9. Data Retention

We retain Your Data for as long as your account is active or as needed to provide the Service. Real-time processing data (such as session state and funnel progress) is retained temporarily with defined time-to-live policies. Analytical and aggregate data may be retained longer to support trend analysis and historical reporting. Upon account termination, we will delete or anonymize Your Data in accordance with our Terms of Use.

 

10. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, or legal requirements. When we make material changes, we will notify you by updating the Effective Date and providing notice through the Service. We encourage you to review this Policy periodically.

 

11. Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us at:

Email: team@playlog.ai Website: playlog.ai

 

This document was last reviewed on March 5, 2026. Playlog is an unincorporated project. This Privacy Policy will be updated as our organizational and legal structure evolves.

Turn player signals into revenue actions

Join the waitlist and we will keep you in the loop when we are live.

Playlog

© Playlog 26-27

team@playlog.ai

LinkedIn

Terms

Privacy

Playlog

Schedule Demo

Privacy

Privacy Policy

 

Effective Date: March 5, 2026

 

This Privacy Policy describes how Playlog and its founding team ("we," "us," "our") collect, use, store, and protect information in connection with the Playlog platform, including our website, SDKs, APIs, dashboards, and related services (the "Service"). We take your trust seriously, and this Policy is designed to be transparent about our practices while reflecting the realities of building a modern, AI-powered analytics platform.

 

Playlog is a business-to-business (B2B) service. Our primary relationship is with you, the developer or organization integrating our SDKs ("Customer"). When your end users interact with applications that use Playlog, we process data on your behalf. This Policy addresses both our practices with respect to Customers and the data we process about their end users.

 

1. Information We Collect

 

1.1 Account Information

When you register for Playlog, we collect your name, email address, and authentication credentials (either directly or through Google OAuth). If you join through an invite code, we also record that association.

 

1.2 Event and Telemetry Data

When you integrate our SDKs into your applications, the Service collects event data generated by your end users' interactions. This includes:

• Behavioral events such as session starts, level completions, progression milestones, in-app purchases, ad interactions, and custom events you define

• Performance telemetry including frame rate, memory usage, boot time, and web vitals

• Device metadata such as operating system, device model, screen resolution, browser version, and network type

• Session information including session identifiers, timestamps, duration, and heartbeat signals

• Error and crash data including error types, stack traces, and contextual system state at the time of failure

 

1.3 Approximate Location Data

We derive approximate geographic information (country and region level) from IP addresses using third-party geolocation services. We do not collect precise GPS coordinates. Our SDKs respect the Do Not Track (DNT) browser signal, and we offer IP anonymization options that Customers can enable at their discretion.

 

1.4 Monetization Data

If you configure monetization tracking, the Service may collect metadata about in-app purchases, subscription events, and ad impressions. This includes product identifiers, price points, currencies, and transaction metadata. Playlog does not process or store payment card numbers, bank account details, or other financial instrument data.

 

1.5 Usage Data

We collect information about how you interact with the Playlog dashboard, including pages viewed, features used, queries submitted through our natural language interface, and analytical workflows performed.

 

2. How We Use Your Information

We use the information we collect for the following purposes:

Providing the Service. Processing events, generating analytics, producing dashboards, and delivering AI-powered insights including funnel analysis, cohort segmentation, error diagnostics, and revenue intelligence.

Improving the Service. Understanding usage patterns, diagnosing technical issues, optimizing performance, and enhancing our analytics capabilities.

 

Advancing our AI capabilities. This is worth explaining in detail. Our AI models — which power funnel discovery, error clustering, cohort analysis, revenue forecasting, and natural language querying — learn and improve through exposure to diverse analytical patterns. We use aggregated, de-identified signals derived from how the Service is used to refine these models.

 

The goal is simple: the more our platform understands about game analytics patterns in general, the better and more precise the insights we can deliver to each individual customer from day one. Your raw data is never shared with other customers, and model training relies on aggregate patterns rather than individual datasets.

 

Security and integrity. Detecting and preventing fraud, abuse, and unauthorized access to the Service.

Communications. Sending you service-related notices, responding to your inquiries, and providing product updates.

 

3. Data Storage and Security

 

3.1 Infrastructure

Your Data is stored on infrastructure provided by reputable cloud service providers, including Amazon Web Services (AWS) (compute and object storage), Supabase (managed PostgreSQL database, authentication, and edge functions), Upstash (managed Redis for real-time processing), and Render (API hosting). These providers maintain their own robust security certifications and compliance programs.

 

3.2 Security Measures

We implement industry-standard security measures to protect Your Data, including:

• Authentication via secure token-based systems (including OAuth 2.0) and API key validation on all SDK request

• Row-Level Security (RLS) policies that enforce strict project-level data isolation, ensuring you can only access data belonging to your projects

• Rate limiting, input validation, CORS enforcement, and domain verification on all API endpoints

• Query execution safeguards including statement timeouts and scope restrictions to prevent unauthorized data access

 

3.3 A Note on Encryption

 

We want to be upfront: while data is protected in transit using TLS/SSL encryption, event data at rest is not currently encrypted at the application level. This is a deliberate architectural decision. Playlog's AI agents need to process, query, and analyze your event data in real time and in batch — including natural language SQL generation, funnel computation, and error clustering — and application-level encryption would introduce latency and complexity that would meaningfully degrade the analytical experience. Data is protected through access controls, network-level security, and the infrastructure-level encryption offered by our cloud providers. As Playlog matures, we will continue to evaluate and enhance our encryption posture.

 

4. Data Sharing and Disclosure

We do not sell Your Data. We may share information in the following limited circumstances:

Service providers. We share data with the third-party infrastructure providers identified in Section 3.1, strictly as necessary to operate the Service. These providers are contractually obligated to protect the data they process on our behalf.

 

AI processing partners. Our AI features are powered by third-party large language model providers (currently Anthropic's Claude). When our AI agents process Your Data, relevant portions may be transmitted to these providers' APIs for inference. This processing is performed under our contractual terms with these providers, and your data is not used by them for their own model training.

 

Legal compliance.

We may disclose information if required by law, regulation, legal process, or governmental request, or if we believe in good faith that disclosure is necessary to protect our rights, your safety, or the safety of others.

 

Business transfers.

If Playlog is incorporated, acquired, merged, or restructured, Your Data will be transferred as part of that transaction. We will provide notice before Your Data becomes subject to a different privacy policy.

 

5. Your Rights and Choices

 

5.1 Customer Controls

As a Customer, you have control over the data collected through your integration:

• You can configure privacy settings in our SDKs, including enabling Do Not Track respect, IP anonymization, and text masking

• You can define which events are tracked and which elements are excluded from data collection

• You can request deletion of Your Data by contacting us, subject to our data retention obligations

 

5.2 End User Rights

If you are an end user of an application that uses Playlog, your relationship is primarily with the application developer (our Customer). Please contact the developer directly to exercise your privacy rights. We will cooperate with our Customers to fulfill valid data subject requests.

 

5.3 Data Portability

You may request an export of Your Data in a machine-readable format. We will fulfill such requests within a commercially reasonable timeframe.

 

6. International Data Transfers

Our infrastructure is primarily hosted in the United States. If you are accessing the Service from outside the United States, you acknowledge that Your Data may be transferred to, stored, and processed in the United States and other jurisdictions where our service providers operate. We rely on the data protection measures described in this Policy and in our service provider agreements to safeguard data during international transfers.

 

7. Children's Privacy

Playlog is a B2B service intended for use by professional developers and organizations. We do not knowingly collect personal information directly from children under 13 (or other age thresholds under applicable law, such as 16 under GDPR). If a Customer integrates Playlog into an application directed at children, the Customer is responsible for ensuring compliance with applicable children's privacy laws, including COPPA and equivalent regulations.

 

8. Cookies and Tracking Technologies

The Playlog dashboard may use session cookies and similar technologies for authentication and functionality purposes. Our SDKs use session identifiers and local storage mechanisms to maintain session state within your applications. We do not use third-party advertising cookies or cross-site tracking technologies.

 

9. Data Retention

We retain Your Data for as long as your account is active or as needed to provide the Service. Real-time processing data (such as session state and funnel progress) is retained temporarily with defined time-to-live policies. Analytical and aggregate data may be retained longer to support trend analysis and historical reporting. Upon account termination, we will delete or anonymize Your Data in accordance with our Terms of Use.

 

10. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, or legal requirements. When we make material changes, we will notify you by updating the Effective Date and providing notice through the Service. We encourage you to review this Policy periodically.

 

11. Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us at:

Email: team@playlog.ai Website: playlog.ai

 

This document was last reviewed on March 5, 2026. Playlog is an unincorporated project. This Privacy Policy will be updated as our organizational and legal structure evolves.

Turn player signals into revenue actions

Join the waitlist and we will keep you in the loop when we are live.

Playlog

Schedule Demo