Why This Policy Exists
Scout is a shared platform. Every feed you configure uses collection, compute and storage that affect every customer. This policy keeps the platform fast and reliable, and keeps what you pay tied to what you monitor.
Focused feeds within your subscription never run into these limits. The policy covers configurations that drift outside what a subscription is built to support.
What Your Subscription Includes
Your Ordering Document states three numbers: how many entities you license, your parameter allowance, and your monthly mention allowance.
The parameter allowance is pooled, so one entity can use more parameters than another. Larger subscriptions include more parameters per entity. A single feed can hold up to 50 parameters, and most feeds work best well below that.
Entities: What You License
An entity is one real-world subject. There are six types.
- Person
- An executive, employee, principal or other individual
- Organization
- A company, agency, institution or group
- Brand or Product
- A brand, product line or ticker
- Facility or Location
- An office, site, venue or point of interest
- Domain or Credential Set
- The domains or email addresses watched for exposure
- Topic
- One monitoring subject defined by keywords
Same subject, two feeds
Counts as one entity.
Two subjects, one feed
Counts as two entities.
Monitoring more subjects than you license means adding entities to your subscription.
Parameters: What Builds Each Feed
Parameters tell Scout what to collect for an entity. There are two kinds, and both count toward your allowance.
- Identifying parameters point collection at the subject: names and variants, handles, email addresses, phone numbers, domains, URLs and tickers.
- Filtering parameters narrow the results: positive and negative keywords and rules.
A parameter counts once in each feed where you configure it.
Identifying (5)
- Brand name
- Name variant
- Name variant
- Ticker
- Main domain
Filtering (3)
- Negative keyword
- Negative keyword
- Negative keyword
Agreements That Use the Term Objects
Object capacity is your parameter allowance. The number does not change, and neither does your licensed entity count.
Earlier XTI agreements, order forms and dashboards describe an object capacity. Where those documents say mentions or monthly events, read it as your monthly mention allowance. Only the names change. Your limits stay as written.
Custom and Government Contracts
Contracts, Statements of Work and government procurement vehicles may set entities, parameters, feeds and mentions directly. Where they do, those terms govern.
The fair use provisions below apply to every subscription, whatever the contract type. If you are unsure of your terms, contact your account executive.
What Is Not Metered
Entities, parameters and mentions drive platform cost, so they are metered. How your team works with collected content is not.
- Search Within Collected Content
- Run as many follow-up searches as you need across content already collected into your feeds, with Boolean operators, filters and pivots.
- Saved Views and Filters
- Create and share as many saved views and filter combinations as your team needs.
- Alerts and Alert Rules
- Configure as many alert rules as your monitoring requires, on keywords, tags, risk categories, geography or any combination.
- Dashboards and Scheduled Reports
- Build as many dashboards as you need and schedule them for email delivery.
- Folders and Client Environments
- Organize feeds, views and dashboards into folders and client environments, and restructure them at any time.
- Forwarding and Export
- Forward posts and export filtered result sets for day-to-day work. Export quotas apply only to bulk data extraction.
What Falls Outside Fair Use
One feed per entity, with parameters tailored to that entity, is always within fair use. These patterns are not.
- Subject stacking
- Adding parameters for additional people, organizations, brands or places to one entity’s feed, so that one licensed entity monitors several subjects.
- Feed packing
- Combining unrelated subjects in one feed to avoid licensing them as separate entities.
- Parameter stuffing
- Loading feeds with broad, low-quality or duplicate parameters to widen coverage beyond your parameter allowance.
- System abuse
- Configurations that generate excessive mention volume, degrade collection or interfere with the platform for other customers.
Overloaded feeds also produce worse results: more noise and less precision.
How We Enforce This Policy
The goal is a configuration that fits your subscription, not a penalty. Each step happens only if the one before it does not resolve the overage.
-
Visibility First
Your account shows your entity count, parameters in use against your allowance, and a breakdown by feed.
-
Grace Margin on Parameters
Parameter use up to 110% of your allowance takes no action.
-
Notice
Above the grace margin, or when a feed monitors subjects beyond your licensed entities, you see a notice that explains the overage and how to resolve it.
-
Conversation Before Action
If an account stays over, we contact you to right-size the configuration or add entities or parameters to your subscription.
-
Throttling or Restriction
Where a configuration creates excessive load or is built to get around your subscription, we may throttle collection or disable specific feeds. We notify you before or when any restriction applies.
-
Suspension
A last resort, used when a notified customer takes no corrective action within a reasonable time, or when a configuration puts platform stability at immediate risk.
Feed Design Guidance
Build one feed per entity. These structures work well.
- Person Feed
- One person. Full name, name variants, email addresses, phone numbers and known handles.
- Brand Feed
- One brand. Brand name, variants, ticker, domains and key product names.
- Organization Feed
- One organization. Name, abbreviations and key identifiers.
- Location Feed
- One facility or site. Name, address variants and relevant nearby landmarks.
- Topic Feed
- One subject. The core term and closely related phrases.
Avoid putting several executives in one feed, mixing unrelated subjects, and using broad words such as “cybersecurity” or “fraud” as identifying parameters. Tailor filtering parameters to the entity in each feed.
Key Definitions
- Entity
- One real-world subject you license monitoring for: a person, organization, brand or product, facility or location, domain or credential set, or topic. Your Ordering Document states how many entities you license.
- Feed
- The collection configuration for one entity, built from parameters.
- Parameter
- One input configured in a feed: a name, alias, handle, email address, phone number, domain, URL, ticker, keyword or rule.
- Identifying Parameter
- A parameter that points collection at the entity, such as a name variant, handle or domain.
- Filtering Parameter
- A positive or negative keyword or rule that narrows what a feed returns.
- Parameter Allowance
- The total number of parameters you can configure across all feeds, stated in your Ordering Document. Identifying and filtering parameters both count. A parameter counts once in each feed where it is configured.
- Monthly Mention Allowance
- The volume of content your subscription collects and processes each month, stated in your Ordering Document.
- Object (legacy term)
- Used in earlier XTI agreements and dashboards. An object capacity is your parameter allowance.
Questions
If you are unsure whether a configuration fits your subscription, contact us at support[at]digitalstakeout.com. We would rather help you set it up right than enforce it later.
This policy supplements your DigitalStakeout Master Subscription Agreement and your Ordering Document. It does not replace them. See MSA Section 2.4 (Authorized Use Cases) and Section 6.4 (Usage Restrictions).