Privacy Policy

1. About this policy

This policy covers Beulog at beulog.com, the account workspace, content generation and research, publishing connections, embeds, partner referrals and withdrawals, and optional reader and website analytics. It explains the information handled through those features and the choices available to account owners and readers.

For privacy questions, contact [email protected]. A website that publishes with Beulog remains responsible for its own visitor privacy information and any other services it uses. Its privacy policy may apply alongside this one.

2. Information we handle

Do not put passwords, private publishing keys, payment card details or personal information you are not authorised to share into article prompts or support messages.

3. How information is used

We use account information to create and secure your account, verify access, send account messages and provide support. Workspace information powers the research, article generation, editing, scheduling and publishing features you request.

Purchase and credit records allow us to fulfil purchases, track usage, return unused reservations, handle failed jobs, review refunds and prevent payment abuse. Connection settings let us deliver content to the websites and embeds you authorise.

Partner records let us apply referral discounts, attribute qualifying purchases to a partner, calculate and adjust commissions, review withdrawal requests and record payouts. A valid referral saved from a link is applied automatically when an eligible customer opens their dashboard after signing in and verifying their email. A customer can also enter a code in Billing. Once applied, the account is linked to that partner and cannot switch to another partner.

Operational information is used to maintain reliability, investigate faults, protect the service and meet applicable obligations. Optional reader analytics is used to produce aggregate article and reading reports for the relevant workspace owner after the reader chooses to allow collection. Optional Beulog website analytics helps our administrator understand use of the public website and improve the service.

Where applicable data-protection law requires a legal basis, processing to deliver the service supports our agreement with you; security and necessary service administration support legitimate operational interests; records required by law support those obligations; and optional reading analytics relies on the reader’s consent. Optional public website analytics also begins only after the visitor agrees.

4. Service providers and sharing

Beulog uses service providers for hosting, data storage, research and AI generation, image creation, payment processing, account email and other operations needed to deliver the service. Relevant information is transmitted to those providers when you use the corresponding features. For example, generation requires sending your topic, relevant brand settings and draft instructions for processing.

If you connect WordPress or another website, published article content and associated publishing fields are sent to that receiving site through the connection you authorise. If you choose an external sign-in option, the identity service processes the sign-in under its own privacy terms.

A referring partner can see the referral date, a masked customer email address, qualifying payment amounts and the related commission in their Partner dashboard. That dashboard does not show the customer’s full email address. Authorised administrators can review partner and withdrawal records. PayPal contact details and the information needed for payment are used to arrange a withdrawal through the payout provider. Withdrawal notification emails include relevant request and payout contact details.

Information may also be disclosed where required by law, to respond to valid legal requests, to protect the service and its users, or in connection with a business reorganisation subject to applicable protections. Contact us if you need information about the providers relevant to your use.

5. Published content and connected websites

Draft articles are accessible through authorised account and workspace access. Publishing an article, enabling an embed or exporting content changes where it can be accessed. Published articles and original image addresses can be public.

Unpublishing an article removes it from new Beulog embed requests. It does not remove WordPress imports, downloads, exports, cached pages or copies already loaded by readers. Manage imported posts on the receiving website. Disabling a connection or rotating an embed address does not recall copies already distributed.

Website allowlists help restrict supported embedding and analytics requests. They do not make published content confidential or prevent someone from copying material they can access.

6. Optional reading analytics

Reading analytics is disabled by default for workspaces and WordPress connections until their owners enable it. For a reader, collection starts only after an explicit consent choice. Articles remain readable when analytics is declined, disabled, blocked or unavailable.

The tracker respects Global Privacy Control and Do Not Track. A reader can use Turn off analytics in the article’s analytics control to stop new collection. A request already in flight may finish; withdrawing consent does not automatically erase earlier history.

Analytics tables contain article, view and short-lived session identifiers; channel; connected website origin; referring hostname; approximate device category; timestamps; visible reading time; and reading progress. They do not store IP addresses, raw user agents, names, email addresses, full visited URLs or full referrer URLs.

A reading session is scoped to a site and browser tab, and expires after up to 30 minutes of inactivity. It is not a permanent visitor profile or a cross-device identity. Reports count opted-in activity; they cannot identify unique people or represent all website traffic.

Infrastructure still receives network requests and may handle connection details separately from the analytics tables. The analytics retention rule does not describe every infrastructure log or backup.

Workspace owners can disable collection or use Delete analytics history, which clears the analytics history, disables collection and invalidates outstanding view tokens. Disabling analytics by itself keeps existing history until deletion or expiry.

7. Optional Beulog website analytics

If enabled on Beulog’s public website, this separate feature starts only after you select Allow analytics. It records public page paths, visit times, a browser-tab session identifier, device category and referring hostname. When the request carries verified Cloudflare information, it also records the connecting IP address and approximate country, region, city and time zone. Location is inferred from the network connection, not your device’s GPS, and may be inaccurate when you use a VPN or shared network.

These reports are restricted to the Beulog administrator. They exclude account and admin pages, query strings, full referrer URLs and raw browser identifiers. IP addresses are hidden after 30 days and scheduled for removal by hourly housekeeping; visit records are scheduled for removal after 90 days. They count consented activity, not unique people or all visitors, and do not link visits to account email addresses.

Select Privacy choices on a public page and then No analytics to stop new collection. The tracker also respects Global Privacy Control and Do Not Track. A request already in flight may finish. Withdrawing consent does not automatically erase earlier records; contact us to request deletion of information relating to you.

8. Cookies and browser storage

Beulog uses necessary account cookies to support sign-in and authentication flows. A language preference cookie remembers an explicitly selected interface language for one year. Browser settings can remove or block cookies, although blocking necessary account cookies can prevent sign-in from working.

Following a partner referral link saves its code and a timestamp in this browser’s local storage. The code is used for attribution for up to 30 days; an expired saved code is removed when next checked. The saved code is cleared after it is successfully applied. Clearing browser storage removes a pending code, but does not remove a partner association already applied to your account. This referral storage is separate from optional analytics.

To help prevent duplicate withdrawal requests, a pending request’s amount, PayPal email, optional note and request identifier may be kept in the browser tab’s session storage until the request is confirmed or cleared, or the browser session ends.

Optional reading analytics does not use tracking cookies. It stores the reader’s consent preference in local storage and a short-lived session in session storage. If that storage is blocked, the tracker falls back to memory. Clearing browser storage removes remembered preferences on that browser. Beulog website analytics uses its own consent preference and tab session in those same browser storage mechanisms, separate from reader analytics on connected websites.

An embedded blog’s consent choice is scoped to its host website. Other websites or independently installed services may use their own cookies and storage under their own policies.

9. Retention and deletion

Account, workspace and article records are kept while needed to provide the service and maintain your chosen content and connections. Billing, partner commission and withdrawal, security and support information may be retained for relevant accounting, dispute, abuse-prevention, operational or legal needs. The retention period depends on the type of record and the reason it is needed.

Optional reader analytics events older than 90 days are scheduled for removal approximately hourly by the service’s background process. Reports cover no more than 90 calendar days. Workspace owners can clear this analytics history sooner with the dedicated delete control. For Beulog’s public website analytics, the background process removes stored IP addresses after 30 days and visit records after 90 days. Administrator reports hide expired IP addresses even before housekeeping runs.

Infrastructure logs and backups have separate operational retention and deletion cycles; the 90-day analytics event rule does not automatically erase those copies. Published content copied to your own website or exported elsewhere is outside Beulog’s deletion controls.

To request account closure, access to your information or deletion, email [email protected] from your account email. We may need to verify your identity and assess any records that must be retained. Export content you want to keep before requesting closure.

10. Security

Beulog uses account and workspace access controls, protected authentication records, scoped and revocable publishing keys, request checks and other safeguards designed to protect the service. Access to draft content and account reports requires authorisation.

No online service can guarantee absolute security. Protect your account email and password, keep publishing keys private, and revoke a connection you no longer use. If you suspect an account or data-security issue, contact [email protected] with a description that does not expose credentials.

11. Your choices and requests

You can edit workspace content and settings, export articles, manage publication state, pause schedules, revoke publishing keys, disable embeds and control optional analytics through the available workspace tools.

Readers can decline analytics or withdraw consent through the article control. Visitors to Beulog can use the public website’s Privacy choices control. Their browser’s Global Privacy Control or Do Not Track signal also suppresses collection.

Depending on applicable law, you may have rights to access, correct, delete or obtain a copy of personal information; restrict or object to certain processing; withdraw consent; or complain to the relevant data-protection authority. These rights may have conditions and exceptions. Send a request to [email protected]. We will assess it under the law that applies and may ask for information needed to verify identity.

If your request concerns an article on someone else’s website, contact that publisher as well. We cannot remove independently published copies through Beulog’s account controls.

12. International processing

Information may be processed in locations where Beulog’s service providers operate. Data-protection requirements can differ between locations. Where applicable law requires transfer protections, those requirements apply to the relevant processing. Contact us for questions about the processing locations and arrangements relevant to your account.

13. Children

Beulog is intended for people who can legally create an account and use the service under its terms. It is not directed to children. If you believe a child has provided personal information without appropriate authority, contact us so we can assess the situation.

14. Policy updates

This policy may change as the service and applicable requirements change. The effective date at the top identifies the current version. Material changes will be communicated through the service or account email where appropriate. A new use that requires consent will require the relevant choice before that processing begins.

15. Contact

For questions about this policy, an account-data request or a reading-analytics concern, email [email protected]. Include the relevant account email or publishing website so we can understand your request. Do not send passwords, private publishing keys or full payment card details.