Data, Replies & Retention

1. What is active and what is planned

Current: separate product databases, organization-scoped permissions, verified account connections, available explicit transfers, Orbit reply processing/intent research, Email reply categories and scheduling operations. WhatsApp is publicly Coming soon. Finder results are transient; it is not a permanent inbox.

Planned: a unified organization-specific signal system connecting the content sent, the prospect/context, send time and observed response, to estimate which content and timing may obtain a reply. That predictive system and continued analysis of closed workspaces are not switched on by these pages. They need verified data flows, controls, provider review and any separate lawful authorization before activation.

2. How replies are associated with records

The organization/workspace is the first boundary. Within it, the product uses the relevant connected LinkedIn account, mailbox or WhatsApp sender, provider message/conversation identifiers and available contact/campaign references. Email can use provider thread IDs and In-Reply-To/References headers; those identifiers are combined with the authorized mailbox and workspace context.

Orbit links inbound conversations to an organization, connected account and lead, distinguishes reliable provider event direction from possible self-echoes, and records the reply outcome. Email distinguishes human replies from bounces and automated/out-of-office messages and associates replies with campaign/sequence records where supported.

A match can be uncertain: people forward messages, share inboxes, change addresses or use different phone/profile identifiers. A name or company alone is not reliable proof that two records are the same person. Cross-product mapping requires explicit authorized transfer/linking and compatible identifiers; all products do not automatically share a single conversation database.

3. Current classification and actions

Available categories include interest, questions, objections/negative replies, generic responses, automated replies and opt-outs. Orbit may use local rules and a configured local or external model. Email uses its current reply-categorization rules and reporting. Different products have different capabilities; one classifier is not assumed to exist everywhere.

Reply processing can pause or complete sequences for human review, stop contact after a negative/opt-out signal and retain a minimal suppression record. A reply does not authorize unlimited further marketing. Delivery, read/open and click events can be missing, duplicated, delayed or generated by infrastructure rather than the recipient.

Classification is an inference. Review incorrect labels, respect a person’s express objection and do not override suppression based only on an optimistic score. Account/provider restrictions and lawful-outreach obligations still apply.

4. The proposed content, timing and response signal

For an enabled and authorized organization, the proposed input record would connect: the prospect/contact and business context; the organization and sender; campaign/sequence/step; message subject/body or a necessary feature representation; send time and relevant time zone; delivery outcome; reply time and type; and later operator-confirmed outcomes such as a booked meeting.

The analysis would compare the organization’s own historical outcomes to estimate response likelihood for content, timing or an audience segment. A useful output must disclose its source/time window and uncertainty. Sparse or biased data can make the score unreliable. An inferred likelihood is not a statement of the prospect’s actual private intention.

The intended boundary is the original customer organization. Its conversations, identifiable prospect history and learned signals must not be exposed to another customer, sold as a prospect feed or pooled into an Abontech-wide training set. Google-connected or otherwise restricted data must be excluded whenever provider rules do not permit the proposed use.

This proposal does not authorize automated sensitive-trait inference or significant eligibility decisions, and does not promise that a model is currently trained, accurate, deployed or able to predict an individual response.

5. After a member leaves or an organization closes

Member removal: the member’s access ends, while the active organization can retain its legitimate shared contacts, messages, campaign records and analysis. Disconnecting a sender: revoke the connection to stop new collection, while assessable historical records may remain. Whole-workspace closure: normal customer use stops and an authorized recovery request may be made within 30 days, subject to available data.

After the recovery window, Abontech intends to keep authorized organization-specific historical records/signals without a preset automatic expiry where a continuing lawful purpose is established. That means account closure alone is not a promise of deletion. It does not mean all raw records can lawfully be kept forever, or that provider-imposed shorter limits cease to apply.

Continued reply/content analysis after closure is a distinct planned purpose. It must not begin solely because the user accepted general terms. Before it is enabled, the organization must receive a specific notice and the required choice or other valid legal basis must be established. Consent, where used, must be optional, specific and withdrawable. The rights of prospects and restrictions on connected provider data remain applicable.

A verified erasure or restriction request is handled separately. We must identify affected raw records and derived signals, remove or restrict what the law requires, explain necessary exceptions, and ensure that restored backups or later imports do not defeat the request. Irreversibly anonymized statistics are different from hashed or pseudonymous prospect records; a hash alone is not anonymization.

6. Records that can remain for a limited purpose

Financial evidence may include credit ledger entries, transaction references and dispute outcomes. Agreement evidence includes the accepted version, digest, identity reference and timestamp. Security records can document abuse or unauthorized access. Suppression records can prevent a person who opted out from being contacted again. Retain only the fields needed for the applicable purpose, with restricted access and appropriate review.

These exceptions do not justify retaining every conversation indefinitely. No single retention period automatically covers all records or jurisdictions. Ask meet@abontech.com for the purpose and retention criteria for a specific record, or to exercise an applicable right.

7. What signup does and does not authorize

The unchecked agreement box is mandatory for new registration. The server rejects missing agreement or a stale/tampered policy version, and stores the accepted policy version, document digest and timestamp tied to the verified identity.

That record proves which agreement was accepted; it is not a waiver of mandatory rights, prospect consent, permission for shared/cross-customer training, or approval of an optional future post-closure pipeline. There is no promise that legal claims are impossible.

Related documents

Keep a copy of the version you accept. Your browser’s Print command can save this page as a PDF.