Legal & customer documents
We keep our paperwork light on purpose. Only two documents need a signature to start work: the optional Mutual NDA before deep-dive conversations, and the Statement of Work that starts each project. Everything else on this page — the MSA, the DPA, and (if elected) the SLA — is accepted automatically when the SOW is signed, as published on the SOW's effective date. No PDF stacks, no twelve signature lines.
The signing process, in order
- First conversation — nothing to sign. An intro call about your operation. Nothing confidential changes hands yet.
- Before discovery — sign the Mutual NDA (optional, both parties). Sign it before you walk us through your operations in detail, share data, or see our platform internals. If nothing sensitive will be shared, it can be skipped — but when in doubt, sign it first.
- Proposal — nothing to sign. From discovery, CCS drafts your Statement of Work: scope, flat monthly fee, hosting model, and timeline.
- Signing day — both parties sign the SOW. This is the one required signature. Before signing, check four things: the hosting model box is checked, the SLA box is checked (or deliberately not), the fees and dates are filled in, and the effective date at the top is correct — it sets which published version of the MSA, DPA, and SLA governs your SOW (later changes need 30 days' notice, and you can object — MSA Section 1.3). Each side keeps a countersigned copy, ideally with the incorporated documents attached.
- Kickoff — nothing to sign. CCS invoices per the SOW, sets up access, and the build starts.
- Ongoing — we keep you posted. The Privacy Policy and Sub-processor list stay current on this page. Adding a provider that handles your personal data, or materially changing the MSA or DPA, comes with advance notice — 30 days for term changes.
- If you ever leave — nothing to sign. 30 days' written notice, a 30-day window to export all your data (you can also export it yourself at any time while subscribed), an optional 60-day transition period, then deletion — confirmed in writing on request.
What needs a signature
| Document | Signature? | When |
|---|---|---|
| Mutual NDA | ✍ Yes — optional | Before discovery, if sensitive details will be shared |
| Statement of Work | ✍ Yes — the one required signature | Start of each project |
| Master Services Agreement | No — accepted by signing the SOW | Applies from your SOW date |
| Data Processing Addendum | No — accepted by signing the SOW | Applies from your SOW date |
| Service Level Agreement | No — applies only if elected in the SOW | Applies from your SOW date |
| Privacy Policy & Sub-processors | No — published policies | Always current on this page |
The documents
Master Services Agreement
The master terms for working with Cream City Solutions: who owns what, how subscriptions work, and the protections both sides get.
Statement of Work (Template)
The short ordering form each engagement starts with: scope, fees, hosting model, and timeline. Signing it accepts the published MSA, DPA, and (if elected) SLA.
Data Processing Addendum
How CCS handles personal information inside client applications: roles, security measures, sub-processors, breach notice, and the Canadian addendum for clients subject to PIPEDA.
Privacy Policy
What personal information Cream City Solutions collects, how it's used, where it's processed, and your choices — including for visitors and clients in Canada.
Service Level Agreement
Support hours, response-time targets by severity, the uptime commitment for CCS-hosted applications, and service credits.
Mutual Non-Disclosure Agreement (Template)
A short two-way confidentiality agreement for discovery and sales conversations, before any project is signed.
Sub-processors & Service Providers
The third-party providers CCS uses to build, host, and operate client applications — what each does and where it processes data.