At most 80 words in a row
A list, a search, a file, a report, a match, a webhook, an email and a Slack or Teams message hold at most 80 words in a row of a source’s own text: a quote, a record’s text, a review’s excerpt, an ad’s words, a passage of a document. Each comes with its page on the source’s own site. When you write from what PodData gave you, in a file, a slide or a reply, quote at most 80 words in a row, and cite each with its page.What comes whole, and how
A whole document, transcript or recording comes only from its own route, one at a time, where it’s open to the caller:- a company’s own material: its filings, its events’ transcripts and recordings, its decks and releases, and the pages of its own site
- a transcript of a podcast, an interview or a hearing, where PodData’s review lets it out
shown is whole, or passages where it isn’t open to you, and then at most 80 words of it come with the address of the rest. A key reads a limited number whole a UTC day: see Keys and limits. A recording or a copy of an original comes as a link that works for a few minutes, never as a file to keep. A recording on YouTube plays in YouTube’s own player.
A target’s folder and its zip hold what a list holds, not the originals: read each original on its own with GET /documents/{id}.
What never leaves
- A reviewer’s or a poster’s name. PodData doesn’t keep one, so none comes back.
- A licensed history by day. A product’s price and rank history from a licensed source shows only in the workspace’s own charts, by its licence’s terms; a key gets the figures derived from it.
- Your team’s licensed figures, outside your team. Figures read through your team’s own data licence are your team’s alone, cited “Your licence”, and never go out by a report’s private link.
- Another team’s interest. Nothing PodData answers says which companies another team looks at, or that any other team does.
- Your key. Never print it, log it, commit it or write it to a file, and never ask a person to paste it to you.