1. Who we are & our two roles
Alba365 Sunrise ("we", "us") is operated by [PLACEHOLDER: legal entity name]. Alba365 Sunrise is a cloud "workshop OS" for cabinet makers: quoting, cut-list nesting, scheduling, orders, invoicing and a customer portal.
We act as a data CONTROLLER for the accounts of the workshops that subscribe to us (their staff users' names, emails and login records). For the data a workshop stores about ITS OWN customers (contacts, quotes, orders), the workshop is the controller and we are its data PROCESSOR — we process that data only to provide the service, on the workshop's instructions.
2. Personal data we process
Depending on how the service is used, this can include:
- Workshop staff accounts — name, email, role, last-login time. Pay-rate fields are access-restricted within the workshop.
- A workshop's customers (its client records) — name, contact name, email, phone, address, and any internal notes the workshop adds.
- Customer-portal users — the email used to sign in, and an access log (IP address + browser user-agent) recorded for security and accountability when a portal or shared link is opened.
- Sales leads and CRM notes a workshop records.
- Subcontractors and external crew a workshop engages — name, company, contact details, address, a tax identifier (e.g. W-9 / business number), pay rate, and insurance/certification details (provider and reference numbers).
- Shared quote / sign-off links — when opened, we log the event with IP and user-agent; portal messages are stored to show the conversation.
- Deposit payments — financial records of deposits taken through the customer portal.
3. How we use personal data
- To provide, secure, and support the service (authentication, generating quotes/drawings/invoices, scheduling, the customer portal).
- To take subscription payments from workshops, and to process customer deposits on a workshop's behalf.
- To send transactional email (e.g. sign-in, quote and portal notifications).
- To detect and prevent abuse (rate-limiting, access logs).
- We do NOT sell personal data, and we do not use it for advertising.
4. Sub-processors
We use a small set of vetted service providers to run the platform. Each processes personal data only as needed to provide their part of the service:
- Stripe — subscription billing (our billing of workshops) and, separately, customer deposit payments taken on a workshop's behalf (Stripe Connect). Card details go directly to Stripe; we do not store card numbers.
- Resend — outbound transactional email delivery (recipient address + message content in transit).
- Microsoft Azure — application hosting (Container Apps), the PostgreSQL database, and Blob storage for uploaded files and logos (served through short-lived, access-controlled links).
- Artificial-intelligence providers — where AI insight features are enabled, we send only AGGREGATED figures (counts, sums, dates and labels); we do not send customer names or other direct identifiers. [PLACEHOLDER: AI export posture — BYO-key vs platform-key fallback].
- Error monitoring — if enabled in production, an error-tracking provider receives diagnostic events with personal data scrubbed. [PLACEHOLDER: confirm whether error tracking is enabled in production].
5. Where data is stored
Data is hosted on Microsoft Azure in [PLACEHOLDER: Azure hosting region(s)]. Some sub-processors (e.g. Stripe, Resend) may process limited data in other regions under their own safeguards.
6. How long we keep data
We keep personal data for as long as a workshop's account is active and as needed to provide the service. Some specific windows:
- Deleted file attachments are purged approximately 30 days after deletion.
- AI insight request logs are retained for around 180 days.
- Customer-portal access logs are retained for around 365 days for security and accountability.
- Personal data on an archived subcontractor record is anonymised after around 365 days.
- Sign-in and capability links expire quickly: portal sign-in (magic) links within about 30 minutes, portal invitation links within about 7 days, and shared quote / sign-off links according to their purpose.
- When an account is closed, we delete or anonymise personal data within a reasonable period, subject to legal and accounting retention obligations.
7. How we protect data
- Passwords are stored hashed (bcrypt); capability and reset tokens are stored hashed (never in plain text).
- Each workshop's data is isolated per-tenant; access requires authentication and is permission-checked.
- Traffic is served over HTTPS; sensitive tokens are redacted from error diagnostics.
8. Your rights
Depending on your location, you may have rights to access, correct, delete, or export your personal data, or to object to or restrict certain processing. [PLACEHOLDER: governing jurisdiction & law] sets the specific rights that apply.
To exercise a right, contact us at [PLACEHOLDER: privacy/DPO contact email]. Because a workshop is the controller of its own customers' data, if you are a workshop's customer we will refer your request to that workshop and assist it in responding. Workshops can export their own data at any time, on every plan, without asking us — every record, as CSV, in one download. We handle deletion requests through the contact process above.
9. Cookies
We use only strictly-necessary cookies to run the service; any future analytics cookies will require your prior consent. See our Cookie Policy for the full list.
10. Children
The service is a business tool and is not directed to children. We do not knowingly collect personal data from children.
11. Changes to this policy
We may update this policy from time to time. Material changes will be notified through the service or by email. The effective date above reflects the latest version.
12. Contact & governing law
Questions about this policy or your data: [PLACEHOLDER: privacy/DPO contact email] ([PLACEHOLDER: legal entity name]).
This policy is governed by the laws of [PLACEHOLDER: governing jurisdiction & law].