| const DATA = {"slack-data-export": {"name": "Slack data export", "url": "https://aitrainingdatabroker.com/data/slack-data-export/", "holds": [["Public channels", "Open discussion by team or project. The easiest part to export, and the part with the fewest privacy questions."], ["Private channels", "Smaller groups, often finance, hiring or management. Valuable because they show real decisions, and sensitive for the same reason."], ["Direct and group messages", "One-to-one and small-group chat. Usually the most personal layer, and the one most often excluded."], ["Threads and replies", "A question and the answers under it. The thread is what turns a message into a lesson."], ["Shared files and links", "Documents, screenshots and links posted in chat. The message may export while the file stays behind."]], "limits": [["Direct messages without agreement", "Private one-to-one chat stays out unless the people in it agreed in writing and your policies allow it."], ["Channels shared with other companies", "Messages from partners and clients belong partly to them. They stay out unless the other side agrees."], ["Credentials and secrets", "Passwords, keys and access links pasted into chat are removed or the message is dropped."], ["Channels about people and pay", "Hiring, performance and compensation channels are screened out first."]]}, "gmail-data-export": {"name": "Gmail data export", "url": "https://aitrainingdatabroker.com/data/gmail-data-export/", "holds": [["Shared mailboxes", "Addresses like sales or support that several people read. The cleanest email to work with, because it was always meant to be shared."], ["Individual work mailboxes", "Each person’s inbox and sent mail. Rich, and mixed with personal messages, so each needs a rule for what counts as work."], ["Labels and folders", "How people sorted their own mail. Useful as a signal of what a message was about, when the labels were used consistently."], ["Attachments", "Quotes, contracts and photos that came with messages. Often the most valuable and the most sensitive part."], ["Calendar invites in the mail", "Meeting requests and replies that show how work was scheduled, with names and sometimes locations."]], "limits": [["Private and personal mail", "Anything that is not company work, including family, health and banking messages that landed in a work inbox."], ["Mail under privilege or confidentiality terms", "Messages with lawyers, and mail covered by a client’s confidentiality agreement, stay out."], ["Mail from people who did not agree", "A mailbox of someone who objects, or who has left and whose terms say otherwise, is left out."], ["Newsletters and automated notices", "Bulk mail and system notices add size and no judgment, and are filtered before review."]]}, "confluence-data-export": {"name": "Confluence data export", "url": "https://aitrainingdatabroker.com/data/confluence-data-export/", "holds": [["Team spaces", "Pages grouped by team or product, each with an owner. A natural unit to approve and export one at a time."], ["Decision and design pages", "The write-ups that say what was chosen, what was rejected and why. Often the most useful pages in the wiki."], ["Meeting notes and retrospectives", "What was discussed, what was agreed, and what went wrong. They hold names, so they need the most cleaning."], ["Page history and comments", "The earlier versions of a page and the comments under it, which show how an answer changed and who pushed back."], ["How-to guides and runbooks", "Step-by-step pages that staff follow. Valuable for showing a process, and easy to share once reviewed."]], "limits": [["Restricted and HR pages", "Pages limited to management, finance or people teams stay out unless that group approves."], ["Customer-specific pages", "Pages written for one client, or copied from a client’s documents, belong in the client review, not the general set."], ["Security and access details", "Pages with network diagrams, credentials or incident details that could help an attacker are removed."], ["Drafts and abandoned pages", "Unfinished or contradicted pages are filtered, since they teach the wrong thing."]]}, "salesforce-data-export": {"name": "Salesforce data export", "url": "https://aitrainingdatabroker.com/data/salesforce-data-export/", "holds": [["Accounts and contacts", "Companies and the people at them, with the fields your team fills in. The identifying layer that needs the heaviest cleaning."], ["Opportunities and stages", "Each deal, its stages and its outcome. The skeleton of the sales story."], ["Activities and notes", "Calls logged, tasks done and the notes a rep wrote. The part that explains why a deal moved."], ["Cases and service history", "If service is used, the questions customers asked and how they were resolved."], ["Reports and dashboards", "Saved views of the pipeline. They show what the company measured, and are not data in themselves."]], "limits": [["Personal contact details", "Phone numbers, personal emails and home addresses are removed or replaced with stand-in values."], ["Customer-owned data", "Records a customer put into your org, or data covered by that customer’s agreement, stay out."], ["Pricing and discount terms", "Current price books, discount rules and negotiated terms are kept out unless the owner decides otherwise."], ["Government and regulated accounts", "Accounts with data handling rules in their contracts are screened first."]]}, "hubspot-data-export": {"name": "HubSpot data export", "url": "https://aitrainingdatabroker.com/data/hubspot-data-export/", "holds": [["Contacts and companies", "Names, titles, company details and the properties your team filled in. The part that identifies people, and the part to clean first."], ["Deals with their stages", "Each opportunity, the stage it moved through and the reason a deal was marked won or lost, if anyone entered one."], ["Logged emails and notes", "Messages sent from the account and the notes a salesperson wrote. This is the conversation layer."], ["Call and meeting records", "Summaries, outcomes and sometimes recordings, depending on how your team used them."], ["Tickets and service history", "If the service tools are used, the questions customers asked and how they were answered."]], "limits": [["Contact details of customers and prospects", "Replaced with stable stand-ins so one buyer can be followed across emails, notes and deals."], ["Purchased or scraped lists", "Left out. They are not yours to license."], ["Notes with sensitive personal detail", "Removed. A note that cannot be cleaned reliably is excluded."]]}, "quickbooks-data-export": {"name": "QuickBooks data export", "url": "https://aitrainingdatabroker.com/data/quickbooks-data-export/", "holds": [["Transactions and the chart of accounts", "Every invoice, bill, payment and journal entry, and the structure the business used to organize them."], ["Customers, vendors and employees", "Names, addresses and tax details. This is the personal information that has to be removed first."], ["Memos and descriptions", "Free text on transactions where someone explained why. Short, but often the only reason on record."], ["Attachments", "Scanned receipts, contracts and statements linked to entries."], ["The audit log", "Who changed an entry and when, which shows how books were corrected."]], "limits": [["Payroll, bank and tax identifiers", "Left out entirely."], ["Customer and vendor identities", "Replaced with stand-ins that keep a relationship followable across entries."], ["Anything the business holds for clients", "A bookkeeper’s client files belong to the clients and are left out."]]}, "microsoft-365-email-export": {"name": "Outlook and Microsoft 365 email export", "url": "https://aitrainingdatabroker.com/data/microsoft-365-email-export/", "holds": [["Mailboxes", "Each person’s inbox, sent mail and folders. The richest source and the most personal."], ["Shared mailboxes", "Addresses such as support or sales that several people read. Often cleaner than personal inboxes because they hold customer conversations."], ["Archives and older mail", "Exported files from past years that people kept on their own machines."], ["Teams chats and channels", "Group and one-to-one conversations. Stored in a different place from mail."], ["Calendars and meeting notes", "Who met whom and when, with whatever notes were attached."]], "limits": [["Personal and private messages", "Excluded. Mail that is not about the company’s work does not belong in a set."], ["Names, addresses and attachments", "Names and addresses are swapped for stand-ins, and attachments are screened before they are included."], ["Privileged and regulated material", "Messages with lawyers, health or financial detail are left out unless they can be fully cleaned."]]}, "google-drive-export": {"name": "Google Drive export", "url": "https://aitrainingdatabroker.com/data/google-drive-export/", "holds": [["Documents, sheets and slides", "Working files in their native form, with the structure that a flattened copy loses."], ["Comments and suggestions", "The notes colleagues left on a document and the replies. This is where the reasoning is."], ["Version history", "Earlier states of a file, which show how a draft changed over time."], ["Shared drives for teams", "Folders owned by the company rather than a person, usually cleaner and easier to authorize."], ["Uploaded files", "PDFs, images and contracts stored alongside the native files."]], "limits": [["Files from clients and partners", "Left out unless the owner has the right to share them."], ["Names and details in documents and comments", "Replaced with stand-ins, including in the comment threads."], ["Personal files in staff drives", "Excluded. They are not about the company’s work."]]}, "jira-data-export": {"name": "Jira data export", "url": "https://aitrainingdatabroker.com/data/jira-data-export/", "holds": [["Issues with their descriptions", "The request, the bug report or the task, in the author’s own words."], ["Comments", "The discussion under each issue: questions, theories, decisions and the reason for each."], ["The history of changes", "Status moves, reassignments and edits, which show how work flowed."], ["Links between issues", "Parent, child and duplicate relationships that connect a bug to its fix and to the release."], ["Attachments and sprint records", "Screenshots, logs and the planning around each period of work."]], "limits": [["Credentials and secrets in comments", "Found and removed, and the keys changed by the team."], ["Customer names and contact details", "Replaced with stand-ins that keep an issue’s story together."], ["Projects that belong to clients", "Left out unless the client agrees."]]}, "github-repository-export": {"name": "GitHub repository export", "url": "https://aitrainingdatabroker.com/data/github-repository-export/", "holds": [["The code and every commit", "The full history of changes with their messages, branches and authors."], ["Pull requests and review comments", "The proposals, the discussions and the approvals. Kept by the service, not inside the code."], ["Issues", "Bug reports and requests with the conversations under them."], ["Workflow and build configuration", "The automated checks that run on each change and how they evolved."], ["Wikis and project boards", "Design notes and planning kept beside the code."]], "limits": [["Keys, tokens and passwords in the history", "Found across every commit and removed, with the keys changed."], ["Forks, client code and third-party code", "Excluded because the company does not own it."], ["Personal data in tests and examples", "Customer records that crept into fixtures are removed."]]}, "zendesk-data-export": {"name": "Zendesk data export", "url": "https://aitrainingdatabroker.com/data/zendesk-data-export/", "holds": [["Tickets with their subject and status", "The question, who asked, how it was categorized and where it ended."], ["The conversation", "Customer messages and agent replies in order, which is the most useful layer."], ["Internal notes", "What agents wrote to each other, which shows the reasoning behind a reply."], ["Macros and help center articles", "The standard answers the team uses and the guides it publishes."], ["Satisfaction ratings", "The customer’s own verdict on how a ticket was handled."]], "limits": [["Customer names, emails and order numbers", "Replaced with stand-ins that keep one customer’s tickets together."], ["Payment, health and account details typed in a ticket", "Removed. A ticket that cannot be cleaned reliably is left out."], ["Attachments", "Screened carefully, and left out unless they can be cleaned."]]}}; |
