Privacy Notice

Calder is a Beta professional relationship and growth product. This notice explains the current Beta privacy approach in plain language. It deliberately avoids claiming certifications, exact retention periods, legal bases, transfer safeguards or company-registration details that have not yet been launch-finally verified.

Who handles privacy requests

During the Beta, privacy requests are handled by the Calder project team through the in-product support channel. Launch-final controller and business-identity details must be confirmed and published before commercial launch.

Data we currently use

Depending on the features you use, Calder may process account and authentication data; profile and professional information you choose to provide; invite and referral records; Mission participation and verification state; Credits/Gems ledger records; notification and product-news state; company/team information; support requests; and limited operational or analytics data needed to run and improve the Beta.

Do not submit passwords, provider secrets or unnecessary sensitive personal information through ordinary profile, Mission or support fields.

Calder Mission Companion

If you install Calder Mission Companion, the browser extension is limited to Calder and LinkedIn pages needed for the active Mission flow. It observes the active Mission target URL and limited page state needed to determine whether a required manual action, such as a reaction or comment submission, was already present before the Mission or was performed after the Mission started.

The Companion stores bounded Mission and interface context locally in browser extension storage so it can show the active Mission, connection state, required actions, Calder member display identity, interface preferences, available-Mission and Credit summaries, and a small recent-notification preview.

For Mission verification, Calder receives bounded evidence such as the action type, observation time, confidence or technical signals, and the active LinkedIn post URL. The Companion does not collect or send LinkedIn passwords, authentication cookies or session tokens, private messages, contact lists, or the text of comments you type on LinkedIn.

The Companion does not automatically Like, Comment, Repost, Follow, Connect or Message on LinkedIn. The member performs third-party-platform actions manually.

Why we use it

We use data to provide and secure your account, operate invite-only access, deliver profile and Mission workflows, maintain balances and audit-relevant product state, provide support, prevent misuse, diagnose failures and understand whether the Beta creates useful repeated value. Any launch-final lawful-basis mapping will be published after legal review rather than invented here.

Service providers and transfers

The Beta uses external infrastructure and service providers for hosting, database/authentication, security or abuse checks, and customer support. Some providers may process data in other countries. Calder will document launch-final subprocessors and applicable transfer safeguards after the operating-entity and legal review is complete.

Storage, cookies and similar technologies

Calder uses necessary browser storage, cookies or similar technologies for authentication, security, language/theme preferences and core product operation. We do not use this Beta notice to claim a marketing-cookie setup that has not been verified.

Retention and deletion

Data is kept only for as long as needed for Beta operation, account/security needs, disputes, audit or ledger integrity, and applicable legal obligations. Exact category-specific retention periods are not asserted in this Beta draft because they are still being governed separately. Some authoritative ledger, security or audit records may need to be retained or anonymized rather than simply deleted.

Your rights

Where GDPR or other applicable data-protection law gives you rights, these may include access, correction, deletion, restriction, objection and portability. Rights can depend on the purpose and legal basis. Use the Calder support channel to make a privacy request during Beta.

Security and Beta limits

Calder uses server-side authorization, row-level data controls and other security boundaries as part of the current architecture. No online service can promise absolute security. The Beta is under continuous development and may change while safeguards are improved and verified.

Children and changes

Calder is not designed as a children’s service. A launch-final eligibility/age rule must be confirmed before commercial launch. We may update this notice as the Beta, providers and legal operating model change; the displayed effective date should be reviewed with each material update.