3.1 Account and profile data

• Full name, work email address, password (hashed with bcrypt — never stored in plain text)
• Profile photograph (optional), company name, country, role, and company type
• Trade shows and events you attend or exhibit at
• Workspace name, type (Buyer / Supplier / Garment Maker / Designer), and team member roles

3.2 Content you create

• Fabric captures: article name, code, composition, weight, width, stretch, construction, wash code, sustainability certifications, colour, finish, and all OCR-extracted or manually entered fields
• Pricing data: price per metre, currency, and price tier — entered by Buyers only, encrypted at workspace level, never shared with any other party
• Text notes: free-text annotations on any capture, each individually marked Private or Shared by you
• Voice notes: audio recordings attached to captures, stored as audio files; transcripts generated only when you explicitly enable transcription
• Photographs: images you take of hang tags, fabric swatches, garment protos, or samples
• Status decisions: the status you assign to any capture or article (Shortlisted, On hold, Sample requested, Rejected, etc.)
• Chat messages and threads: messages and attachments sent through the in-app threading system, including pinned fabric references
• Development pipeline data: proto submissions, SMS records, fit sample records, stage notes, target FOB, yardage estimates, drop stage, and drop reasons
• Event data: trade show and mill visit records including name, date, location, and associated captures
• Export history: a log of PDFs and CSVs generated, including recipient details you provide

3.3 Technical and usage data

• IP address, device type, operating system, and app version
• Session duration, screens visited, and features used (anonymised in analytics)
• Crash reports and error logs
• Offline sync queue data and sync timestamps
• Push notification tokens

3.4 Data we do NOT collect

• Payment card numbers or bank account details (handled entirely by our payment processor)
• Government identification numbers or tax IDs
• GPS or precise location data (we collect country only, from your profile)
• Health, biometric, or sensitive category data as defined under GDPR Article 9
• Social media credentials or login tokens

5.1 What a Supplier sees about a connected Buyer

• Which of the supplier's own articles the buyer selected, and the buyer's status on each
• Notes and voice notes the buyer has explicitly marked as Shared
• The count of Private notes on a capture (e.g. "2 private notes") — never the content
• Messages sent through in-app threads

What a Supplier can never see: the buyer's price per metre, Private notes, captures from other suppliers, brand-internal budget information, or sub-brand tags.

5.2 What a Garment Maker sees about a Buyer and Supplier

• The fabric specification of the nominated article (composition, weight, width, stretch, construction)
• The buyer's target FOB garment price and delivery date
• Development stage, yardage estimate, and buyer feedback notes on each stage
• Messages in threads addressed to the garment maker

What a Garment Maker can never see: the fabric price the buyer paid per metre, Private notes, the supplier's buyer list or other relationships, or drop reasons beyond "Dropped" (the reason is internal to the buyer).

5.3 Workspace isolation

Each workspace is isolated at the database level. Connecting Workspace A to Workspace B creates a bilateral relationship scoped to those two workspaces only. Neither party can see the other's relationships with third parties. This cannot be overridden by any user role or permission setting.

5.4 Disconnecting a workspace

Either party may disconnect at any time from workspace settings. On disconnection, the other party's access to your shared data is revoked immediately. Data already received and potentially exported by the other party before disconnection cannot be retroactively deleted on their systems. Treat shared data as potentially retained by the receiving party after disconnection.

5.5 Note and voice note privacy toggles

Every text note and every voice note has an individual Private/Shared toggle. The default for all new notes is Private. Switching a note to Shared makes it visible to connected workspaces. Switching it back to Private revokes that visibility going forward, but does not retroactively delete the note from the other party's view if they have already read it.

7.1 Connected workspaces

As described in Section 5. All sharing is at your explicit direction.

7.2 Service providers (data processors)

We engage third-party processors under written data processing agreements. Current categories:

DenimNotes uses only four processors: Supabase, Resend, Apple APNs, and Google FCM. We do not currently use third-party AI providers, analytics platforms, payment processors, or error monitoring services that process personal data. AI features, OCR, and voice transcription are handled on-device or within our own application logic on Supabase infrastructure. When paid subscriptions are introduced, a payment processor will be added to this table.

Processors are not permitted to use your data for any purpose other than providing services to us. The complete sub-processor list above reflects all processors currently used. We will update this table and notify users 30 days in advance before adding any new processor that handles personal data.

7.3 Legal requirements

We may disclose data to courts, regulators, or law enforcement where required by law. Where legally permitted, we will notify you before complying.

7.4 Business transfers

In a merger, acquisition, or sale of assets, your data may be transferred. We will notify you before data becomes subject to a different privacy policy.

7.5 What we never do

• Sell or license personal data or business data to third parties
• Share pricing data, private notes, or captures outside of Section 5 boundaries
• Use your data to train AI models without explicit consent
• Share data with advertisers or data brokers
• Share aggregate data in a form that could identify your company's commercial position

12.1 How AI is used — schema-only architecture

DenimNotes uses AI for three functions. In every case, your actual fabric data never leaves our infrastructure:

• OCR (hang tag scanning): the hang tag photograph is sent to a third-party OCR service to extract text. The photograph is not retained by the OCR provider beyond the immediate transaction.
• AI search: your natural language query is sent to an AI model along with a description of your data structure (field names only — not values). The AI returns a structured filter. That filter is applied to your data on our servers. Your captures, notes, prices, and supplier names are never transmitted to the AI provider.
• AI Chat: the same schema-only approach. The AI interprets your query and returns a filter or instruction. Your data is retrieved from our database separately. Supplier-visible threads have additional restrictions — the AI cannot surface price data or private notes in any thread that includes a supplier participant.

12.2 Voice note transcription

Audio files are sent to a speech-to-text provider only when you explicitly request transcription for a specific recording. See Section 13 for full detail.

12.3 No automated decision-making with significant effects

We do not use automated decision-making, including profiling, to make decisions about you that produce legal or similarly significant effects (GDPR Art. 22). All status decisions, development approvals, and commercial choices are made by human users.

12.4 AI model training

We do not use your User Content — captures, notes, prices, voice recordings, supplier names, or development data — to train any AI model, internal or external, without your explicit prior written consent. If AI training features are introduced in future, they will be explicitly opt-in.

14.1 Threads and messages

• Threads are created by Buyers and addressed to connected suppliers or garment makers
• Messages in a thread are visible to all participants of that thread
• Thread messages are stored on our servers and retained for the duration of the account plus 30 days (see Section 9)
• Messages you send to connected workspaces may be retained by the receiving party after disconnection — treat messages as potentially permanent
• Deleting your account does not delete messages from the other party's workspace view

14.2 AI in supplier-visible threads

When @Denim AI is invoked in a thread that includes a supplier participant, the AI feature is restricted. It can answer questions about the shared fabric specification only. It cannot surface the buyer's price, private notes, or any data from outside the shared scope. This is enforced architecturally — not as a guideline.

14.3 Workspace connection data

When you invite a supplier to connect, we store a connection record including both workspace IDs, the status, access level, the date the invitation was created, and the date it was accepted. This record persists until the connection is dissolved.

18.1 Data breach notification

In the event of a personal data breach likely to result in risk to your rights and freedoms, we will notify the relevant supervisory authority within 72 hours (GDPR Art. 33) and affected users without undue delay if the risk is high (GDPR Art. 34). Contact info@esipick.com to report a security concern.