Acceptable Use Policy

1. General rules

You must:

• use the Services only as permitted by your plan, order form, documentation, Terms of Service, and applicable law;
• protect accounts, API keys, access tokens, credentials, and downloaded data;
• preserve LORE metadata, release IDs, quality warnings, freshness statuses, coverage statuses, source-limited warnings, leakage warnings, and training-safe flags where needed to understand data limitations;
• validate outputs before using them in research, applications, public materials, models, or trading systems;
• comply with applicable financial-services, securities, commodities, consumer protection, data protection, export-control, sanctions, advertising, and platform rules;
• cooperate with reasonable security, compliance, usage, and abuse-prevention requests.

2. Prohibited legal, abusive, or harmful uses

You may not use the Services to:

• engage in unlawful, fraudulent, deceptive, abusive, harmful, or unauthorized activity;
• violate sanctions, export controls, securities laws, commodities laws, privacy laws, intellectual property laws, consumer protection laws, or other applicable laws;
• interfere with, disrupt, degrade, overload, damage, or gain unauthorized access to the Services, our systems, our providers, or other users' systems;
• conduct malware activity, credential stuffing, phishing, scraping beyond approved access, automated enumeration, denial-of-service attacks, or vulnerability testing without written authorization;
• reverse engineer, decompile, circumvent, or bypass access controls except where applicable law expressly permits and cannot be waived;
• evade authentication, authorization, metering, quotas, rate limits, seat limits, end-user limits, export controls, download controls, or billing controls;
• share API keys across teams, users, customers, products, or organizations outside your licensed plan;
• publish, expose, embed, or commit secret API keys, credentials, access tokens, signed download URLs, or private endpoints in public repositories or client-side code;
• use the Services in a way that creates security, legal, regulatory, infrastructure, or reputational risk for LORE.

3. Data redistribution and competitive-use restrictions

You may not:

• share, sell, sublicense, rent, lease, timeshare, resell, or provide API-equivalent access to the Services outside your purchased tier;
• build, operate, or support a competing raw or substantially similar data redistribution service using LORE data;
• mirror, clone, bulk copy, or attempt to recreate the product library beyond approved usage limits;
• publish or redistribute substantial portions of LORE data, schemas, labels, release files, dataset cards, setup cards, setup definitions, research bundles, documentation, or quality reports except as permitted by your plan or written approval;
• remove, hide, alter, or falsify LORE attribution, product IDs, release IDs, schema versions, freshness metadata, quality warnings, coverage warnings, leakage warnings, source-limited warnings, or training-safe flags;
• publish LORE data, dataset cards, setup cards, research outputs, or derived outputs as if they were independently created by you without required attribution;
• expose immature outcome labels as training-safe labels;
• hide known warnings or represent warning-covered products as complete across every venue, symbol, region, or endpoint;
• provide user-provided SQL over the full LORE library unless expressly enabled in a separate agreement.

4. Financial-services, market, and trading restrictions

You may not use the Services to:

• claim that LORE recommends trades, strategies, positions, assets, venues, or portfolios;
• claim that LORE guarantees outcomes, profits, returns, alpha, model performance, or strategy performance;
• present LORE outputs as personalized financial, investment, legal, tax, accounting, or regulatory advice;
• provide regulated investment advice, commodity trading advice, broker-dealer services, copy trading, custody, order execution, portfolio management, or other regulated financial services unless you have all required licenses, registrations, exemptions, disclosures, supervision, and compliance controls;
• manipulate markets, coordinate manipulation, deceive users, spoof, pump and dump, front-run unlawfully, wash trade, or facilitate fraudulent investment claims;
• use LORE as a live execution system, brokerage, exchange, order-routing service, portfolio manager, or trading bot execution layer;
• send LORE customer exchange credentials, private exchange API keys, private account data, or order instructions unless a future product expressly supports that and provides separate terms;
• misrepresent historical outcomes, labels, examples, charts, or research bundles as guaranteed future results.

5. AI, model, and agent restrictions

You may use the Services with AI agents, prompts, notebooks, scripts, dashboards, retrieval workflows, and internal research systems as allowed by your plan. Unless your plan or written approval permits it, you may not:

• train, fine-tune, distill, pre-train, benchmark for resale, or create third-party model products using LORE data;
• create embeddings or retrieval databases for third-party resale or API-equivalent access;
• use immature labels, outcome labels, or warning-covered data as training-safe unless the applicable metadata identifies them as training_safe;
• remove leakage warnings or training-safety metadata before using data in model workflows;
• represent model outputs based on LORE data as LORE recommendations, LORE signals, or LORE advice.

6. Alpha and bulk usage controls

During controlled alpha or other limited-access periods, the following default controls apply unless we approve otherwise in writing:

You may not split accounts, rotate keys, automate around controls, or otherwise evade these thresholds. We may throttle, queue, deny, require approval for, or charge for large jobs, unusual usage, and bulk exports.

7. Attribution requirements

If you publish substantial data excerpts, charts, tables, benchmarks, public research, public reports, academic work, or derived research based on the Services, you must identify LORE / Edge Atlas as a data source unless your order form or enterprise agreement says otherwise. A suggested attribution is: "Data source: LORE / Edge Atlas."

Attribution does not give you permission to redistribute raw data, remove warnings, imply endorsement, or exceed your plan limits.

8. Security research

You may not conduct vulnerability testing, penetration testing, scanning, automated probing, or security research against the Services without prior written authorization. If you discover a vulnerability accidentally, report it promptly to info@loremoney.com and do not exploit it, access data that is not yours, disrupt the Services, or disclose it publicly before we have had a reasonable opportunity to address it.

9. Enforcement

We may investigate suspected violations of this AUP. We may throttle, suspend, revoke API keys, block downloads, require key rotation, require deletion of improperly obtained data, require attribution corrections, remove access to features, terminate accounts, notify affected parties, or take legal action if we believe activity violates this AUP, the Terms of Service, law, or platform integrity.

We may consider context, severity, risk, repetition, cooperation, harm, and legal requirements when deciding how to enforce this AUP.

10. Reporting abuse

To report abuse, security concerns, unauthorized use, missing attribution, market-manipulation concerns, or misuse of LORE data, contact:

Star Forge LLC
Email: info@loremoney.com
Website: loremoney.com