What BHASM knows.
And what it never asks.
46 computed signals across 8 categories. The complete data inventory, the tier visibility model, and exactly what BHASM never uses — with the compliance posture that backs it.
The 46 computed signals
Eight categories. Every signal is computed at every tier — what changes by tier is visibility, not computation. Inspired by the GA4 model: the data has always been there; you unlock the surfaces.
Purchase patterns · 8 signals
- Days since last purchase
- Personal cycle (median)
- Cycle elapsed ratio
- Purchase velocity trend
- AOV trajectory (3-order rolling)
- Total spend (lifetime)
- Frequency band
- First-purchase recency
Silence intelligence · 6 signals
- Silence outcome history
- Silence pattern hash
- Personal silence floor
- Recovery probability
- Inferred silence reason
- Reason confidence
Relationship health · 7 signals
- Relationship balance
- Actions without response
- Sentiment veto state
- Customer state (5-class)
- Hold status + reason
- Last contact recency
- Last intervention outcome
Channel performance · 5 signals
- WhatsApp opt-in state
- Email opt-in state
- Per-channel reply rate
- Preferred channel
- Optimal send-time window
Behavioural profile · 8 signals
- Archetype (1 of 18)
- Archetype confidence
- Archetype arc (evolution)
- Discount receptivity
- Price sensitivity tier
- Discovery vs habitual ratio
- Social-signal responsiveness
- Quality-vs-deal tilt
World context · 4 signals
- World signal modifier (per city)
- Cultural event proximity
- Economic window state
- Disruption flag (3 tiers)
Digital signals · 5 signals (connectors)
- GA4 engagement score
- GA4 sessions (7-day)
- Cart abandon flag + value
- Page-view recency
- UTM attribution chain
Support & CRM · 3 signals (connectors)
- Open complaint flag
- Open dispute / chargeback
- Support ticket recency
What BHASM does NOT use
A retention tool's discipline is often clearer in what it refuses than in what it consumes.
- Age, gender, religion, ethnicity. Never collected. Never inferred. Never used for scoring.
- Device type, browser fingerprinting. Out of scope. We do not need it.
- Location beyond city tier. We use city-level intelligence (tier 1, 2, 3) for relevance. Never street, never IP triangulation.
- Income beyond purchase history. No third-party income enrichment. The customer's actual purchase pattern is the only spend signal.
- Social media data. No Facebook/Instagram/LinkedIn scraping. No social graph imports.
- Any third-party enrichment. No Clearbit. No ZoomInfo. No people-finder APIs. The data you bring is the data BHASM uses.
The tier visibility model
All 46 signals are computed at all tiers. What changes between tiers is what becomes visible and actionable.
| Signal class | Seed | Growth | Scale | Performance |
|---|---|---|---|---|
| Days silent · personal cycle | ✓ | ✓ | ✓ | ✓ |
| Urgency score | hidden | visible | visible | visible |
| Archetype | ✓ | ✓ | ✓ | ✓ |
| Score breakdown (5 factors) | hidden | visible | visible | visible |
| Relationship balance | hidden | visible | visible | visible |
| Channel performance | hidden | hidden | visible | visible |
| Disagree / override + tracking | hidden | hidden | visible | visible |
| Cohort comparison vs industry | hidden | visible | visible | visible |
| LTV curves by archetype + state | hidden | hidden | visible | visible |
| Full ROI attribution (causal model) | hidden | hidden | hidden | visible |
| All 46 raw signals via API | hidden | partial | full | full |
The intelligence was always there. The tier unlocks visibility — not computation. Seed-tier customers benefit from the same engine that powers Performance; they just see less of it.
Data you bring
| Connector | Signals added | Auth |
|---|---|---|
| Shopify | 12 signals: order history, cart, line items, customer state | OAuth or API key |
| GA4 | 8 signals: engagement, sessions, conversions, UTM | OAuth (Google) |
| Razorpay | 6 signals: payment history, failed payments, dispute state | API key |
| WooCommerce | 11 signals: same as Shopify minus 1 | REST API key |
| HubSpot / Pipedrive / Zoho CRM | 5 signals: contact state, last touch, deal pipeline | OAuth or API key |
| Plain CSV | Base signals only (name, email, last purchase, AOV) | Upload |
Connectors are additive. Connect more — the engine has richer signal. Connect only CSV — the engine still works, with the base intelligence layer alone.
Compliance
DPDP Act 2023 (India)
BHASM complies with the Digital Personal Data Protection Act, 2023 (India), GDPR (EU), and CCPA (California). Each is treated as an equal governance layer enforced by the law engine — not as primary vs. secondary.
- Consent. Every founder records DPDP consent at signup — the timestamp is logged in
clients.dpdp_consent_at. - Data minimisation. Only signals necessary for scoring are stored. No demographic enrichment.
- Right to access. Full data export is available from your account settings — returns customers, interventions, outcomes, reports, and voice edits as a JSON archive. See Privacy Policy for the exact data categories included.
- Right to deletion. Account deletion deletes all rows tied to the client within 72 hours.
- Data not sold. No data is ever sold, brokered, or licensed.
GDPR alignment
For global clients, BHASM aligns with GDPR. The export and deletion endpoints serve both DPDP and GDPR requests. Data is processed in regions consistent with each tenant's data residency requirements.
Data we never store
- Card data — never. Razorpay tokenises payment instruments; BHASM never sees raw card information.
- Passwords — hashed only (bcrypt, never plaintext, never transmitted in logs).
- OAuth refresh tokens — encrypted at rest, scoped per connector.
- Customer PII beyond what is necessary for messaging (name, contact channel, purchase history).