Privacy Policy

Privacy Policy

Effective date: July 26, 2026


Last updated: July 26, 2026


Loglisted is an early-stage screenplay evaluation website currently operated by an individual under the name “Loglisted.” No separate corporation or other legal entity has yet been formed.


This Privacy Policy explains how Loglisted collects, uses, stores, and shares information when you visit the website, upload a screenplay, or use the screenplay-scoring service.


By using Loglisted, you acknowledge the practices described in this Privacy Policy.

1. Who Operates Loglisted


For purposes of this Privacy Policy, “Loglisted,” “we,” “us,” and “our” refer to the individual currently operating the Loglisted website and service.


Website: https://www.loglisted.com
Privacy contact: hello@loglisted.com
Mailing address: “Available upon verified legal request”


If Loglisted becomes operated by a corporation, limited liability company, or other legal entity, this Privacy Policy may be updated to identify that entity.

2. Information We Collect


Loglisted does not currently require users to create an account, log in, or provide an email address.

However, some information is still processed when you use the service.


Information You Provide


When submitting a screenplay, you may provide:

  • Project title

  • Screenplay format

  • Genre and secondary genres

  • Approximate page count

  • An optional logline

  • The screenplay PDF

  • Confirmations regarding authorship, upload rights, privacy terms, and acceptable use


You should not include unnecessary personal information in a screenplay, title page, logline, filename, or other submission field.


A screenplay may contain names, contact details, biographical information, or other personal information. Loglisted processes whatever information is included in the file you choose to upload.


Automatically Collected Technical Information


To operate the service, prevent abuse, and protect against automated submissions, Loglisted may process:


  • Internet Protocol address, which may be hashed or pseudonymized

  • Browser and device information

  • A randomly generated first-party browser or device identifier

  • Anonymous session identifiers

  • Cookies or similar local-storage identifiers

  • Submission timestamps

  • File size, type, and cryptographic file hash

  • Rate-limit and duplicate-submission information

  • Cloudflare Turnstile or similar anti-bot verification results

  • General request, error, performance, and security logs


Although Loglisted does not currently request names, emails, or account information, some of this technical data may still be considered “personal data” or “personal information” under applicable privacy laws.


Screenplay Analysis Information


When a screenplay is processed, Loglisted may generate and store:

  • Extracted screenplay metadata

  • Page, scene, character, dialogue, and formatting statistics

  • Script summaries or compressed representations

  • Genre, tone, theme, production, or structural metadata

  • Ten category scores

  • An overall score

  • Model, prompt, rubric, and processing-version information

  • Token usage, processing cost, and system-performance information


The public-facing MVP is intended to return scores rather than written coverage or analysis.


Although Loglisted does not require users to provide names, email addresses, or account information, screenplay files may themselves contain personal information, including writer names, contact information, copyright notices, representation details, or information about real individuals.


Loglisted may detect the presence of certain title-page contact information for redaction purposes. The system is designed not to retain the detected contact values as ordinary screenplay metadata. It may retain non-identifying indicators, such as whether title-page contact information was detected or redacted.

3. How We Use Information


Loglisted may use information to:


  • Receive and process screenplay submissions

  • Generate screenplay scores and metadata

  • Display results to the submitting browser session

  • Detect duplicate uploads

  • Reuse cached processing results where appropriate

  • Prevent spam, fraud, automated abuse, and excessive usage

  • Enforce submission limits

  • Monitor system reliability and performance

  • Diagnose errors

  • Estimate and control model-processing costs

  • Improve scoring methods, prompts, rubrics, and software

  • Protect the rights, security, and integrity of Loglisted and its users

  • Comply with legal obligations

  • Respond to lawful requests or disputes


Abuse-prevention information, such as IP-derived data, device identifiers, or risk signals, is kept separate from screenplay-quality scoring and is not intended to influence a screenplay’s score.

4. Artificial Intelligence Processing


Loglisted uses artificial intelligence models to summarize, classify, and score screenplay submissions.


Before screenplay text is sent to an artificial intelligence provider, Loglisted is designed to perform a local automated redaction process intended to remove or replace certain contact and identifying information that may appear on a screenplay title page or in related submission text.


This may include:


  • Email addresses

  • Phone numbers

  • Street or mailing addresses

  • Personal website addresses

  • Social-media handles

  • Agent, manager, or representative contact blocks

  • Writer contact lines

  • Writer names on title pages, which may be replaced with a generic label such as “[WRITER]”


The redaction process does not modify the original uploaded PDF. It creates a separate, temporary redacted representation for AI processing.


Redaction is automated and may not identify every item of personal information. Users should avoid including unnecessary personal information in screenplay files, filenames, loglines, or submission fields.


Depending on the system configuration, the following may be sent to a third-party artificial intelligence provider:


  • Redacted screenplay excerpts

  • Redacted screenplay chunks

  • Compressed summaries

  • Objective screenplay metadata

  • Selected representative scenes

  • The scoring rubric and evaluation instructions


Loglisted is designed not to send abuse-prevention data, IP-derived information, browser identifiers, anonymous session identifiers, professional-profile information, or writer contact information to the screenplay-scoring model.


Loglisted does not intentionally opt submitted screenplay content into third-party model training. Provider processing and retention remain subject to the applicable provider’s current API terms, account settings, contractual arrangements, and technical controls.

5. Temporary Screenplay Processing and Retention


The current MVP is designed not to retain the original uploaded PDF after processing is completed.

During processing, Loglisted may temporarily create or hold:


  • The original uploaded PDF

  • Unredacted extracted screenplay text

  • A redacted version of the text used for AI processing

  • Screenplay chunks

  • Representative excerpts

  • Summaries or compressed screenplay representations


The original PDF and unredacted extracted text are intended to remain in temporary processing memory and not be permanently stored.


Redacted chunks, summaries, or compressed representations may be cached for a limited period where necessary to prevent duplicate processing, reduce cost, recover from processing failures, or improve system reliability. These materials may be encrypted and subject to configured expiration periods.


Loglisted may retain:


  • File hashes

  • Project metadata

  • Objective screenplay metadata

  • Scores

  • Rubric, model, and prompt-version information

  • Processing-cost and performance records

  • Security and abuse-prevention records

  • Non-identifying indicators that redaction occurred


A cryptographic file hash may be stored to identify duplicate submissions. A file hash is not intended to reproduce the screenplay, but it may still be treated as protected information where required by law.

6. Legal Bases For Processing


Where applicable law requires a legal basis, Loglisted may process information on the following grounds:


  • Performance of a service: to process a screenplay and provide scores

  • Consent: where you voluntarily submit information or accept optional processing

  • Legitimate interests: to operate, secure, improve, and prevent abuse of the service

  • Legal obligations: to comply with applicable laws, court orders, or lawful requests


7. Cookies and local storage


Loglisted may use cookies and browser local storage for:


  • Anonymous session management

  • Security

  • CSRF protection

  • Rate limiting

  • Remembering a randomly generated browser identifier

  • Preserving access to a submitted result

  • Cloudflare Turnstile or similar bot-prevention functionality


Loglisted does not currently use login cookies because the MVP does not include user accounts.

You may clear cookies or local storage through your browser. Doing so may remove access to prior results or cause the browser to be treated as a new anonymous session.

8. Service Providers


Loglisted may use third-party vendors to provide infrastructure and processing services, including:


  • Website hosting

  • Serverless computing

  • Database or Redis-compatible storage

  • Cloudflare Turnstile or similar bot prevention

  • Artificial intelligence model providers

  • Error monitoring

  • Security monitoring

  • Performance analytics

  • File parsing and processing infrastructure


Potential providers may include:


  • Framer

  • Namecheap

  • Cloudflare

  • OpenAI

  • AWS


These providers may process information only as necessary to provide their services, subject to their own terms and privacy practices.


Loglisted does not sell screenplay content or personal information to advertisers.

9. Sharing of Information


Loglisted may share information:


  • With vendors that help operate the service

  • When required by law, subpoena, court order, or lawful government request

  • To investigate fraud, abuse, security incidents, or violations of terms

  • To protect the rights, property, or safety of Loglisted, users, or others

  • In connection with a merger, financing, acquisition, asset sale, reorganization, or formation of a new operating entity

  • With your consent or at your direction


Loglisted does not publicly display or distribute submitted screenplays through the MVP.

If future features allow writers to opt into discovery, manager contact, public profiles, rankings, or spotlight programs, those features will be governed by additional disclosures and choices.

10. Use of Submissions to Improve the Service


Loglisted may use derived metadata, aggregated statistics, scores, error reports, and de-identified operational data to test and improve the service.


Loglisted does not intentionally opt submitted screenplay content into third-party model training. Portions of submitted screenplays may be transmitted to AI service providers for processing and may be retained by those providers for limited periods under their applicable API terms and data-control settings.


Third-party AI providers may process submitted content according to the service tier, API terms, retention settings, and data-use controls applicable to Loglisted’s account with that provider.

11. Data Retention


Retention periods may vary by data type.


The intended MVP data retention practices are:


  • Original uploaded PDF: temporary processing only; deleted after analysis

  • Unredacted extracted screenplay text: temporary processing only; not persistently stored

  • Redacted screenplay chunks: temporary processing or short-lived cache, generally up to 24 hours

  • Representative excerpts: not stored by default; short-lived cache only if necessary

  • Chunk summaries and compressed representations: up to 30 days, where caching is enabled

  • Anonymous result: up to 30 days

  • Scores and approved project metadata: up to 90 days

  • File hash and duplicate records: up to 90 days

  • Security and abuse-prevention telemetry: up to 30 days

  • Operational logs: up to 30–90 days

  • Aggregated or de-identified statistics: may be retained longer


Loglisted may retain information for longer when reasonably necessary to:


  • Comply with law

  • Resolve disputes

  • Enforce agreements

  • Investigate security incidents

  • Prevent repeated abuse

  • Maintain backups


Loglisted does not retain the original uploaded PDF after processing. Certain redacted or derived screenplay data, including summaries, metadata, and scores, may be retained for limited periods as described in this policy.

12. Security


Loglisted uses reasonable administrative, technical, and organizational safeguards intended to protect submitted information.


These may include:


  • Encrypted HTTPS connections

  • Temporary in-memory file handling

  • Cryptographic file hashing

  • Short-lived upload tokens

  • Single-use token validation

  • Strict origin controls

  • Rate limiting

  • Cloudflare Turnstile

  • Pseudonymized or hashed IP records

  • Access controls

  • Secret management

  • Processing-cost circuit breakers

  • Separation of abuse data from scoring data

  • Local title-page contact-information redaction

  • Separation of original extracted text from redacted model text

  • Prevention of screenplay content from appearing in logs, traces, analytics, or error reports

  • Provider request-storage controls where supported

  • Configurable retention and deletion of derived screenplay artifacts


Loglisted’s redaction system is intended to reduce the amount of personal information transmitted to artificial intelligence providers, but it is not guaranteed to identify or remove every name, address, contact detail, or other item of personal information.


Personal information may appear within the body of a screenplay as part of the story, dialogue, scene headings, copyright notices, or references to real individuals. Such information may not always be distinguishable from fictional screenplay content.


Users should review their files and remove unnecessary personal information before uploading.

13. Your Rights and Choices


Depending on where you live, you may have rights regarding personal information, including the right to:


  • Request access

  • Request correction

  • Request deletion

  • Object to or restrict processing

  • Request a portable copy

  • Withdraw consent

  • Appeal certain decisions

  • Lodge a complaint with a privacy regulator


Because the MVP does not require accounts or email addresses, Loglisted may be unable to identify or retrieve a submission unless you provide sufficient information, such as:


  • Result identifier

  • Submission date

  • Project title

  • File hash

  • Anonymous result-access information

  • Other evidence reasonably necessary to verify the request


Loglisted may decline a request when it cannot reasonably verify that the requester is connected to the relevant submission.


A valid deletion request may remove the public result, project metadata, scores, stored summaries, compressed representations, representative excerpts, and related access credentials where those records are uniquely associated with the submission. Security, duplicate-detection, or abuse-prevention records may remain for their stated retention period.


Deletion from Loglisted’s systems does not necessarily cause immediate deletion from a third-party AI provider’s systems. Provider-side deletion and retention are governed by that provider’s applicable technical controls and retention policies.


Privacy requests may be sent to:


hello@loglisted.com

14. California Privacy Disclosures


California residents may have rights under the California Consumer Privacy Act and related laws, subject to applicable thresholds, definitions, and exemptions.


Loglisted does not currently sell personal information or share personal information for cross-context behavioral advertising.


Loglisted does not knowingly use sensitive personal information for purposes requiring a right to limit use.


California residents may contact Loglisted using the privacy email above.

15. International Users


Loglisted may be operated and hosted in the United States.


If you access the service from another country, your information may be processed in the United States or other jurisdictions where Loglisted’s providers operate.


Those jurisdictions may have privacy laws that differ from those in your country.

16. Children’s Privacy


Loglisted is not intended for children under 13.


Loglisted does not knowingly collect personal information from children under 13. Users must also meet any higher minimum age required in their jurisdiction to consent to online data processing.


If you believe a child submitted personal information, contact hello@loglisted.com.

17. Third-Party Links


Loglisted may link to third-party websites or services. Loglisted is not responsible for their privacy, security, or content practices.

18. Future Accounts, Profiles, and Discovery Features


Loglisted may later add:


  • User accounts

  • Email verification

  • Writer profiles

  • Saved projects

  • Payment processing

  • Subscription plans

  • Public rankings

  • Manager or producer discovery

  • Direct messaging

  • Professional profile links

  • Opt-in industry contact

  • Human review

  • Contest or spotlight submissions


Before collecting information for these features, Loglisted will update this Privacy Policy and provide any additional notices or consent choices required by applicable law.


Information collected under a future version of the service will be handled under the Privacy Policy in effect at that time.

19. Business Formation, Transfer, or Reorganization


Loglisted is currently operated by an individual and has not yet been assigned to a separate corporate entity.


If a company is later formed to own or operate Loglisted, information and service records may be transferred to that entity. Any successor entity will be required to handle information in accordance with this Privacy Policy or provide notice of materially different practices.

20. Changes to This Privacy Policy


Loglisted may update this Privacy Policy as the service evolves.


The revised policy will display a new “Last updated” date. Material changes may also be communicated through the website or submission interface.


Continued use of Loglisted after a revised policy becomes effective constitutes acknowledgment of the updated policy, to the extent permitted by law.

21. Contact


Questions, privacy requests, or concerns may be directed to:


Loglisted Privacy Contact


Email: hello@loglisted.com
Website: https://www.loglisted.com