Salesforce
Data Residency and PII
Salesforce is the durable home for personal data in a Forge deployment. This page explains what is stored where, for how long, and what you can do as an admin to limit it.
PII policy
Names, email addresses, phone numbers and postal addresses are fetched from Salesforce just in time and held briefly in a short-lived cache. They are not kept in Forge's database record cache. Three deliberate, narrow exceptions exist: a mirror of Contact name, email and title used for staff and speaker lookups (skipped for orgs with more than 50,000 Contacts); Activation Workflow conversation transcripts, which are sealed and purged on a schedule; and SMS Conversations content for orgs that choose Forge as the SMS system of record.
What counts as PII
| Data type | PII? | Where it lives |
|---|---|---|
| Person name (first, last, full) | Yes | Salesforce Contact, Lead or Attendee. Briefly in the short-lived cache. Contact names are also in the staff and speaker lookup mirror. |
| Email address | Yes | Salesforce Contact, Lead or Attendee. Briefly in the short-lived cache. Contact email is also in the staff and speaker lookup mirror. |
| Phone number | Yes | Salesforce Contact, Lead or Attendee. |
| Postal address | Yes | Salesforce Contact or Lead. |
| Salesforce record IDs | No | Forge database (audience lists, audit logs, record cache). |
| Counts, statuses and aggregates | No | Forge database and short-lived cache. |
| Timestamps and durations | No | Forge database (audit logs, scheduled jobs). |
| Feature flags and settings | No | Forge database or short-lived cache. |
| Email templates (HTML with merge tokens) | No | Forge database. Merge values are fetched from Salesforce at send time. |
| Company and account names | No | Forge database (audience members store the company name only). |
Storage and handling by system
| System | What it stores | How long |
|---|---|---|
| Salesforce | All customer records: events, attendees, contacts, leads, forms, answers, transactions, speakers, sponsors. | Indefinitely. Your org controls retention. |
| Forge database | Org connection and users (Forge user email and Salesforce user ID), encrypted OAuth refresh tokens, sessions, audience definitions and ID-only audience member lists, email job definitions, audit logs, object mapping, and a read cache of non-personal record fields. | Org data until the org is disconnected. Read cache refreshed on a schedule. Audit logs are not purged automatically. |
| Short-lived cache (Redis) | Attendee display names and emails (keyed by org and event), contact profiles, in-progress checkout sessions, email suppression lists, plus describe metadata, layouts, feature flags and picklist values. | Attendee data up to 2 hours by default; a checkout session 15 minutes by default; other entries minutes. If Redis is unavailable Forge falls back to a short-lived in-process cache with the same lifetimes. |
| Forge logs | Org ID, Salesforce record IDs, error codes and HTTP status. PII is redacted before a log entry is written. | Per infrastructure log retention. |
| Email provider | The recipient email address during delivery, and a suppression list for bounces and unsubscribes (address only). | Short-lived during delivery. The suppression list is kept for bounce and unsubscribe management. |
Scenario: attendee list
When a planner opens the Attendees tab, Forge checks the short-lived cache for a list that is under two hours old. If there is none, Forge queries conference360__Attendee__c in Salesforce, hydrates the names and emails, caches them for up to two hours and returns them to the browser. The names and emails are not written to Forge's database.
Scenario: registration form submission
When an attendee submits a registration form, Forge validates the answers in memory and writes them to Salesforce (conference360__Form_Submission__c and conference360__Form_Submission_Answer__c). Answers that map to Contact or Lead fields are written to those standard objects. While the checkout is in progress, the registrant's details are held in a short-lived checkout session (15 minutes by default) so the payment step can complete.
Scenario: email campaign send
Email send jobs store only the Salesforce IDs of recipients (Contact, Lead or Attendee) in Forge's database. When a job runs, Forge fetches the email addresses from Salesforce, sends through the email provider and discards the addresses. No recipient email list is written to the database.
Scenario: data export
Exports (CSV downloads of attendees, registrations or reports) are streamed from Salesforce through Forge to the browser and are not saved in Forge's storage.
Audience segments and ID-only snapshots
An audience segment is a filter, for example all Registered attendees for events in 2025. When a segment is used for a send, Forge stores only the Salesforce IDs of the matching records (plus a company name for business contacts), not names, emails or phone numbers. Personal data is fetched from Salesforce when the job runs.
Beacon (AI copilot) — data handling
| Data type | How Beacon handles it |
|---|---|
| Salesforce records queried during a session | Queried live per request — never bulk-synced or stored outside Salesforce. |
| Conversation history | Moving to your Salesforce org before general availability. Email and phone numbers are pseudonymized wherever conversation data is processed outside Salesforce. |
| Knowledge base | Contains only Blackthorn product and help content — no customer personal data. |
| Cross-customer isolation | Each Salesforce org is fully isolated; no cross-customer data sharing or AI training on customer data. |
Cache contract
- Salesforce org ID and record IDs are the primary cache key parts, so one org's cached data cannot be returned to another.
- Attendee name and email are cached for up to 2 hours under keys scoped to the org and event. They expire on their own and are not copied to the database.
- If Redis is unavailable, Forge falls back to a short-lived in-process cache with the same lifetimes.
- Queued Salesforce writes (the write outbox) keep their payload only until Salesforce confirms; the payload is emptied the moment the row is done or dead, and finished rows are deleted by a cleanup job shortly after.
Admin recommendations
| To achieve... | Do this | Why |
|---|---|---|
| Limit who can see attendee personal data | Remove Read on the attendee name, email and phone fields from permission sets that do not need them, in Salesforce. | Forge checks each person's field-level security and hides fields they cannot read, so Salesforce stays the single place you control access. |
| Answer a deletion or access request | Delete or export the person's Contact, Lead and Attendee records in Salesforce. | Salesforce holds the personal data. Short-lived caches expire within their lifetimes, and the Contact lookup mirror refreshes on the next sync. |
| Keep personal data out of exports | Export only the columns you need and handle the CSV under your own data policy. | Attendee exports include email and phone. |
| Shorten how long attendee data is cached | Ask Blackthorn support to lower the attendee-data and display-name lifetimes for your org. | Each lifetime can be capped per org (down to not caching at all, with checkout sessions never below 5 minutes). It only ever shortens the default. |
| Confirm what Forge copies for an org with a very large Contact base | Check the Contact count in Salesforce. Above 50,000 Contacts, the staff and speaker lookup mirror is skipped and names are looked up live. | Mirroring a very large Contact table would slow the database, so Forge turns it off. |
Data deletion and export requests
Because Forge holds Salesforce IDs and non-personal operational state, a deletion request is satisfied by deleting the records in Salesforce, which is the durable store of personal data. Forge's rows for a disconnected org are purged when the org is disconnected. Contact your Blackthorn support rep if you need a written data-processing agreement.