Data Export & Switching for Stringtale

Overview

Stringtale's normal workflow allows a Customer's developer to retrieve Customer Content and edits into the Customer's own codebase or source-code repository at any time, without Stringtale intervention or approval. The Customer controls that repository. The Account take-out is an additional completeness mechanism, not the Customer's only route for recovering project content.

Request and delivery

The Account Owner or another authorised representative requests an Account take-out through an available Account request method or by contacting [email protected].

Stringtale verifies the requester's identity and authority where necessary.

A Stringtale platform administrator generates the export and provides it securely to the authorised recipient.

The Account take-out is currently not self-service.

Output format

One downloadable .json file containing a single top-level Account object.

Media type: application/json. Character encoding: UTF-8. The JSON syntax follows RFC 8259.

Date and time values use RFC 3339 UTC timestamps with the Z offset.

The file is a snapshot of the Stringtale data stored for the selected Account when the export is generated.

Export scope

Account identifiers, name, status and creation/update timestamps.

Account memberships, roles, owner flags and associated user profile, contact, status and notification-preference data.

Workspaces, including identifiers, Account references, names, archive data, timestamps, assigned developers, invited editors/guests and nested projects.

Projects inside workspaces and projects attached directly to the Account, including identifiers, references, names, URLs, notes, versions, archive data, timestamps, assigned developers, invited editors/guests, integration metadata and copy.

Project integration metadata stored by Stringtale: identifiers, project references, names, types and timestamps.

Copy records and values: keys, types, versions, deletion state, selectors, current and previous values, creator/modifier references and timestamps.

Copy history: selectors, old and new values, status, versions and copy/project references.

Update-batch metadata: identifiers, project/user references, date and version.

JSON structure

The field names below are case-sensitive. number means a JSON number containing an integer value. A field marked nullable can contain null.

Account:

id:number; name:string; status:string; createdAt/updatedAt:RFC3339 string; users:AccountMembership[]; workspaces:Workspace[]; projects:Project[]

AccountMembership:

isOwner:boolean; role:string; user:User

User:

id:number; name:string|null; email:string; status:string; sendUpdates:boolean; createdAt:RFC3339 string

Workspace:

id:number; cuid:string; accountId:number; name:string; archived:boolean; archivedAt:RFC3339 string|null; createdAt/updatedAt:RFC3339 string; users:User[]; guests:WorkspaceGuest[]; projects:Project[]

WorkspaceGuest:

workspaceId:number; company:string|null; createdAt:RFC3339 string; user:User

Project:

id:number; cuid:string; accountId:number; workspaceId:number|null; name:string; url:string|null; notes:string|null; version:number; archived:boolean; archivedAt:RFC3339 string|null; createdAt/updatedAt:RFC3339 string; users:User[]; guests:ProjectGuest[]; integrations:Integration[]; copies:Copy[]

ProjectGuest:

projectId:number; company:string|null; createdAt:RFC3339 string; user:User

Integration:

id:number; projectId:number; name:string; type:string; createdAt/updatedAt:RFC3339 string

Copy:

id:number; projectId:number; key:string; type:string; version:number; deleted:boolean; modifiedById:number; createdAt:RFC3339 string; values:CopyValue[]

CopyValue:

copyId:number; selector:string; value:string; oldValue:string; createdById:number|null; modifiedById:number|null; createdAt/modifiedAt:RFC3339 string; history:CopyHistory[]

CopyHistory:

id:number; copyId:number; projectId:number; selector:string; oldValue:string; newValue:string; status:string; version:number; batch:UpdateBatch

UpdateBatch:

id:number; projectId:number; userId:number; date:RFC3339 string; version:number

Exclusions

Passwords, authentication or authorisation tokens, and sessions are not exported.

Data held only by Third-Party Services is not exported. This includes billing, invoice, payment and tax records held by Stripe or another payment provider.

Stringtale-stored project integration metadata is included; underlying content or account data held by the integration provider is not.

The Account take-out is separate from an individual's personal-data access or deletion request under data-protection law.

Known limitations

The Account take-out is manually generated and is not currently self-service.

It provides a point-in-time JSON export; it is not a continuous synchronization feed or destination-import service.

The export does not guarantee that another service can recreate Stringtale functionality or import every field automatically.

Field names and enum values reflect the current production serializer and may evolve. This page must be updated when the export structure changes.

The existing Stringtale retrieval workflow remains the primary way to bring copy changes into the Customer's own codebase. This page is not general public API documentation.

Relevant standards and specifications

JSON: RFC 8259, application/json, UTF-8.

Timestamps: RFC 3339 Internet date/time format, emitted in UTC with Z.

Stringtale does not currently use a separate destination-import schema or Stringtale-specific open interoperability specification for the Account take-out.

Infrastructure, jurisdictions and safeguards

Stringtale's primary production environment and database are hosted by TransIP in Amsterdam, the Netherlands. Network security and DDoS protection are provided through Cloudflare's global network. Database backups are stored in Cloudflare R2 using an EU jurisdiction restriction and are retained for 30 days.

Transactional and service-related email is delivered through Twilio SendGrid, provided under Stringtale's account with Twilio Ireland Limited. These emails may contain recipient contact data and, where triggered by a user, Customer Content. Stringtale does not currently use SendGrid's EU Data Residency configuration, so SendGrid processing outside the European Union and EEA cannot be excluded.

Stringtale restricts production access to authorised personnel, uses encrypted transport for application-to-database and outbound network traffic, applies EU data-location settings where available, and limits relevant log and backup retention. Service providers are subject to applicable contractual data-protection, confidentiality and security obligations.

Stringtale does not voluntarily disclose non-personal Customer data held in the European Union to third-country public authorities. Any request for access or transfer is assessed under applicable EU and Dutch law. Stringtale does not comply where doing so would conflict with that law unless the applicable conditions for lawful access or transfer under Article 32 of the EU Data Act are satisfied.