docs/comms.md

comms

Pepperwind's collaboration and privacy systems, exported in the shape of a hosted business suite: mail (RFC 5322 headers, a message trace and each mailbox's copies), RFC 5545 calendars, a Slack-style chat export, the identity provider's audit log, a document store and the policy register. It also holds the privacy desk's records: the consent ledger, rights requests and the personal-data incident register. People are core employees (employee_id); consent and rights requests concern commerce customers. Message, chat, calendar-booking and audit rows cover 1 October 2023 to 30 September 2026; mailboxes, channels, series, documents and policies go back to the company's start in 2017.

Table	Rows	What it holds
audit_log	5,068	One row per audit event from the identity provider, the mail and file suite and the exports storage location. It joins three kinds of rows: people's own events (sign-ins, second-factor challenges, exports, API keys, external file shares) with IT's changes to their accounts; account events when a person joins and leaves; and events that come in bursts or on a schedule (credential-stuffing waves, service accounts' jobs, and the May 2026 export exposure with its response). Times are in UTC.
calendar_event	504	One row per calendar event: the one-off meetings employees book (from 1 October 2023), plus one row for each recurring or company-dated meeting in calendar_series, carrying its recurrence rule. Occurrences of a series are not expanded into rows.
calendar_series	258	One row per recurring meeting (one-to-ones, stand-ups, team weeklies, the leadership weekly, sales pipeline, S&OP) and per meeting the company dates itself (board meetings, monthly business reviews, incident reviews), as the calendar stores the series. Each also appears as one row in calendar_event.
chat_channel	1,159	One row per chat channel ever created, including archived ones and direct messages: standing channels, team, site and social channels, projects, the festive war rooms, incident rooms and direct messages between two people.
chat_member	5,375	One row per member of a channel at the export date, as the chat tool lists them: people still in the channel, the bots posting in it, and both people in every direct message. Someone whose account was switched off on leaving is not listed, except in direct messages.
chat_message	24,458	One row per chat message from 1 October 2023: people's messages in direct messages and channels, replies in threads, the incident rooms and their status updates, bot posts (deploys, CI, on-call pages, the payment monitor, and an order feed of every wholesale order and large storefront orders), and the chat tool's own line when someone joins a channel.
consent_record	1,883	The privacy desk's consent ledger: one row per storefront (D2C) customer and purpose they were asked about. Rows are rewritten in place, so each holds the current status and only the one before it. Wholesale accounts have no rows.
data_incident	3	The register of personal-data incidents: one row per incident, from discovery to closure, with who was told and when.
document	999	One row per document in the company's document store at the export date: SOPs, product specs, artwork briefs, design docs, runbooks, postmortems, board papers, budgets, monthly MIS packs, contracts, HR documents, marketing briefs, sales material, privacy documents and meeting notes.
document_versions	2,537	One row per saved version of a document, so each document's history can be read as a sequence of validity periods.
dsar_request	9	One row per data-subject rights request (deletion, access, opt-out, correction) as the privacy desk logs it, from storefront customers and from people who match no customer. A customer who asks for deletion places no order after asking, and the email platform sends nothing after a deletion or opt-out request the desk matches to a customer. A deletion the desk completed erased the customer's personal data from the systems it touched, keeping their orders, invoices and ledger lines for the books.
email_message	98,960	One row per message per Pepperwind mailbox that holds it: the sender's Sent copy and each Pepperwind recipient's Inbox copy, all with the same Message-ID. Besides conversational mail (mail_item), it holds automated mail, phishing that reached inboxes, announcements to distribution lists, out-of-office replies, the privacy mailbox's request threads and incident notices, and separation mail. A copy exists only while its mailbox was open; outside parties' mailboxes are not included. Rows are numbered in order of sending.
mail_item	27,170	The mail suite's message trace for conversations: one row per message, internal or with an outside party, from a thread's first message to its last reply. Each message appears once here; its copies in Pepperwind mailboxes are in email_message. Automated mail, phishing, announcements, out-of-office replies, privacy mail and separation mail are only in email_message.
mail_thread	10,201	One row per mail conversation: started by a Pepperwind employee (with a colleague or an outside party) or by an outside party writing to them. Threads that got no reply have a single message. Mail an outside party sends to a shared address is filed under a colleague who reads that address.
mailbox	210	One row per mailbox ever created, including disabled ones: personal mailboxes (full ones for office staff, small web-only kiosk ones for Rotterdam's warehouse staff), shared addresses (orders@, ap@, privacy@, careers@ and others) and meeting rooms. Kochi's floor staff have no mailbox. Mailboxes are disabled, never deleted.
policy	15	The policy register: one row per approved version of a company policy (POL--v), current or superseded.
policy_versions	40	One row per saved state of a policy version in the register: its drafts, then its approval, so the path from first draft to approval can be read as validity periods.

audit_log

One row per audit event from the identity provider, the mail and file suite and the exports storage location. It joins three kinds of rows: people's own events (sign-ins, second-factor challenges, exports, API keys, external file shares) with IT's changes to their accounts; account events when a person joins and leaves; and events that come in bursts or on a schedule (credential-stuffing waves, service accounts' jobs, and the May 2026 export exposure with its response). Times are in UTC.

5,068 rows; key log_id.

Column	Type	Empty	Range or values	Meaning
log_id	integer, key	0.0%	1 to 5068	Identifies the audit event.
action	text	0.0%	sso_login, sso_login_failed, mfa_challenge	What happened, for example sso_login, sso_login_failed, mfa_challenge, data_export_started, role_granted, user_deactivated, storage_object_read, public_link_revoked or consent_backfill_batch.
actor_kind	text	0.0%	employee, admin, service	Who acted: employee (a person on their own account), admin (IT changing accounts), service (an integration or scheduled job) or unknown (an outside actor, such as credential stuffing or reads of the exposed export).
actor_employee_id	integer	39.2%	1 to 283	The employee who acted (for admin events, the IT administrator). Empty for service accounts and unknown actors.
object_type	text	0.0%	user, file, export	What the action was on: user, export, api_key, file, storage_object, bucket, integration, audit_log or consent_ledger.
object_id	text	2.6%	nikhil.paulose@pepperwind.example, fathima.rasheed@pepperwind.example, drive/MKs2lHSHCF73bQuJ5iXx	The object acted on: a user's mail address, an export file path, an API key id, a shared file's drive path, a bucket or a service account's name. A failed sign-in in a stuffing wave may name an address that does not exist. Empty where the event names no single object.
occurred_at	text	0.0%	2023-10-31T03:54:58+00:00, 2023-11-07T03:48:53+00:00, 2024-03-19T03:56:26+00:00	When the event happened, in UTC.
ip	text	0.0%	192.0.2.17, 192.0.2.28, 192.0.2.19	The address the request came from, all in documentation ranges: 192.0.2.x for the offices, IT and the service accounts, 198.51.100.x for home and remote connections, 203.0.113.x for outside actors.
outcome	text	0.0%	success, failure	success or failure; failed sign-ins are the failures.
related_ref	text	62.3%	org_change:2647, org_change:2927, org_change:2934	What the event belongs to, where it belongs to something: org_change: for role changes made in a bulk reorganisation (the day counted from 1 January 2017, so 2647 is 1 April 2024), or data_incident: for a personal-data incident in the register and its response.

calendar_event

One row per calendar event: the one-off meetings employees book (from 1 October 2023), plus one row for each recurring or company-dated meeting in calendar_series, carrying its recurrence rule. Occurrences of a series are not expanded into rows.

504 rows; key event_id.

Column	Type	Empty	Range or values	Meaning
event_id	integer, key	0.0%	1 to 504	Identifies the calendar event.
organizer_employee_id	integer	0.0%	1 to 278	The employee who organised the meeting.
attendees	text	0.0%	[{"email": "nikhil.paulose@pepperwind.example", "role": "CHAIR", "partstat": "ACCEPTED", "optional": false}, {"email": ", [{"email": "fathima.rasheed@pepperwind.example", "role": "CHAIR", "partstat": "ACCEPTED", "optional": false}, {"email": , [{"email": "thomas.kuriakose@pepperwind.example", "role": "CHAIR", "partstat": "ACCEPTED", "optional": false}, {"email":	The invitees as a JSON list of {email, role, partstat, optional}: the organiser first as CHAIR, then REQ-PARTICIPANT or OPT-PARTICIPANT, with each one's response (ACCEPTED, TENTATIVE, DECLINED or NEEDS-ACTION). Outside guests appear by their own address. A series lists at most its first forty attendees.
start_at	text	0.0%	2017-03-22T17:00:00+05:30, 2017-03-31T11:30:00+05:30, 2017-04-20T11:00:00+05:30	When the meeting starts (for a series, its first occurrence), on the organiser's clock in timezone.
end_at	text	0.0%	2017-03-22T17:30:00+05:30, 2017-03-31T12:00:00+05:30, 2017-04-20T11:30:00+05:30	When the meeting ends (for a series, its first occurrence), on the organiser's clock in timezone.
created_at	text	0.0%	2017-03-17T12:03:02+05:30, 2017-03-25T11:50:52+05:30, 2017-04-14T10:19:14+05:30	When the event was booked, on the organiser's clock in timezone.
timezone	text	0.0%	Asia/Kolkata, Europe/Amsterdam, America/New_York	The organiser's IANA time zone, which start_at, end_at and created_at are written in.
location	text	3.0%	https://meet.pepperwind.example/zia-tclp-0sx, https://meet.pepperwind.example/k92-ak8r-r6a, https://meet.pepperwind.example/krm-kkzq-u6y	A meeting room or a video link on meet.pepperwind.example. Empty where none was set.
recurrence	text	58.7%	FREQ=WEEKLY;INTERVAL=2;BYDAY=WE, FREQ=WEEKLY;INTERVAL=2;BYDAY=FR, FREQ=WEEKLY;INTERVAL=2;BYDAY=TH	The iCalendar recurrence rule (RRULE) of a recurring series. Empty for one-off meetings and dated meetings.
exdates	text	67.9%	20230308T170000,20231101T170000,20240717T170000,20241225T170000,20251105T170000,20260304T170000,20260527T170000, 20220415T113000,20220819T113000,20230407T113000,20230414T113000,20240126T113000,20241115T113000,20250314T113000,20250815, 20220414T110000,20220908T110000,20230330T110000,20230928T110000,20240411T110000,20240523T110000,20251225T110000	Occurrences removed from a series, as local start times (yyyymmddThhmmss) in the series' time zone, mostly ones falling on a public holiday. Empty where none were removed.
cancelled	boolean	0.0%	False to True	True when the meeting was cancelled.
status	text	0.0%	CONFIRMED, CANCELLED	The iCalendar status: CONFIRMED, or CANCELLED for a cancelled meeting.
sequence	integer	0.0%	0 to 4	The iCalendar SEQUENCE: how many times the event was updated after it was sent, 0 if never.
uid	text	0.0%	4bd7306b-78e3-495c-b927-9289423365ee@pepperwind.example, 5e2b839e-a6f8-423b-9fc0-2023a474ef88@pepperwind.example, 9aa76a56-34dc-412e-97c2-a7a15ad30a19@pepperwind.example	The iCalendar UID, one per event or series.
title	text	0.0%	1:1, Leadership weekly, FIN weekly	The meeting's title as its organiser wrote it.

calendar_series

One row per recurring meeting (one-to-ones, stand-ups, team weeklies, the leadership weekly, sales pipeline, S&OP) and per meeting the company dates itself (board meetings, monthly business reviews, incident reviews), as the calendar stores the series. Each also appears as one row in calendar_event.

258 rows; key series_id.

Column	Type	Empty	Range or values	Meaning
series_id	integer, key	0.0%	1 to 258	Identifies the series.
organizer_employee_id	integer, → core.employee.employee_id	0.0%	1 to 278	The employee who owns the series.
title	text	0.0%	1:1, Leadership weekly, FIN weekly	The series' title, for example 1:1, Leadership weekly or FIN weekly.
start_at	text	0.0%	2017-03-22T17:00:00+05:30, 2017-03-31T11:30:00+05:30, 2017-04-20T11:00:00+05:30	When the first occurrence starts, on the organiser's clock in timezone.
end_at	text	0.0%	2017-03-22T17:30:00+05:30, 2017-03-31T12:00:00+05:30, 2017-04-20T11:30:00+05:30	When the first occurrence ends, on the organiser's clock in timezone.
timezone	text	0.0%	Asia/Kolkata, Europe/Amsterdam, America/New_York	The organiser's IANA time zone. A series keeps this wall-clock time, so other offices see it move at daylight-saving changes.
location	text	5.8%	https://meet.pepperwind.example/zia-tclp-0sx, https://meet.pepperwind.example/k92-ak8r-r6a, https://meet.pepperwind.example/krm-kkzq-u6y	A meeting room or a video link on meet.pepperwind.example. Empty where none was set.
recurrence	text	19.4%	FREQ=WEEKLY;INTERVAL=2;BYDAY=WE, FREQ=WEEKLY;INTERVAL=2;BYDAY=FR, FREQ=WEEKLY;INTERVAL=2;BYDAY=TH	The iCalendar recurrence rule (RRULE). Empty for a dated meeting that does not repeat.
exdates	text	37.2%	20230308T170000,20231101T170000,20240717T170000,20241225T170000,20251105T170000,20260304T170000,20260527T170000, 20220415T113000,20220819T113000,20230407T113000,20230414T113000,20240126T113000,20241115T113000,20250314T113000,20250815, 20220414T110000,20220908T110000,20230330T110000,20230928T110000,20240411T110000,20240523T110000,20251225T110000	Occurrences removed from the series, as local start times (yyyymmddThhmmss) in its time zone, mostly ones falling on a public holiday. Empty where none were removed.
created_at	text	0.0%	2017-03-17T12:03:02+05:30, 2017-03-25T11:50:52+05:30, 2017-04-14T10:19:14+05:30	When the series was set up, on the organiser's clock in timezone.
cancelled	boolean	0.0%	False to False	True for a cancelled series; no series in this export is cancelled.
status	text	0.0%	CONFIRMED	The iCalendar status of the series (CONFIRMED).
sequence	integer	0.0%	0 to 2	The iCalendar SEQUENCE: how many times the series was updated after it was sent.
attendees	text	0.0%	[{"email": "nikhil.paulose@pepperwind.example", "role": "CHAIR", "partstat": "ACCEPTED", "optional": false}, {"email": ", [{"email": "fathima.rasheed@pepperwind.example", "role": "CHAIR", "partstat": "ACCEPTED", "optional": false}, {"email": , [{"email": "thomas.kuriakose@pepperwind.example", "role": "CHAIR", "partstat": "ACCEPTED", "optional": false}, {"email":	The invitees as a JSON list of {email, role, partstat, optional}: the organiser first as CHAIR, then REQ-PARTICIPANT or OPT-PARTICIPANT, with each one's response. Lists at most the first forty attendees, and outside guests (such as board members) by their own address.
uid	text	0.0%	4bd7306b-78e3-495c-b927-9289423365ee@pepperwind.example, 5e2b839e-a6f8-423b-9fc0-2023a474ef88@pepperwind.example, 9aa76a56-34dc-412e-97c2-a7a15ad30a19@pepperwind.example	The iCalendar UID, shared by every occurrence of the series.

chat_channel

One row per chat channel ever created, including archived ones and direct messages: standing channels, team, site and social channels, projects, the festive war rooms, incident rooms and direct messages between two people.

1,159 rows; key channel_id.

Column	Type	Empty	Range or values	Meaning
channel_id	integer, key	0.0%	1 to 1159	Identifies the channel in this dataset.
slack_id	text	0.0%	CC04M3JSF4I, C7BUKJ6KMZ0, CUDKOSOZYOK	The channel's id in the chat tool's own format: C and ten characters for a channel, D for a direct message.
name	text	90.1%	founders, random, general	The channel's name, in lowercase (for example general, eng-deploys, inc-2025-11-18-payment-gateway). Empty for direct messages.
kind	text	0.0%	team, social, announcement	What the channel is for: team, site (an office), project (including the diwali- war rooms), incident, announcement, alerts (bot feeds), social or dm (a direct message).
is_private	boolean	0.0%	False to True	True for a private channel or a direct message.
topic	text	92.7%	Anything goes. Be kind, Company-wide announcements. Questions go in #it-help or #people-team, Kochi HQ: visitors, parking, the pantry, power cuts	The channel's topic as the export finds it, the last one set. Empty where none was ever set, and on every direct message.
created_at	text	0.0%	2017-03-14T13:08:54+05:30, 2017-03-14T16:30:22+05:30, 2017-03-14T17:23:32+05:30	When the channel was created, on Kochi's clock (IST, +05:30).
created_by_employee_id	integer, → core.employee.employee_id	0.3%	1 to 283	The employee who created the channel. Empty where no member was on the payroll when it was created.
archived_at	text	98.3%	2022-11-14T17:30:23+05:30, 2024-03-29T15:48:21+05:30, 2023-12-03T16:27:31+05:30	When the channel was archived, on Kochi's clock (IST, +05:30). Empty for channels still open; projects, war rooms and incident rooms are archived when their work ends.

chat_member

One row per member of a channel at the export date, as the chat tool lists them: people still in the channel, the bots posting in it, and both people in every direct message. Someone whose account was switched off on leaving is not listed, except in direct messages.

5,375 rows; key chat_member_id.

Column	Type	Empty	Range or values	Meaning
chat_member_id	integer, key	0.0%	1 to 5375	Identifies the membership row.
channel_id	integer, → comms.chat_channel.channel_id	0.0%	1 to 1159	The channel.
employee_id	integer, → core.employee.employee_id	0.1%	1 to 287	The employee who is a member. Empty for a bot.
user_id	text	0.1%	U3XSWP13RZ1, UD56S5YXZVP, U0QW83IECT7	The person's chat user id (U and ten characters), the same in every channel and message. Empty for a bot.
bot_id	text	99.9%	B08GNAQL2PR, B06FOPXT09D, B0CEIXWVOVX	The bot's id (B and ten characters) for a bot member. Empty for people.

chat_message

One row per chat message from 1 October 2023: people's messages in direct messages and channels, replies in threads, the incident rooms and their status updates, bot posts (deploys, CI, on-call pages, the payment monitor, and an order feed of every wholesale order and large storefront orders), and the chat tool's own line when someone joins a channel.

24,458 rows; key chat_message_id.

Column	Type	Empty	Range or values	Meaning
chat_message_id	integer, key	0.0%	1 to 24458	Identifies the message.
channel_id	integer, → comms.chat_channel.channel_id	0.0%	1 to 1123	The channel or direct message it was posted in.
user_employee_id	integer	14.6%	1 to 287	The employee who posted it. Empty for bot posts.
bot_id	text	85.4%	B0YQ871ZYBL, B08GNAQL2PR, B06FOPXT09D	The bot that posted it. Empty for people's messages.
posted_at	text	0.0%	2023-10-05T20:26:40+05:30, 2023-10-13T11:45:51+05:30, 2023-10-13T09:31:15+05:30	When the message was posted, on the poster's local clock (bots on Kochi's, IST).
ts	text	0.0%	1696517800.153812, 1697177751.584953, 1697169675.382460	The chat tool's message timestamp (Unix seconds and microseconds), which identifies the message within its channel.
edited_at	text	94.7%	2024-02-26T17:02:21+05:30, 2024-05-07T12:37:29+05:30, 2024-08-19T09:12:35+05:30	When the message was last edited, on the same clock as posted_at. Empty if never edited.
reactions	text	92.1%	[{"name": "slightly_smiling_face", "count": 1}], [{"name": "thumbsup", "count": 1}], [{"name": "ok_hand", "count": 1}, {"name": "thumbsup", "count": 1}]	The emoji reactions as a JSON list of {name, count}. Empty when the message has none.
thread_ts	text	81.0%	1697177751.584953, 1707284467.963169, 1709728041.338765	The ts of the thread's first message: set on a message that started a thread (equal to its own ts) and on each reply in it. Empty for messages outside threads.
subtype	text	70.5%	thread_broadcast, bot_message, channel_join	The chat tool's message subtype: bot_message, channel_join, or thread_broadcast (a reply also posted to the channel). Empty for an ordinary message.
text	text	0.0%	hey team Can someone own the cutover checklist?, pipeline is updated in the CRM, Need a hand with this when someone's free	The message text as Slack exports it: a person is mentioned as <@user_id>, the channel as or , and emoji as :name:. Bots post deploys, builds, pages, payment alerts and orders; a join line reads <@user_id> has joined the channel. Some direct messages between colleagues in one office are in Dutch, or in Malayalam typed in the Latin alphabet.

consent_record

The privacy desk's consent ledger: one row per storefront (D2C) customer and purpose they were asked about. Rows are rewritten in place, so each holds the current status and only the one before it. Wholesale accounts have no rows.

1,883 rows; key record_id.

Column	Type	Empty	Range or values	Meaning
record_id	integer, key	0.0%	1 to 1883	Identifies the consent record.
customer_id	text, → commerce.customer.customer_id	0.0%	cus_H4xsA8WGgDRIJc, cus_4kwxj7KP7D9DPK, cus_KkFrD48CdXjYsT	The storefront customer.
purpose	text	0.0%	account_terms, marketing_email, marketing_sms_whatsapp	What the consent covers: account_terms and club_terms (agreed terms of an account and of the Club subscription), marketing_email, marketing_sms_whatsapp (India only), and personalised_ads_cookies and analytics_cookies (the EU web store's cookie banner, from February 2024).
captured_at	text	0.0%	2023-04-03T09:23:40+05:30, 2023-04-03T09:23:58+05:30, 2023-06-13T21:52:59+05:30	When the choice was first recorded, on the customer's local clock: at sign-up, checkout, the cookie banner or the Club subscription's start. Indian customers who signed up before June 2021 carry the date their records were imported (1 June 2021).
status	text	0.0%	granted, withdrawn, reconsent_requested	The current status: granted, denied, withdrawn, or reconsent_requested (asked to confirm again and not yet answered).
rewritten_at	text	85.9%	2026-06-22T02:26:39+05:30, 2023-06-15T18:12:23+05:30, 2023-12-02T01:10:35+05:30	When the status last changed after it was captured (an unsubscribe, a complaint, a request, a correction or a re-consent), on the customer's local clock. Empty if it never changed.
previous_status	text	85.9%	granted, reconsent_requested, withdrawn	The status before the last change. Empty if it never changed.
evidence	text	0.0%	checkout_checkbox, checkbox_preticked_v1, unsubscribe_link	What the current status rests on: checkout_checkbox, checkbox_preticked_v1, checkbox_unticked_v2, cookie_banner_v2, legacy_import, unsubscribe_link, spam_complaint, support_ticket, dsar or reconsent_email_v3.
source	text	0.0%	checkout, cookie_banner, import	Where the consent was first captured: checkout, cookie_banner, or import (records brought over in June 2021).
policy_version	integer	0.0%	1 to 3	The privacy policy version the status was given under (1, 2 or 3, as policy POL-PRV-v1 to v3): the one in force at capture, or 3 for a re-consent.

data_incident

The register of personal-data incidents: one row per incident, from discovery to closure, with who was told and when.

3 rows; key incident_id.

Column	Type	Empty	Range or values	Meaning
incident_id	integer, key	0.0%	1 to 3	Identifies the incident.
incident_key	text	0.0%	misdelivered_statement, account_takeover_cluster, exports_location_exposure	A short stable name for the incident, used in references such as data_incident: elsewhere.
title	text	0.0%	Account statement sent to the wrong buyer, Customer account takeovers, Marketing export exposed by a public link	The incident's title.
discovered_at	text	0.0%	2024-11-13T16:42:09+05:30, 2026-02-16T11:52:18+05:30, 2026-05-11T10:14:37+05:30	When Pepperwind found out, on Kochi's clock (IST, +05:30).
exposure_start	text	0.0%	2024-11-13T15:58:31+05:30, 2026-02-09T00:00:00+05:30, 2026-04-20T14:26:51+05:30	When the data first became exposed, on Kochi's clock (IST, +05:30).
exposure_end	text	0.0%	2024-11-13T17:05:44+05:30, 2026-02-27T23:59:59+05:30, 2026-05-11T11:03:27+05:30	When the exposure ended, on Kochi's clock (IST, +05:30).
records_affected	integer	33.3%	4 to 247	How many people or records were affected; for the export exposure, the number of customers sent a notice. Empty where no count was recorded.
data_categories	text	0.0%	business contact names,emails,invoice numbers and amounts, names,phones,addresses,order history,saved card brand and last four, names,emails,phones,city and pincode,order count and last order date,consent flags	The kinds of personal data involved, comma-separated.
notified_at	text	0.0%	2024-11-13T17:31:02+05:30, 2026-02-16T17:22:40+05:30, 2026-05-11T15:41:06+05:30	When the first notification went out to anyone outside the company, on Kochi's clock (IST, +05:30).
regulator_notified_at	text	33.3%	2026-02-16T17:22:40+05:30, 2026-05-11T15:41:06+05:30	When a regulator was told, on Kochi's clock (IST, +05:30). Empty where no regulator was notified.
customers_notified_at	text	0.0%	2024-11-13T17:31:02+05:30, 2026-02-17T14:05:12+05:30, 2026-05-14T09:00:00+05:30	When the affected customers or account were told, on Kochi's clock (IST, +05:30).
root_cause	text	0.0%	misdelivery (email autocomplete), credential stuffing with reused passwords; no second factor on customer accounts, a marketing export written to a storage location with a public link and no expiry	What caused the incident, in a phrase.
status	text	0.0%	closed	The incident's status in the register.
closed_at	text	0.0%	2024-11-15T12:10:51+05:30, 2026-03-13T15:27:18+05:30, 2026-07-31T16:02:44+05:30	When the incident was closed, on Kochi's clock (IST, +05:30).
owner_employee_id	integer, → core.employee.employee_id	0.0%	7 to 20	The employee accountable for the incident.

document

One row per document in the company's document store at the export date: SOPs, product specs, artwork briefs, design docs, runbooks, postmortems, board papers, budgets, monthly MIS packs, contracts, HR documents, marketing briefs, sales material, privacy documents and meeting notes.

999 rows; key document_id.

Column	Type	Empty	Range or values	Meaning
document_id	integer, key	0.0%	1 to 999	Identifies the document.
doc_no	text	0.0%	DOC-00001, DOC-00002, DOC-00003	The document number, DOC- and five digits, in order of creation.
title	text	0.0%	Product specification: Moonlight White 250 g, Subscription agreement: Thekkady Labs, Product specification: Mango Wood Serving Board	The document's title as the store lists it. A few documents were never given one and read Untitled document.
kind	text	0.0%	product_spec, contract, sop	The type of document: sop, product_spec, packaging_artwork_brief, design_doc, runbook, postmortem, board, budget_and_forecast, mis_pack, contract, hr, marketing_brief, sales_material, privacy or meeting_notes.
owner_employee_id	integer, → core.employee.employee_id	0.0%	1 to 278	The employee who owns the document.
created_at	text	0.0%	2017-03-17T21:46:37+05:30, 2017-04-06T20:36:29+05:30, 2017-04-21T16:43:04+05:30	When the first version was saved, on Kochi's clock (IST, +05:30).
updated_at	text	0.0%	2017-03-17T21:46:37+05:30, 2017-04-06T20:36:29+05:30, 2017-11-26T11:56:25+05:30	When the latest version was saved, on Kochi's clock (IST, +05:30); equal to created_at for a document never edited.
classification	text	0.0%	internal, confidential, public	The document's access class: public, internal, confidential or restricted.
version_count	integer	0.0%	1 to 8	How many versions have been saved (the rows in document_versions).
body	text	0.0%	Product specification: Moonlight White 250 g Owner: Thomas Kuriakose Purpose: the specification of this product as pack, Subscription agreement: Thekkady Labs Owner: Martin Ittyerah Key commercial terms and renewal dates. ## Quality Goods , Product specification: Mango Wood Serving Board Owner: Thomas Kuriakose This spec covers grade, moisture, pack size and	The text of the latest version: the title and owner, then the document's sections.

document_versions

One row per saved version of a document, so each document's history can be read as a sequence of validity periods.

2,537 rows; key version_id.

Column	Type	Empty	Range or values	Meaning
version_id	integer, key	0.0%	1 to 2537	Identifies the saved version.
document_id	integer, → comms.document.document_id	0.0%	1 to 999	The document.
version	integer	0.0%	1 to 8	The version number within the document, from 1.
valid_from	text	0.0%	2017-03-17T21:46:37+05:30, 2017-04-06T20:36:29+05:30, 2017-04-21T16:43:04+05:30	When this version was saved, on Kochi's clock (IST, +05:30).
valid_to	text	39.4%	2017-04-26T10:04:29+05:30, 2017-11-26T11:56:25+05:30, 2017-06-14T16:34:30+05:30	When the next version replaced it, on Kochi's clock (IST, +05:30). Empty for the current version.
edited_by_employee_id	integer, → core.employee.employee_id	0.0%	1 to 278	The employee who saved this version: the owner, or a colleague in the owner's unit once the owner had left.
body	text	0.0%	Product specification: Moonlight White 250 g Owner: Thomas Kuriakose Purpose: the specification of this product as pack, Subscription agreement: Thekkady Labs Owner: Martin Ittyerah Key commercial terms and renewal dates. ## Quality Goods , Product specification: Mango Wood Serving Board Owner: Thomas Kuriakose This spec covers grade, moisture, pack size and	The text of this version: the title and owner, then the sections written by then. Later versions add sections as the document is written.

dsar_request

One row per data-subject rights request (deletion, access, opt-out, correction) as the privacy desk logs it, from storefront customers and from people who match no customer. A customer who asks for deletion places no order after asking, and the email platform sends nothing after a deletion or opt-out request the desk matches to a customer. A deletion the desk completed erased the customer's personal data from the systems it touched, keeping their orders, invoices and ledger lines for the books.

9 rows; key dsar_id.

Column	Type	Empty	Range or values	Meaning
dsar_id	integer, key	0.0%	1 to 9	Identifies the request.
received_at	text	0.0%	2025-10-14T11:00:59+05:30, 2026-05-14T21:41:34+05:30, 2026-05-15T06:04:32+05:30	When the request arrived, on Kochi's clock (IST, +05:30).
intake	text	0.0%	privacy_mailbox, web_form	How it arrived: privacy_mailbox (mail to privacy@), support_ticket, or web_form.
kind	text	0.0%	deletion, opt_out, access	What was asked: deletion, access, opt_out, correction or other.
due_at	timestamp, ISO 8601 with the row's own UTC offset	0.0%	2025-11-28 00:00:00 to 2026-06-17 00:00:00	The date the answer is due: one calendar month after receipt for EU customers (two months more when the desk extends it), 30 days for India and 45 days for the US.
status	text	0.0%	completed, closed_unverified, closed_no_match	Where the request stands at the export: completed, open, closed_unverified (the requester did not pass the identity check), closed_no_match (no customer matched) or closed_duplicate.
completed_at	text	0.0%	2025-11-17T12:29:20+05:30, 2026-05-19T17:16:57+05:30, 2026-05-27T10:07:22+05:30	When the desk closed the request, whatever the outcome, on Kochi's clock (IST, +05:30). Empty while it is open.
systems_touched	text	0.0%	commerce,billing,support,marketing,product,crm, marketing, commerce,billing,support,marketing,product	The systems the desk searched or changed for it, comma-separated; follows from kind.
handled_by_employee_id	integer	0.0%	8 to 248	The privacy desk member who handled it.
customer_id	text, → commerce.customer.customer_id	11.1%	cus_GUNkgcNNLgHXJd, cus_DVEVexrbVdVEsw, cus_NahKBNR46tx49g	Identifies the storefront customer the request was matched to. Empty for requests closed with no match.
requester_email	text	0.0%	scook@courier.example, karthik.jayakumar@mail.example, rnambiar@post.example	The address the request came from: the customer's own, or for no-match requests an address that matches no customer.
ticket_ref	text	100.0%		The support ticket the request came in on, for requests with intake support_ticket. Empty otherwise.

email_message

One row per message per Pepperwind mailbox that holds it: the sender's Sent copy and each Pepperwind recipient's Inbox copy, all with the same Message-ID. Besides conversational mail (mail_item), it holds automated mail, phishing that reached inboxes, announcements to distribution lists, out-of-office replies, the privacy mailbox's request threads and incident notices, and separation mail. A copy exists only while its mailbox was open; outside parties' mailboxes are not included. Rows are numbered in order of sending.

98,960 rows; key email_id.

Column	Type	Empty	Range or values	Meaning
email_id	integer, key	0.0%	1 to 98960	Identifies this copy of the message, numbered in order of sending.
mailbox_id	text, → comms.mailbox.mailbox_id	0.0%	2f8e6d16-ed79-4f8f-9540-a1b646c2c5df, 870104f5-bf36-4866-9ca9-392393e5554f, 22408e14-7b1a-485e-a332-7b1d56ebc612	The Pepperwind mailbox (personal or shared) holding this copy.
message_id	text	0.0%	<5C45AawP0aiBUELU5riHY2Wpbz2r5R3c@mailer.sendrelay.example>, <eC7nXKwhoI3wxkOFYO0jnmVRlS9O63r6@calendar.pepperwind.example>, <iw46rnm6XUvGrA7prEmP4Se3EeW3vj63@mailer.sendrelay.example>	The message's Message-ID header, the same in every copy; Pepperwind's own mail uses hex@mail.pepperwind.example>, with the UTC time.
thread_id	text	0.0%	<5C45AawP0aiBUELU5riHY2Wpbz2r5R3c@mailer.sendrelay.example>, <eC7nXKwhoI3wxkOFYO0jnmVRlS9O63r6@calendar.pepperwind.example>, <iw46rnm6XUvGrA7prEmP4Se3EeW3vj63@mailer.sendrelay.example>	The Message-ID of the conversation's first message.
in_reply_to	text	68.2%	<XKKUPR01MB6329feecVEIjXAMLBYOVbJfG@HPOSPR04MB1522.eurprd10.prod.officesuite.example>, <20231003044914.3cbc84b7@mail.pepperwind.example>, <20231003045842.e4c0a2c6@mail.pepperwind.example>	The In-Reply-To header: the Message-ID of the message this one answers. Empty for a first message.
references	text	68.2%	<XKKUPR01MB6329feecVEIjXAMLBYOVbJfG@HPOSPR04MB1522.eurprd10.prod.officesuite.example>, <20231003044914.3cbc84b7@mail.pepperwind.example>, <20231003044914.3cbc84b7@mail.pepperwind.example> <20231003045842.e4c0a2c6@mail.pepperwind.example>	The References header: the Message-IDs of the earlier messages in the conversation, space-separated. Empty for a first message.
from_addr	text	0.0%	no-reply@saas-notify.example, calendar-notification@pepperwind.example, alerts@monitoring.example	The sender's address.
to_addrs	text	0.0%	mubeena.rafeek@pepperwind.example, gopakumar.ayyappan@pepperwind.example, rajesh.vijayan@pepperwind.example	The To addresses, comma-separated.
cc_addrs	text	72.1%	purchase@jamunsearchpartners.example, priya.varghese@pepperwind.example, purchase@investors.example	The Cc addresses, comma-separated. Empty when no one was copied.
subject_prefix	text	0.0%	``, Auto: , Re:	The structural start of the subject: empty, Re: (a reply), Fwd: (a forward), Auto: (an out-of-office reply), Undeliverable: (the mail server's notice that a message reached no mailbox), or Antw: or AW: written by Dutch or German correspondents.
date_header	text	0.0%	Sun, 1 Oct 2023 04:00:55 +0000, Sun, 1 Oct 2023 05:14:03 +0000, Sun, 1 Oct 2023 05:16:02 +0000	The Date header as the sender's mail program wrote it, with the sender's UTC offset. Some outside servers write +0000 and a few senders' clocks are off, so it can differ from sent_at.
direction	text	0.0%	in, out, internal	internal (Pepperwind to Pepperwind), in (from outside) or out (to outside), from the sender's side.
kind	text	0.0%	automated, recruitment, bank_and_advisor	What the mail is: internal, or the kind of outside correspondent (b2b_customer, export_buyer, vendor, logistics_partner, threepl, bank_and_advisor, investors_and_board, tax_and_regulator_portals, recruitment, payroll_and_benefits_provider, agency_and_creator, other), or automated, phishing, announcement, auto_reply, privacy_request, privacy_notice or separation.
size_kb	integer	0.0%	1 to 25603	The message's size in kilobytes, attachments included.
attachment_count	integer	0.0%	0 to 5	How many files are attached.
related_ref	text	56.7%	saas_notice, calendar_notice, ci_and_monitoring	What the mail is about, where known: a wholesale or export buyer's order number (their latest order when the conversation began); the sending system for automated mail (erp_approval, hrms_notice, crm_notice, ci_and_monitoring, saas_notice, newsletter, calendar_notice), or bounce for postmaster@pepperwind.example's notice to a Pepperwind sender that a message reached a disabled mailbox; the lure for phishing (bank_change, credential, invoice, parcel, docshare); the subject of an announcement (an org change, an office, a policy version such as POL-PRV-v3, an incident); separation: for separation mail; data_incident: for incident notices; dsar_request for request threads.
folder	text	0.0%	inbox, sent	sent for the sender's copy, inbox for a recipient's.
sent_at	text	0.0%	2023-10-01T09:30:55+05:30, 2023-10-01T10:44:03+05:30, 2023-10-01T10:46:02+05:30	When the message was sent, on the local clock of the mailbox holding this copy.
received_at	text	19.8%	2023-10-01T09:31:14+05:30, 2023-10-01T10:44:08+05:30, 2023-10-01T10:46:04+05:30	When this copy arrived in the mailbox, on the same clock. Empty for sent copies.
auto_submitted	text	69.2%	auto-generated, auto-replied	The Auto-Submitted header: auto-generated for automated mail, auto-replied for out-of-office replies and non-delivery notices. Empty for mail written by a person.
subject	text	0.0%	Upcoming service maintenance, Your schedule for 1 October 2023, [storefront] Deployment succeeded	The Subject header, subject_prefix followed by the conversation's subject. Every copy of a message has the same subject.
body	text	0.0%	Our services will undergo planned maintenance. We don't expect any downtime. You are receiving this email because you h, Your events for 1 October 2023. Invitation from the calendar. You are receiving this because you have daily agendas tur, The deployment to production finished successfully. You are receiving this because you are a member of the project.	The message's text as its sender wrote it: greeting, paragraphs and sign-off. Every copy of a message has the same text. Automated mail, notices and auto-replies carry the text of the system that sent them.
incident_ref	integer, → comms.data_incident.incident_id	99.8%	3 to 3	For an incident notice to a customer, the data incident it is about. Empty otherwise.
dsar_ref	integer, → comms.dsar_request.dsar_id	100.0%	1 to 1	For mail in a rights request's thread on the privacy mailbox, the request. Empty otherwise.

mail_item

The mail suite's message trace for conversations: one row per message, internal or with an outside party, from a thread's first message to its last reply. Each message appears once here; its copies in Pepperwind mailboxes are in email_message. Automated mail, phishing, announcements, out-of-office replies, privacy mail and separation mail are only in email_message.

27,170 rows; key item_no.

Column	Type	Empty	Range or values	Meaning
item_no	integer, key	0.0%	1 to 27170	Identifies the message in the trace.
thread_no	integer, → comms.mail_thread.thread_no	0.0%	1 to 10201	The conversation the message belongs to.
sent_at	text	0.0%	2023-10-03T10:54:38+05:30, 2023-10-03T14:08:50+08:00, 2023-10-11T21:43:50+05:30	When the message was sent, on the sender's local clock (an outside party's own time zone for mail from outside).
message_id	text	0.0%	<20231003052438.810a963a@mail.pepperwind.example>, <TETDPR08MB7826GQYCMheQcPDLhSCVUQKM@XEMFPR03MB3881.apcprd11.prod.officesuite.example>, <20231011161350.febb439e@mail.pepperwind.example>	The Message-ID header: hex@mail.pepperwind.example> with the UTC time for Pepperwind's mail, and the shape of the sender's own mail system for mail from outside.
thread_id	text	0.0%	<20231003052438.810a963a@mail.pepperwind.example>, <20231011161350.febb439e@mail.pepperwind.example>, <CAHsl-FGrmDOcYcrRLt7QEHO6m4qI_XYJkbNUezPkMKClE@mail.postbox.example>	The Message-ID of the thread's first message.
in_reply_to	text	37.5%	<20231003052438.810a963a@mail.pepperwind.example>, <CAHsl-FGrmDOcYcrRLt7QEHO6m4qI_XYJkbNUezPkMKClE@mail.postbox.example>, <20231116172323.7855579f@mail.pepperwind.example>	The In-Reply-To header: the Message-ID of the message this one answers. Empty for a thread's first message.
references	text	37.5%	<20231003052438.810a963a@mail.pepperwind.example>, <CAHsl-FGrmDOcYcrRLt7QEHO6m4qI_XYJkbNUezPkMKClE@mail.postbox.example>, <20231116172323.7855579f@mail.pepperwind.example>	The References header: the Message-IDs of the earlier messages in the thread, oldest first, space-separated. Empty for a thread's first message.
from_addr	text	0.0%	nikhil.paulose@pepperwind.example, portfolio@harbourline.example, sanjayrajendran@inmail.example	The sender's address.
to_addrs	text	0.0%	portfolio@harbourline.example, nikhil.paulose@pepperwind.example, support@ilanjibank.example	The To addresses, comma-separated.
cc_addrs	text	57.8%	purchase@investors.example, purchase@ilanjibank.example, suresh.ramanathan@pepperwind.example	The Cc addresses, comma-separated. Empty when no one was copied.
direction	text	0.0%	out, in, internal	internal (Pepperwind to Pepperwind), in (from an outside party) or out (to an outside party).
kind	text	0.0%	investors_and_board, bank_and_advisor, b2b_customer	internal, or the kind of outside party the thread is with: b2b_customer, export_buyer, vendor, logistics_partner, threepl, bank_and_advisor, investors_and_board, tax_and_regulator_portals, recruitment, payroll_and_benefits_provider, agency_and_creator or other.
subject_prefix	text	0.0%	``, Re: , Fwd:	The structural start of the subject: empty on a first message, Fwd: on a forward, Re: on a reply (Antw: or AW: from some Dutch and German correspondents).
attachment_count	integer	0.0%	0 to 5	How many files are attached.
size_kb	integer	0.0%	2 to 25603	The message's size in kilobytes, attachments included.
date_header	text	0.0%	Tue, 3 Oct 2023 10:54:38 +0530, Tue, 3 Oct 2023 14:08:50 +0800, Wed, 11 Oct 2023 21:43:50 +0530	The Date header as the sender's mail program wrote it, with the sender's UTC offset. Some outside servers write +0000 and a few senders' clocks are off, so it can differ from sent_at.
subject	text	0.0%	Loan documents, Re: Loan documents, Wholesale enquiry	The Subject header, subject_prefix followed by the thread's subject.

mail_thread

One row per mail conversation: started by a Pepperwind employee (with a colleague or an outside party) or by an outside party writing to them. Threads that got no reply have a single message. Mail an outside party sends to a shared address is filed under a colleague who reads that address.

10,201 rows; key thread_no.

Column	Type	Empty	Range or values	Meaning
thread_no	integer, key	0.0%	1 to 10201	Identifies the conversation.
mailbox_id	text, → comms.mailbox.mailbox_id	0.0%	607da667-e615-4e57-9434-7ff36e505584, c444ce60-3c14-4144-b181-094781dda62f, 4c59d7fa-ea1d-4280-bff3-89ecb3fa7849	The personal mailbox of the employee the conversation belongs to: the one who started it, or the one the outside party wrote to.
first_message_id	text	0.0%	<20231003052438.810a963a@mail.pepperwind.example>, <20231011161350.febb439e@mail.pepperwind.example>, <CAHsl-FGrmDOcYcrRLt7QEHO6m4qI_XYJkbNUezPkMKClE@mail.postbox.example>	The Message-ID of the conversation's first message (its thread_id in mail_item and email_message).
kind	text	0.0%	investors_and_board, bank_and_advisor, b2b_customer	internal, or the kind of outside party: b2b_customer, export_buyer, vendor, logistics_partner, threepl, bank_and_advisor, investors_and_board, tax_and_regulator_portals, recruitment, payroll_and_benefits_provider, agency_and_creator or other.
started_at	text	0.0%	2023-10-03T10:54:38+05:30, 2023-10-11T21:43:50+05:30, 2023-10-23T14:40:20+05:30	When the first message was sent, on the local clock of the employee the conversation belongs to.
direction	text	0.0%	out, in, internal	internal, out (Pepperwind wrote first) or in (the outside party wrote first).
related_ref	text	86.1%	ORD-IN-1061632, ORD-IN-1062321, ORD-IN-1061549	For a conversation with a wholesale or export buyer, the order number of the account's latest order placed before it began. Empty for other conversations and for buyers with no order yet.

mailbox

One row per mailbox ever created, including disabled ones: personal mailboxes (full ones for office staff, small web-only kiosk ones for Rotterdam's warehouse staff), shared addresses (orders@, ap@, privacy@, careers@ and others) and meeting rooms. Kochi's floor staff have no mailbox. Mailboxes are disabled, never deleted.

210 rows; key mailbox_id.

Column	Type	Empty	Range or values	Meaning
mailbox_id	text, key	0.0%	607da667-e615-4e57-9434-7ff36e505584, c444ce60-3c14-4144-b181-094781dda62f, 4c59d7fa-ea1d-4280-bff3-89ecb3fa7849	Identifies the mailbox (a UUID).
owner_employee_id	integer, → core.employee.employee_id	7.6%	1 to 287	The employee a personal mailbox belongs to. Empty for shared mailboxes and rooms.
address	text	0.0%	nikhil.paulose@pepperwind.example, fathima.rasheed@pepperwind.example, thomas.kuriakose@pepperwind.example	The mail address; personal ones are first.last@pepperwind.example, with a number added when the name was already taken.
display_name	text	0.0%	Nikhil Paulose, Fathima Rasheed, Thomas Kuriakose	The name shown in mail: the person's name, a shared address's name in capitals followed by (shared), or Room and the room's name.
kind	text	0.0%	user, shared, room	user (a full personal mailbox), kiosk (a small web-only personal mailbox), shared or room.
created_at	text	0.0%	2017-03-08T13:20:37+05:30, 2017-03-09T12:41:20+05:30, 2017-03-13T15:42:58+05:30	When IT created the mailbox, on Kochi's clock (IST, +05:30); for a person, up to a working week before their first day.
disabled_at	text	65.7%	2024-02-06T19:11:49+05:30, 2025-10-08T10:04:59+05:30, 2025-06-06T19:15:16+05:30	When the mailbox was disabled after its holder left, on Kochi's clock (IST, +05:30); usually the last day, sometimes days later. Empty while open.

policy

The policy register: one row per approved version of a company policy (POL--v), current or superseded.

15 rows; key policy_key.

Column	Type	Empty	Range or values	Meaning
policy_key	integer, key	0.0%	1 to 15	Identifies the policy version, numbered in order of approval.
policy_id	text	0.0%	POL-EXP-v1, POL-PRV-v1, POL-PUR-v1	The policy version's id, POL--v.
code	text	0.0%	EXP, PRV, PUR	The policy's short code, for example EXP (travel and expenses), PRV (privacy), PUR (purchasing), LEV-NL (Netherlands leave).
name	text	0.0%	Travel and expenses, Privacy, Purchasing and vendor onboarding	The policy's name.
version	integer	0.0%	1 to 3	The version number of the policy, from 1.
owner_employee_id	integer, → core.employee.employee_id	0.0%	2 to 53	The employee who owns the policy.
approved_by_employee_id	integer, → core.employee.employee_id	0.0%	1 to 175	The employee who approved this version.
approved_at	text	0.0%	2021-03-22T15:20:21+05:30, 2021-05-20T16:55:15+05:30, 2021-06-01T16:46:33+05:30	When this version was approved, on Kochi's clock (IST, +05:30).
effective	timestamp, ISO 8601 with the row's own UTC offset	0.0%	2020-04-01 00:00:00 to 2026-06-01 00:00:00	The date this version takes effect.
review_due	timestamp, ISO 8601 with the row's own UTC offset	0.0%	2021-04-01 00:00:00 to 2027-06-01 00:00:00	The date this version is due for review, a year after it takes effect. Reviews can pass without a new version.
status	text	0.0%	superseded, approved	approved for the version in force at the export, superseded once a later version has taken effect.
scope	text	0.0%	PTPL,PEBV,PINC, PTPL, PEBV	The companies the version applies to, comma-separated: PTPL (Pepperwind Trading Private Limited, India), PEBV (Pepperwind Europe B.V.), PINC (Pepperwind Inc., US).
supersedes	text	60.0%	POL-PRV-v1, POL-CLB-v1, POL-LEV-v1	The policy_id of the version this one replaces. Empty for a first version.
body	text	0.0%	Travel and expenses Policy POL-EXP-v1, version 1, effective 1 April 2021 Owner: Suresh Ramanathan. Approved by Nikhil Pa, Privacy Policy POL-PRV-v1, version 1, effective 1 June 2021 Owner: Divya Krishnamoorthy. Approved by Nikhil Paulose on 2, Purchasing and vendor onboarding Policy POL-PUR-v1, version 1, effective 1 April 2020 Owner: Fathima Rasheed. Approved b	The policy text of this version: its heading (id, version, effective date, owner and approver), its rules with the limits, windows and days in force, and from the second version on what changed.

policy_versions

One row per saved state of a policy version in the register: its drafts, then its approval, so the path from first draft to approval can be read as validity periods.

40 rows; key version_id.

Column	Type	Empty	Range or values	Meaning
version_id	integer, key	0.0%	1 to 40	Identifies the saved state.
policy_key	integer, → comms.policy.policy_key	0.0%	1 to 15	The policy version (row in policy) this state belongs to.
policy_id	text	0.0%	POL-EXP-v1, POL-PUR-v1, POL-PRV-v1	The policy version's id, POL--v.
version	integer	0.0%	1 to 4	The draft number within that policy version, from 1; the last one is the approval.
state	text	0.0%	draft, approved	draft or approved.
valid_from	text	0.0%	2021-03-06T15:20:21+05:30, 2021-03-10T19:49:46+05:30, 2021-03-16T22:13:55+05:30	When this state was saved, on Kochi's clock (IST, +05:30).
valid_to	text	22.5%	2021-03-10T19:49:46+05:30, 2021-03-16T22:13:55+05:30, 2021-03-22T15:20:21+05:30	When it was replaced, on Kochi's clock (IST, +05:30): by the next draft or the approval, or for an approval, around when the next version of the policy was approved. Empty for the approval still in force.
body	text	0.0%	DRAFT. Legal has not reviewed the second section yet. Travel and expenses Policy POL-EXP-v1, version 1, effective 1 Apr, DRAFT. Awaiting comments from the People team. Travel and expenses Policy POL-EXP-v1, version 1, effective 1 April 2021, DRAFT. Please check the limits against what finance uses today. Travel and expenses Policy POL-EXP-v1, version 1, effec	The policy text of the version as approved; a draft carries it under the note it went round for review with.