Salesforce-Native Financial Planning Security

1 · Built on Salesforce

A world-class platform, applied to every plan

Financial Planner runs natively on Salesforce. It uses platform security capabilities you already operate — identity, role-based access, permissions, sharing, auditability, and trusted infrastructure — instead of a second planning cloud.

Identity

Advisors sign in with Salesforce. Your org's SSO, MFA, sessions, and user lifecycle apply to planning the same way they apply to every other Lightning app.

Role-based access

Profiles, permission sets, and sharing rules decide who can open a plan. Packaged FinPlan Admin and FinPlan User sets are assigned by your admins — least privilege, not a parallel ACL.

Permissions, sharing, and audit

CRUD, field-level security, org-wide defaults, and audit history stay on the Salesforce model you already operate. Planning does not invent a second permission system.

Trusted infrastructure

The app runs on Salesforce's platform — the security, compliance, privacy, and availability Salesforce publishes at Trust — instead of a vendor-operated planning cloud.

See how Salesforce publishes Trust — trust.salesforce.com

2 · AppExchange Security Review

Passed Salesforce AppExchange security review

Salesforce uses AppExchange security review to evaluate partner offerings before listing them. Financial Planner has passed that review.

3 · Customer data handling

What we access, where it lives, and what never leaves

This is usually the first question in a security review. Household planning data stays in your org. Stratus does not host a copy, and there is no planning subprocessor to add to your register.

What the app uses

Financial Plan records and related planning objects — accounts, assets, real estate, income, debt, expenses, money flows, insights, projection results, and Monte Carlo runs. Contacts can be linked as plan owners. CRM balances are not copied automatically.

Where it is stored

In your Salesforce org. Plans, projections, and explorer results never leave the platform. Stratus does not operate a separate datastore for subscriber planning records.

Subprocessors

None for planning data. Normal operation makes no outbound callouts to a planning host. Website, email, and support tools Stratus uses for sales and tickets sit outside that boundary and are covered in a DPA on request.

4–7 · Access, authentication, encryption, monitoring

The controls you already run still apply

Least privilege, Salesforce identity, platform encryption, and admin visibility — with no extra OAuth grant and no passwords stored by Stratus.

Access control

Least-privilege by design: admins assign FinPlan Admin or FinPlan User. Record access follows Salesforce profiles, permission sets, sharing rules, and CRUD/FLS. There is no connected-app OAuth grant and no extra scope to approve.

Authentication

Financial Planner uses Salesforce identity. It supports the SSO and MFA patterns your org already requires and does not store Salesforce user passwords. It is not a connected app, so it does not add its own OAuth, OpenID Connect, or SAML flow.

Encryption

Data in transit uses Salesforce TLS. Data at rest uses Salesforce platform encryption. If your org enables Shield Platform Encryption, planning records stay in that org and remain compatible. The package does not hold external API secrets for a planning vendor.

Monitoring and auditability

Admins review activity with Salesforce audit trails and, where licensed, Event Monitoring and Field Audit Trail. Projection runs also keep in-app run history so operators can see when calculations executed.

8 · Secure development

A managed package that passed Salesforce security review

Financial Planner is compiled and locked as a Salesforce managed package. Releases follow the security bar Salesforce sets for AppExchange listings.

Secure code review on package changes before they are submitted.
Static analysis and Salesforce security-review requirements for Apex, Lightning, and data-access patterns.
Vulnerability remediation as part of preparing each public distribution.
Responsible disclosure: sales@stratuscloudsolutions.com

9 · Compliance and Trust resources

Verify the platform. Request what you need from Stratus.

Planning data inherits your Salesforce org's attestations. Use Salesforce Trust and Compliance for platform evidence, then request Stratus privacy, DPA, and security contacts for everything outside the org.

Salesforce Trust Platform security, privacy, compliance, and availability — including status transparency. Salesforce compliance documents SOC, ISO, and other attestations for covered Salesforce services. Confirm your edition. Privacy Policy How Stratus handles website, sales, and support information — separate from org planning data. Data Processing Agreement Request a DPA for support and any Stratus activity outside Salesforce. Planning records stay in your org. Security contact Report a security concern or request a walkthrough for your review team. Subprocessor list None for planning data. Website and support subprocessors are disclosed in the DPA.

For IT and the business

What this means for leaders

Security review gets smaller. Advisors stay in Lightning. Client data stays on the platform the firm already trusts.

For IT and security leaders

A smaller review, not a new vendor cloud

You already secured Salesforce. Financial Planner keeps household planning inside that boundary, so the review is about an app — not a data pipeline.

Reuse identity, sharing, monitoring, and data residency you already operate.
Assign packaged FinPlan Admin and FinPlan User permission sets — no parallel access model.
Compatible with Shield, Event Monitoring, and Field Audit Trail if your org uses them.

For business leaders

Client confidence stays with the system of record

Advisors plan in Lightning, on the platform the firm already bought. Sensitive household data does not move to a second login or a second vendor.

Procurement is simpler: you are adding native capability, not a new place that stores client finances.
Advisors stop reconciling CRM with an external planning portal.
World-class Salesforce Trust is the foundation — Financial Planner is built to use it, not bypass it.

For your reviewer

Questions a security or IT review will ask

Does planning data leave Salesforce?

No. Household records, projections, and explorer results are stored in your Salesforce org. Financial Planner is a native managed package, not an external planning portal and not a copy of client data in another cloud.

Are there subprocessors for planning data?

No. Planning data is not sent to Stratus or to a third-party planning host. Subprocessors for the Stratus website, email, and support tools sit outside that boundary and are covered when you request a DPA.

Who controls access?

Your Salesforce admins do. Packaged FinPlan Admin and FinPlan User permission sets sit on top of profiles, sharing, and field-level security you already run. There is no separate planning login or extra OAuth grant to govern.

How do users sign in?

They use Salesforce identity — including the SSO and MFA your org already requires. Financial Planner does not store Salesforce user passwords and is not a connected app with its own OAuth, OpenID Connect, or SAML flow.

Is data encrypted? Does Shield apply?

Planning data uses Salesforce encryption in transit and at rest. If your org enables Shield Platform Encryption, Event Monitoring, or Field Audit Trail, those controls remain compatible because the records never leave Salesforce. Confirm coverage for your edition.

Has Financial Planner completed AppExchange security review?

Yes. Financial Planner has passed Salesforce's required AppExchange security review. Salesforce uses that review to evaluate partner offerings before listing them on AppExchange.

Put it in front of IT and security

We will walk through native architecture, permission sets, and how planning data stays inside your Salesforce org — backed by the platform you already trust.

Public AppExchange listing coming soon — request early access to pilot in your org.
Passed Salesforce AppExchange security review.
Stratus Cloud Solutions has built Salesforce-native apps since 2009.
Documentation is available for evaluator walkthroughs. Open docs

Request early access Read the docs