Legal
Privacy Policy
Operational beta policy · Updated: 7 November 2026
1. Who this policy covers
This policy describes the information practices of LoreAds (we, us or our) for loreads.com, our advertiser and publisher dashboards, publisher beta programme, APIs, SDKs and related services (collectively, the Services). It applies to website visitors, advertisers, publishers, publisher personnel and people whose information is included in support requests. LoreAds is currently preparing for beta and has not enabled self-serve payment collection. The legal entity that will contract with customers must be identified in the applicable customer agreement before paid commercial services begin.
2. Information we collect
Depending on how you use the Services, we may collect: (a) account and contact information such as name, email address, login and authentication details, role and support correspondence; (b) business and publisher information such as organisation name, website, chatbot name and URL, platform, integration settings, API-key identifiers and beta application details; (c) advertiser and campaign information such as campaign name, topic/category, creative text, destination URL, targeting choices, budget, schedule, review status and performance settings; (d) publisher payment administration information such as payee name, bank account details, IFSC/bank details, masked account details, payout requests and transaction records; (e) service and event information such as API requests, topic/question signals, campaign/publisher/chatbot identifiers, impressions, clicks, timestamps, spend, earnings and fraud/security events; and (f) technical information such as IP-derived security signals, country or city metadata supplied by infrastructure providers, browser/device information, logs and diagnostic information.
3. Information we ask publishers to send
The ad-serving API is designed to receive a short, non-sensitive topic or question signal to determine whether a relevant campaign exists. Publishers should send only the minimum context necessary, and must not send full conversation transcripts, message history, names, email addresses, account IDs, precise location, health information, financial account information, information about children or other sensitive personal information. The current API applies input-length limits and rejects requests without context. A topic signal may still be personal information if it can be linked to an identifiable person or account by a publisher or another party; publishers must assess their own notice and lawful-basis obligations before integrating.
4. How we use information
We use information to: create and administer accounts; authenticate users and secure API access; review and approve campaigns; register publisher chatbots; match non-sensitive contextual topics to eligible campaigns; deliver clearly identified sponsored recommendations; measure impressions, clicks and campaign performance; calculate campaign spend, publisher earnings, platform fees and payout balances; detect invalid traffic, abuse and security incidents; respond to support requests and beta applications; maintain service reliability; enforce our agreements; and comply with legal obligations or resolve disputes. We do not need full chatbot conversations to perform contextual ad matching. Separately, when you use the interactive LoreAds demo or AI support chat, the messages submitted to that feature are sent to OpenAI to generate a response. Requests may include recent messages from that feature, up to 16 messages of 800 characters each. Do not enter personal, confidential or sensitive information into these chat features. These chats are distinct from publisher topic-only ad requests.
5. How contextual advertising works
LoreAds uses campaign topics and a short topic/question signal supplied by the publisher to determine contextual relevance. The current product is designed not to build behavioural advertising profiles, retargeting audiences or cross-site interest profiles from chatbot conversations. The publisher controls the chatbot experience and remains responsible for its own collection, use and disclosure of conversation data. Advertisers receive campaign reporting and may receive event-level delivery information needed for billing, fraud review or support; the product is not designed to disclose a reader's full conversation or identity to advertisers.
6. How we disclose information
For account notices, LoreAds stores the recipient address, message and sending status. When email delivery is enabled, Resend receives the recipient, sender and message, including any public publisher guide attachment. We may disclose information to: (a) service providers that host, secure, maintain or support the Services, including application infrastructure, database, authentication, email, analytics/diagnostics and customer-support providers; (b) payment, banking and payout providers when those services are enabled; (c) advertisers and publishers, to the limited extent needed to deliver campaigns, provide reporting, resolve disputes or prevent fraud; (d) professional advisers, auditors and insurers subject to appropriate confidentiality duties; (e) law enforcement, regulators, courts or other parties when disclosure is required by law or reasonably necessary to protect rights, safety and security; and (f) a successor or transaction counterparty in connection with a merger, financing, restructuring or sale, subject to applicable law. We do not authorise service providers to use personal information for their own unrelated advertising.
7. Sale, sharing and targeted advertising
LoreAds' current contextual-ad design is not intended to sell personal information for money or disclose personal information for cross-context behavioural advertising. We do not use chatbot conversation signals to create retargeting pools. The exact treatment of identifiers, analytics, infrastructure logs and any future advertising measurement tools must be reviewed before commercial launch. If our practices change in a way that constitutes a sale, sharing or targeted advertising under an applicable privacy law, we will provide required notices and opt-out mechanisms before that processing begins.
8. Cookies, local storage and similar technologies
The current website does not use a cookie-consent banner, advertising cookies or browser storage for campaign attribution. The authenticated dashboard may use a sidebar preference cookie, and authentication and hosting infrastructure may set cookies or similar technologies necessary to provide sessions, security and core functionality. We have not identified a separate third-party advertising pixel or retargeting tag in the application source reviewed for this policy. Base44 or other infrastructure scripts may process technical telemetry; the live vendor configuration should be checked before launch. Browser controls can be used to manage or delete stored values, but disabling essential storage may affect sign-in or service functionality.
9. International processing
LoreAds is intended to serve users and businesses in multiple countries. Information may be processed in countries other than the country where it was collected, including countries where our hosting, infrastructure or service providers operate. Privacy protections and government access rules may differ between countries. Before onboarding commercial users, LoreAds must document its service-provider locations, transfer mechanisms and any country-specific disclosures or safeguards required by applicable law.
10. Retention
We retain information for as long as reasonably necessary for the purposes described in this policy, including operating accounts and campaigns, maintaining impression and click records, calculating financial balances, preventing fraud, resolving disputes, meeting tax/accounting obligations and enforcing agreements. Retention periods vary by record type and legal requirements. Security logs and request-protection signals may be retained for shorter periods than financial and transaction records. We will delete or de-identify information when it is no longer needed, subject to lawful retention exceptions. A documented record-by-record retention schedule is required before commercial launch.
11. Security
We use technical and organisational safeguards intended to protect information, including access controls, hashed API-key storage, encryption of stored publisher bank details, request validation, rate limiting and security monitoring. No internet transmission, database or security measure can be guaranteed to be completely secure. You are responsible for protecting account credentials and API keys, restricting access to them and notifying us promptly if you suspect compromise.
12. Your privacy choices and rights
Depending on your location and applicable law, you may have rights to request access to, correction of, deletion of, or a copy of personal information; to object to or restrict certain processing; to withdraw consent where processing relies on consent; or to opt out of certain sale, sharing or targeted-advertising activities. You may submit a request by emailing legal@loreads.com with the subject Privacy Request and identifying the account or service involved. We may ask for reasonable information to verify your identity and authority. We will respond within the period required by applicable law and explain if an exception applies. You may use an authorised agent where local law permits, subject to verification. We will not unlawfully discriminate against you for exercising a privacy right.
13. Additional information for California residents
If the California Consumer Privacy Act, as amended (CCPA), applies to LoreAds, California residents may have rights to know/access, delete and correct personal information; to receive information about categories of information collected, sources, purposes and categories of recipients; to opt out of sale or sharing; to limit certain uses of sensitive personal information; and to non-discrimination. Based on the current product design described above, LoreAds does not intend to sell personal information or share it for cross-context behavioural advertising. This statement must be reassessed against the actual production vendor and analytics configuration and applicable CCPA thresholds before launch. To submit a request, email legal@loreads.com with the subject California Privacy Request. We will verify and process requests as required by law. We have not yet verified that the production site detects or processes Global Privacy Control or other universal opt-out signals. Before serving residents of jurisdictions where such signals are legally required, LoreAds must implement, test and document the required signal handling and related opt-out workflow.
14. Children
The Services are business tools and are not directed to children under 13. We do not knowingly seek to collect personal information directly from children under 13. Publishers must not submit information about children or use child-directed chatbot conversations for ad matching. If you believe a child has provided personal information to LoreAds, contact us so we can review and take appropriate steps. Additional age-related laws may apply in particular jurisdictions.
15. Third-party websites and publisher services
The Services may link to third-party websites or be embedded in publisher-controlled chatbot experiences. Those third parties operate under their own privacy policies and terms. LoreAds does not control their independent practices. Publishers must provide appropriate privacy disclosures to their users and obtain any permissions or consents required for the data they send to LoreAds.
16. Changes to this policy
We may update this policy as the Services, vendors or legal requirements change. We will update the revision date and provide additional notice where required by law. The revised policy applies from its stated effective date, subject to applicable legal requirements.
17. Contact
For privacy questions or requests, email legal@loreads.com and use the subject line Privacy Request. For general enquiries, contact hello@loreads.com; for account and technical assistance, contact support@loreads.com. Before paid commercial launch, LoreAds must publish the full legal name and address of the contracting operator, a monitored privacy/grievance contact and any jurisdiction-specific representative details required by law.