Data Retention

Access-token state supports the signed-in session. Token expiry and removal of the persisted browser entry are different events; server logs and account data have their own retention. Logout or clearing site storage removes the relevant local state according to the interface.

The published choice-record period is a maximum of 13 months. This concerns the stored consent choice, not every Google Analytics identifier or event. The Cookie Policy separately describes the analytics arrangement.

The sidebar_state interface cookie has a published seven-day lifetime. This preference does not determine how long any professional record is kept.

Session or token expiry controls authentication. It is distinct from account deletion, revocation of a provider connection and retention of security evidence.

The published onboarding token lifetime is 3,600 seconds. That validity period is not a deletion deadline for the registration or customer file.

Temporary browser-session values support sign-in, return navigation or an in-progress payment. Closing a tab normally ends that session storage; browser restoration behavior may differ. It does not erase server-side orders or business records.

Audio received for transcription is retained for its processing purpose, with any limited incident or legally required retention assessed separately. A recording held by a provider and a link stored in AlefOS are different objects. The project specifies the source and applicable retention; no universal audio deadline is inferred from message-body rules.

Published ingestion-buffer windows are up to 24 hours for messages and 48 hours for sessions or temporary raw-transcript buffers. Final call transcripts stored as professional records are separate; these buffer deadlines do not impose a global 30-day deletion rule on them.

Temporary IBOX access links expire at most five hours after creation, or twenty minutes after first successful reveal if earlier. Link expiry removes that access path; it is not the underlying message’s retention period.

Summaries, relationship information, missions and final records follow their specific purpose and lifecycle: current work, relevant relationship, accuracy, deletion instructions and applicable rights. A useful record can outlast its raw message body. No universal age-based purge is created, but professional memory does not justify indefinite retention of every detail or copy.

The published rolling window is 120 days from creation for WhatsApp text and semantic envelopes, including messages already analyzed, and 30 days for other IBOX bodies. Removal of bodies is distinct from deletion of associated metadata, analyses and final professional records.

Raw message bodies and the professional knowledge shared with a group are separate categories. The project’s retention instructions must identify each and the relevant trigger. A raw-body cleanup must not be presented as automatically erasing the group’s entire knowledge or overriding individual rights.

Indicators used to organize professional follow-up are retained for that purpose and reviewed against the relationship’s current relevance and accuracy. An indicator remaining technically active is not, by itself, a legal reason to retain all underlying information forever.

Contact data collected from authorized work flows follow the professional purpose and applicable information and rights requirements. No registration is needed to ask for access, correction or deletion. The existence of a contact signal alone does not justify unlimited retention.

Return or deletion of data processed for the Customer follows its choice under the DPA and the agreed exit arrangements. Backup copies pending their defined expiry remain restricted; deletion instructions apply again after recovery. Legal accounting records, necessary dispute evidence and security logs require separate limited purposes and periods. Disconnecting a provider or removing a member does not erase all company records.