Privacy Policy

1. Who and what this notice covers

SoDog Enterprises Corp. is the business contact for SoDog — Next-Gen Companion Platform / Ecosystem. “We” in this notice refers to that operator. Our contact details appear below.

The current site is a static landing page with story previews and information about planned membership. The checkout preview described here is a browser-only demonstration, not a payment gateway, account system, mailing-list signup, or AI conversation interface. This notice does not describe data practices of separate mobile applications or an unlaunched companion backend.

2. Information, sources, and purposes

Technical browsing information

When your browser requests the site or an asset, the static hosting infrastructure receives standard connection and request metadata. This can include your IP address, request time, requested URL, browser or device information in request headers, and referrer information if your browser sends it. The source is your browser and its network connection, not a checkout submission.

This information is involved in delivering the requested content, operating and securing the hosting service, and diagnosing availability or technical problems. Exact logging and retention settings depend on the host and need operator verification; this notice does not promise that browsing is anonymous.

Name and email in the checkout preview

When the landing page offers the checkout preview, you may enter a name and email and select a plan. These values are used only within the open page to demonstrate the interface and its local validation. They are not sent by the preview over a network, saved by it in browser storage, or submitted to SoDog, a bank, or a payment processor.

The preview clears its entered values when it closes or the page reloads. It does not collect a card number, card security code, bank account details, or a password. Do not enter those details. Your browser's own autofill or saved-form settings are separate from storage by the preview.

Support and privacy communications

If you choose to email or call us, that is a separate communication. We receive the contact information you use, the contents of your request, and any details or attachments you provide. A future order reference may be needed for an access, refund, or cancellation issue. This information comes from you or an authorized person contacting us for you.

We use communications to respond, resolve issues, handle privacy requests, prevent misuse of support, and maintain records needed for those purposes or applicable obligations. Send only information necessary for your request. Do not send payment credentials, passwords, or sensitive information about a child or another person.

3. Recipients and external services

• Static hosting infrastructure: the host and its infrastructure providers receive the requests needed to serve the site. Their role includes delivery, operation, and security of that infrastructure.
• Google Fonts: the existing landing page loads its font stylesheet and font files from Google services. Those requests disclose connection and request metadata to Google, such as an IP address and browser headers. These standalone policy pages use a system-font stack and do not request Google Fonts.
• FlipHTML5: the embedded book iframe receives a remote book URL only when you open the book reader. Opening it connects your browser to FlipHTML5, which can receive request information and may use its own cookies or similar technology. Closing the reader unloads the embedded book; it does not delete information already received by that provider.
• Email and phone providers: when you contact support, the communication is handled through the relevant email or telephone services and by the people responsible for answering your request.

External services have their own practices and may process information outside your location. See Google's Privacy Policy and FlipHTML5's Privacy Policy for their notices. We do not control a third-party reader's internal processing merely because it appears inside this page.

Support records may also need to be disclosed when required by applicable law or a valid legal request, or as necessary to address a security issue, protect rights, or obtain professional advice. Any such disclosure should be limited to the relevant purpose. The current preview has no payment integration sending its fields to Huntington Bank Merchant Services.

4. Storage, cookies, and browser choices

The landing page code does not implement an advertising tracker or a first-party analytics collection endpoint. The checkout preview does not use cookies, local storage, session storage, or another persistent store for entered names, emails, or plan selections. This is a statement about the landing implementation, not an audit of the hosting infrastructure or third-party services.

Ordinary browser caching of static files is separate from saving form values. A third-party service you load, including the book reader, may have its own storage behavior. You can manage cookies, cache, autofill, and third-party content through your browser settings. Blocking remote resources may change font rendering or prevent a book from opening.

You can read these policies without opening a book or entering preview information. To avoid the book provider's embedded requests, do not open the reader. Google Fonts requests on the existing landing page occur as that page loads, rather than waiting for a book-reader action.

5. Retention and security

Preview fields remain only in the open page and are cleared on close or reload; the preview creates no server-side submission record. Clearing a page does not remove separate emails you sent, a provider's request logs, or information retained by your own browser.

Support and privacy-request records are retained only as needed to answer and document requests, resolve disputes, protect against misuse, and meet applicable recordkeeping or legal obligations. Necessary retention depends on the type of record, whether an issue is still open, and any applicable duty to preserve it. Records should be deleted or de-identified when no longer needed for those purposes.

Hosting and external-service logs are governed by the relevant infrastructure settings and provider practices. We do not specify an unverified retention interval for those records. Contact us for information about a particular record or a deletion request.

No internet transmission, browser, or support channel can be guaranteed completely secure. The local-only preview reduces the information submitted through the site but does not eliminate technical request data or the risks of separate communications. Avoid sending sensitive credentials and report suspected exposure to support.

6. California privacy rights

Where the California Consumer Privacy Act, as amended by the California Privacy Rights Act, applies, California residents may have the following rights, subject to the law's conditions and exceptions:

• Access and know: request the categories and specific pieces of personal information collected about you, its sources, the purposes for collection, and the categories of recipients to whom it is disclosed, sold, or shared, as applicable.
• Correct: request correction of inaccurate personal information we maintain about you.
• Delete: request deletion of personal information, subject to exceptions such as necessary legal recordkeeping or completing a requested transaction.
• Opt out of sale or sharing: direct a covered business not to sell personal information or share it for cross-context behavioral advertising, where applicable.
• Limit sensitive personal information: limit certain uses or disclosures of sensitive personal information where this right applies.
• Non-discrimination: exercise applicable privacy rights without unlawful discriminatory treatment.

The current preview does not transmit entered fields, and the landing code does not implement a sale, sharing, or advertising-preference mechanism. That observation is not a blanket assertion about all provider activity or a future paid platform. We have not established in this draft whether every hosting or third-party practice falls within California's legal definitions of sale or sharing. Operator and legal verification is required, including any required opt-out controls and recognition of applicable preference signals, before new processing is enabled.

You may contact support now to ask about sale or sharing, express an opt-out request, or request a limit on applicable sensitive-information use. We will evaluate the request against the processing involved and applicable law. You do not need a paid account to contact us.

7. How to make a privacy request

Email support@sodog.app or call +1 (224) 456-6188. Describe the right you want to exercise and the interaction involved, such as a support email or a visit to the landing page. Provide a way to reach you; please do not send a card number, password, or identity document in an initial request.

For access, correction, or deletion, we may ask for reasonable information to match the request to records we hold and verify your identity, proportionate to the sensitivity and risk of the request. We will not require you to create an account merely to make a request. Local preview values that were never submitted cannot be retrieved from a SoDog submission database.

You may use an authorized agent where permitted by law. We may require evidence of the agent's authority and, when appropriate and permitted, direct confirmation from you. Verification for a particular request will not be used to impose identity requirements on an opt-out where the law does not permit them.

We will respond under the applicable legal requirements, explain any information needed to act on your request, and explain a denial or limitation when required. Exceptions may prevent deletion of particular records or disclosure of information about someone else. Contact support if you need help submitting a request or understanding the response.

8. Family use, future service, and policy updates

Stories may be of interest to families. The current landing page is not an invitation to submit a child's personal information, voice recording, or private experiences. Parents and caregivers can contact support about information they believe was sent unnecessarily, so the request can be assessed.

Before any live checkout, account, or AI voice and companion service is introduced, this notice must be updated to explain the actual data categories, purposes, recipients, retention, security practices, and available controls for those features, including any family-use requirements. This draft makes no claim about future AI training, voice storage, or sale of platform data.

Updates will be made available on this policy page and any additional notice or consent required for new practices must be provided. The current pre-launch label distinguishes this notice from future paid-service terms. Read the Terms of Service, Refund Policy, and Delivery Policy for planned membership conditions.

9. Business and privacy contact

Use these contacts for questions about current landing-page practices, external services, support records, or exercising an applicable privacy right.