Lorescent legal
Privacy Policy
Effective September 2, 2026. This is the privacy policy for Lorescent, a service operated by Story Stroll, LLC of Bangor, Maine, United States. It explains how Lorescent accesses, collects, uses, stores, retains, deletes, and shares information, including Google user data. Lorescent is an institutional story-intelligence platform for authorized organizations and their users; this is not a template or sample policy.
Information Lorescent collects
Lorescent may collect account information such as a user's name, email address, organization, role, authentication status, and preferences; institution and workspace information; billing, support, procurement, demo, and sales communications; and technical information such as browser and device details, IP address, timestamps, diagnostics, and service-usage activity. Lorescent also processes content that authorized users choose to upload, create, connect, or analyze, including interviews, transcripts, notes, quotations, source material, photographs, audio, video, documents, story concepts, research, institutional records, and collaboration activity.
Google API Services and data accessed
Connecting Google is optional and occurs only after an authorized user or institution administrator chooses to connect an account and grants the permissions displayed on Google's OAuth consent screen. Lorescent may receive the connected Google account identifier, name, email address, profile information, authorization status, and OAuth tokens needed to maintain the connection.
The institution Google Drive connection currently requests drive.readonly , drive.file , and email . Lorescent restricts use of these permissions to institution-approved Drive roots or files explicitly selected by an authorized user. It may access file and folder identifiers, names, MIME types, parent relationships, Drive identifiers, web links, timestamps, size and capability information, and approved file contents. Read access is used to list, retrieve, preview, stream, import, transcribe, index, and analyze approved source files. File-level write access is used only to create user-requested Lorescent-managed folders or files, deliver Story Study materials or release documents, and create files requested by an authorized user. Lorescent does not rename, move, alter, or delete an institution's original Drive files during ordinary archive management.
Optional Google Workspace connections may let a user send an outbound Gmail note or Lorescent link; Lorescent does not read or ingest the user's Gmail inbox. A user may separately connect Google Docs to list or import a selected document or create a requested collaborative document; Google Calendar to create requested interview, access, or story-deadline events; Google Sheets to create requested exports; or Google Slides to create requested starter presentations. Lorescent accesses only the data and functions required for the action the authorized user requests.
How Google user data is used
Lorescent uses Google account data to authenticate or identify the connected user, associate the connection with the correct Lorescent account or institution, display connection status, and maintain security and integration audit records. Lorescent uses approved Google Drive or Workspace data to perform the user-requested workflow: importing and organizing sources; previewing or streaming approved media; transcribing approved recordings; extracting, indexing, searching, and analyzing approved content; generating evidence-linked summaries, findings, Story Leads, concepts, and institutional memory; creating requested files, exports, documents, presentations, messages, or calendar events; and securing, troubleshooting, and supporting the integration.
If an authorized user requests an AI-assisted or transcription feature, the minimum content needed for that feature may be transmitted to contracted AI, transcription, hosting, or infrastructure providers acting as processors for Lorescent. Google user data is not used for advertising, sold, disclosed to data brokers, used to build advertising profiles, or used to train general-purpose AI models.
Storage and security of Google user data
Lorescent may store Google account identifiers, connection status, OAuth authorization material, file and folder metadata, imported content, generated derivatives, and integration audit records for as long as reasonably necessary to provide the requested connection and contracted service. Authorization secrets are handled through controlled integration infrastructure and are not intentionally displayed to ordinary workspace users. Lorescent uses administrative, technical, and organizational safeguards designed to protect data against unauthorized access, loss, misuse, alteration, or disclosure, including authenticated access and institution-scoped controls. No online system can guarantee absolute security.
Sharing and disclosure
Lorescent does not sell Google user data or Customer Content. Google user data may be shared only with: the connected user's institution and other authorized workspace users according to institutional permissions; contracted service providers that operate hosting, authentication, security, support, communications, AI, transcription, or data-processing functions on Lorescent's behalf; Google as necessary to operate the integration; a third party when an authorized user explicitly directs an export or delivery; or legal and governmental authorities when disclosure is required by valid law or legal process. Providers receive only the information reasonably necessary for their function and are subject to applicable contractual or operational restrictions.
Retention, deletion, and revocation
Google-derived information is retained only while reasonably necessary to provide the integration and Lorescent service, fulfill institutional instructions, maintain security and audit records, resolve disputes, or satisfy contractual or legal obligations. An authorized user or institution administrator can disconnect the Google integration in Lorescent where that control is available, revoke Lorescent access through Google Account permissions , or request deletion by emailing patrick@storystrollstudios.com . After disconnection or a verified deletion request, Lorescent stops new access through the revoked authorization and deletes or de-identifies covered Google user data unless retention is required for security, legal, contractual, backup, or legitimate audit purposes. Residual backup copies are isolated from ordinary use and removed through normal backup-expiration cycles.
Google API Services User Data Policy
Lorescent's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy , including its Limited Use requirements.
Other privacy practices and user rights
Lorescent may use cookies, browser storage, and similar technologies necessary for authentication, security, preferences, session continuity, functionality, and service measurement. Institutions control what Customer Content they place in Lorescent and are responsible for configuring access, permissions, retention, releases, and workflows consistent with their policies and legal obligations. Depending on applicable law, individuals may have rights to request access, correction, deletion, restriction, objection, or portability. Requests concerning institution-controlled Customer Content should generally be directed first to the institution responsible for the workspace.
Lorescent is not directed to children under 13 for independent consumer use. Institutions using the service in connection with minors are responsible for required permissions, consents, releases, and legal bases.
Changes and contact
Story Stroll may update this policy as Lorescent, its data practices, or applicable requirements change. The effective date will be updated, and additional notice will be provided when a change materially affects how Google user data or other personal information is used. Questions, access requests, or deletion requests may be emailed to patrick@storystrollstudios.com or mailed to Story Stroll, LLC, Bangor, Maine, United States. Do not include passwords, OAuth tokens, or sensitive source content in a request.