1. Who is responsible
SamaraAnn Group LLC operates these SamaraAnn services and is responsible for the personal information it collects through them. Contact Samara@SamaraAnn.com with privacy questions or requests. This policy covers SamaraAnn.com, the SamaraAnn beta portal, and the StoryCraft beta.
2. What each service handles
| Service | Information handled | Why it is used |
|---|---|---|
| Main website | Ordinary web requests and the choices you enter into concept demos. Demo inputs stay in the current page and are not submitted to an account database. | Display company information and produce the demo result you request. |
| Beta portal | Your entered name, verified sign-in email, account matching identifier, application status, consent or acknowledgment records, and related timestamps. | Review applications, manage beta access, and communicate about your testing when needed. |
| Contact form | The name, email, subject, and message you submit; privacy acknowledgment and notice version; a reference; review status; and timestamps. Email-enabled messages also have separate notification and acknowledgement statuses, attempt counts, and timestamps. The entered email is not verified by this form. | Let Samara review your question, support issue, feedback, or data request; send the disclosed company notification and generic receipt; and manage failed or uncertain delivery. |
| StoryCraft | Your signed-in account identity and writing workspace: projects, scenes, notes, goals, artwork, publishing materials, snapshots, and recovery copies. | Open your workspace, save and recover work, and create the downloads you request. |
Publishing materials may contain an author biography or contact details you choose to enter. Include only information you want in those materials.
Beta registrations and contact messages are stored in the separate portal. Manuscripts are stored in StoryCraft’s separate writing storage. The company website does not store either collection. StoryCraft checks approval using an account-matching code and an access status; it does not copy the portal’s contact roster into your writing workspace.
3. Signing in with ChatGPT
Beta registration and StoryCraft use Sign in with ChatGPT. The app uses your authenticated account identifier and verified email to recognize you and control access. You enter the name used for your beta application.
OpenAI’s identity service may share the name, email, and profile picture shown in its sign-in flow. Sign-in alone does not give SamaraAnn your ChatGPT conversations or memory. Any additional permissions would need to be requested separately. See OpenAI’s explanation of Sign in with ChatGPT.
The public contact form does not require a ChatGPT account. Completing its security check does not establish ownership of an email address or writing account.
4. How we use information
We use information to provide the features you request, review beta applications, manage access, save and recover writing, respond to questions, handle data requests, and protect the services from misuse.
When the contact form shows its email-delivery notice, we first save your message privately, then attempt two separate emails through Zoho CPaaS, the transactional email service formerly called ZeptoMail. A copy of your name, supplied email address, subject, message, reference, and submission time goes to samara@samaraann.com. A short acknowledgement goes to the single email address you supply. That acknowledgement contains a reference and company information; it does not repeat your name, original subject, or message. Use an address you are entitled to use.
The on-screen receipt confirms that your message was saved. Acceptance by the email service does not guarantee arrival in an inbox. Delivery problems or protective limits may prevent an email without removing the saved message. Uncertain sends are not automatically repeated; Samara can review their status and explicitly retry an eligible email.
If the form shows a storage-only notice, submitting it does not automatically email your message. Turning on email delivery later does not automatically email those earlier submissions. Beta applications still do not trigger automatic invitation, approval, or marketing emails. A contact acknowledgement does not create a beta account or grant StoryCraft access.
Where applicable law requires a legal basis, providing the requested account service supports performance of our agreement with you; maintaining security and responding to inquiries supports our legitimate interests; and a permission-based activity relies on the permission requested for that activity. You can contact us to withdraw a permission. This does not undo processing already carried out lawfully or remove information needed for another applicable basis.
5. AI tools and exports
The main website’s demos use predefined local rules. StoryCraft’s AI companion currently prepares a writing request for you to review and copy. It does not automatically send your manuscript or prompt to an AI model.
If you choose to include scene text and send a request to another AI service, that service’s policies apply to what you share there. Downloading a manuscript or publishing file does not publish, submit, or email it. Files you download or share are outside the app’s access controls.
6. Service providers and security checks
We use OpenAI’s ChatGPT Sites and sign-in services for the beta portal and StoryCraft, and Cloudflare infrastructure for website delivery, storage, and security. These providers process the information needed to operate their services, including technical request, browser, device, and network information. Their own policies also describe processing they carry out for their purposes.
The company mailbox is hosted by Zoho Mail. For contact emails enabled by the form’s notice, we use Zoho’s separate transactional email service, Zoho CPaaS (formerly ZeptoMail). Zoho processes the sender and recipient addresses, email contents, and related delivery information needed to handle those emails. The service hosting a recipient’s mailbox also processes the email it receives. Our acknowledgement content is plain text, contains no tracking image, and does not request a read receipt.
The contact form uses Cloudflare Turnstile to help detect automated submissions. Cloudflare processes signals such as IP address, browser information, connection characteristics, and the website origin to protect the form and improve its bot detection. Our contact record does not store the raw verification token, IP address, or browser user-agent string. Hosting and security providers may still process technical request information.
To reduce unwanted acknowledgement emails, we apply daily limits per recipient and across the service. A private counter stores the date, counts, and a date-specific hash derived from a normalized email address. It does not contain raw email addresses, names, message contents, IP addresses, or browser identifiers. A limit can suppress an acknowledgement while leaving the saved contact and its separate company notification available.
Provider information: OpenAI Privacy Policy, Cloudflare Privacy Policy, Cloudflare Turnstile Privacy Addendum, and Zoho Privacy Policy.
These providers operate internationally. Information may be processed in countries other than yours; their notices describe their international processing and applicable safeguards. We do not promise storage in a particular country.
7. Access and protection
The portal’s roster and contact inbox require Samara’s owner account. Writing access is checked for each signed-in account. The services use server-side access checks and safeguards against one account overwriting another account’s records.
Private access does not mean end-to-end encryption or that no service operator can process the information. SamaraAnn and its infrastructure providers may process stored information as needed to operate, protect, and support the services, and when required by applicable law. No internet service can guarantee that every security risk will be eliminated.
We have not added advertising or visitor-analytics scripts to the main website. These apps do not include a feature for selling your registrations, messages, or manuscripts to advertisers.
8. Retention and recovery copies
Beta registrations, contact messages, their delivery-status records, and current writing workspaces do not presently have an automatic time-based deletion schedule. They remain stored until they are removed through an applicable account or data request or other necessary service administration. We assess requests and any legal or security need to retain information.
Contact email copies can also remain in the company mailbox. The transactional email provider may retain delivery records and message content under its settings and policies. Removing a portal record does not itself remove or recall an email copy. Data requests can include portal records, company-mailbox copies, and related provider records under our control. Acknowledgements received in your own mailbox are also subject to your email provider’s controls and retention practices.
The acknowledgement-limit counter is kept separately from contact messages. Its previous-day recipient hashes and counts are replaced when an acknowledgement attempt first uses a new UTC day. If there is no new attempt, the last counter remains; it does not accumulate a separate history for every day.
StoryCraft keeps up to 30 project snapshots per project and up to five previous workspace versions for recovery. New history can replace older history. Trimming project snapshots does not necessarily remove copies already included in earlier workspace versions or files you downloaded.
Signing out or clearing cookies does not delete cloud records or email copies. If you request deletion, tell us whether you mean your beta application, contact messages and related emails, writing workspace, and/or recovery copies. Data requests are handled manually; the current apps do not offer an automatic account-deletion button.
9. Your choices and data requests
You can download project and full-workspace backups while you have access to StoryCraft. Contact Samara@SamaraAnn.com, or use our protected contact form, to request access, a copy, correction, or deletion of information. Depending on the law that applies to you, you may also have rights to object, restrict processing, withdraw consent, or complain to a relevant data-protection authority.
Describe the service and records involved, including any contact reference and whether your request includes related company-mailbox copies. We may need to verify your identity and authority before releasing or changing information. A generic acknowledgement is not proof of identity or ownership of a writing account. Do not send a password or identity document with an initial request. We will explain any additional information needed and any limit on fulfilling the request under applicable law.
See the Cookies & Local Storage Policy for browser controls. If you contact us directly by email, your message is also handled through the email services used to send and receive it.
10. Audience and policy updates
StoryCraft is not designed for children under 13 or the applicable age of digital consent. If you believe a child has provided information contrary to this restriction, contact us so we can review it.
We will update this page when our practices change. The date at the top identifies the current notice. A stored acknowledgment records the notice version shown at that time; publishing a new notice does not create a record that you accepted it. For questions, contact Samara@SamaraAnn.com.
