Loading
How Chirpul handles data
What Chirpul collects, how platform data is used for verifiable collaboration, messaging, discovery, momentum, moderation, and security, and what controls members have over analytics and profile visibility.
This policy is written from the actual current Chirpul data model and should still be reviewed for launch jurisdiction, retention rules, and consent wording.
Chirpul collects account and profile information such as your name, username, email, avatar, professional role, skills, interests, social links, onboarding details, and account-provider metadata needed to authenticate you.
We also process collaboration data, including projects, roles, applications, invites, requests, updates, comments, posts, messages, reactions, bookmarks, notifications, attachments, and other content you create or receive through the service.
We use platform data to run the service, secure accounts, route notifications, support project collaboration, deliver messages and calls, personalize discovery, rank relevant builders and projects, and surface execution signals in the execution network.
We also use data for abuse prevention, moderation, reliability, analytics, troubleshooting, and to verify whether workflows such as project applications, provider linking, and role permissions were completed correctly.
Some information is public by default, such as public profile fields, public projects, project updates that are intentionally published into the feed, and posts you publish with public visibility.
Other information remains limited to the relevant participants or operators, including direct messages, private projects, role applications, internal project workflows, NDA acceptances, and some moderation records.
Chirpul may use providers such as cloud hosting, managed PostgreSQL, Redis, object storage, email delivery, error monitoring, GitHub, Google sign-in or location services, and analytics or observability tools to run the product.
These providers process data only for operational purposes such as account access, delivery, storage, location suggestion, security, debugging, abuse prevention, or product reliability. The exact providers may change as the platform moves from beta to production.
Chirpul stores engagement and discovery signals to improve search, feed quality, ranking, recommendation quality, and product reliability. This can include view, click, search, and interaction events tied to accounts, sessions, projects, posts, and other platform objects.
Where supported by the product, members can manage analytics and view-tracking related preferences from their settings.
We retain data for as long as necessary to provide the service, maintain account integrity, support active projects, comply with legal obligations, detect fraud, and preserve moderation or security history where justified.
Different categories of data may follow different retention periods depending on whether the data is user-visible content, operational telemetry, abuse evidence, or regulated business records.
Chirpul uses technical and organizational safeguards intended to protect account access, stored content, and platform operations. These include authentication controls, rate limiting, access checks, logging, and infrastructure-level protections.
No system is perfectly secure, so you should also protect your own account credentials, review connected accounts carefully, and notify us promptly if you suspect misuse.
Depending on your location and the way you use Chirpul, you may have rights to access, correct, delete, export, or object to certain uses of your personal information.
You can also manage some profile visibility, linked-account, notification, and analytics-related settings directly inside the product.
For privacy questions, correction, export, deletion, consent, or grievance requests, contact privacy@chirpul.com or support@chirpul.com. For security reports, contact security@chirpul.com.
When you contact us, include enough information to identify the account or content involved while avoiding unnecessary sensitive information in email.