version v1.3 · 2026-11-19
Ludyte Privacy Policy
Version: v1.3
Effective date: The publication date shown on the service for new users; 30 days after notice of this revision for existing users. Any longer notice period required by law applies.
NationA, Inc. · support@ludyte.com
Contents
- Who we are and the scope of this Policy
- Information we collect and its sources
- How and why we use information
- AI processing, shared training, and resulting models
- Public video posts, creation materials and music sharing
- Service operations, support, and security
- Service providers, partners, and other recipients
- Analytics, advertising, marketing, and content promotion
- Retention, deletion, and continuing model use
- International processing
- Security
- Requests, withdrawal, and applicable time limits
- US state rights, regional supplements, and privacy contact
- Adult eligibility and children
- Changes, language, and contact
1. Who we are and the scope of this Policy
NationA, Inc. is responsible for personal information processed through Ludyte. Our address is 2810 N Church St STE 90780, Wilmington, DE 19802, United States. Contact support@ludyte.com for privacy inquiries.
This Policy covers Ludyte's website, accounts, creation tools, storage, publication, reuse, billing and support, as well as service personalization, improvement and analytics, AI development and training, advertising, marketing and content promotion. Each activity is subject to the purposes, limits and applicable legal requirements described here.
Section 9 of the Terms accepted during registration establishes the license in Your Content. Personal information is used on an applicable lawful basis. Where the law requires separate consent, we obtain it before the relevant processing; acceptance of the Terms or acknowledgment of this Policy does not replace that consent.
Sections 3, 4 and 8 explain personalization, analytics, training and marketing; section 5 addresses Public publication; section 9 covers retention and deletion; and sections 12 and 13 explain rights and regional conditions. Separate services you use directly, including sign-in and payment services, may have their own notices. Service-country restrictions are in section 2 of the Terms, and changes to this Policy are governed by section 15.
2. Information we collect and its sources
| Category | Examples and source |
|---|---|
| Identifiers and account information | Email, Google and Firebase identifiers, display name, authentication status and time through Google account sign-in; Ludyte account, language, and settings; from you and Google |
| Creation content and audiovisual information | Prompts, generation-related messages, images, videos, audio and other supported references you submit; frames or transcripts needed for the task; generated results and editing instructions |
| Service and commercial activity | Projects, tasks, bookmarks, publication and reuse settings, job status, quality, duration and scheduling choices, plans, free allowance and credit records |
| Billing information | Customer, subscription, order and payment references, amount, currency, status, and invoice, refund or dispute records; from you and the payment provider |
| Internet, device and network activity | IP address, approximate location inferred from IP, browser/device characteristics, session identifiers, page and interaction events, request and error information; from service operation and, for optional tracking, the choices in section 8 |
| Security and abuse-assessment records | Relevant request timestamps, frequency and sequences, concurrent jobs or sessions, account/session references, allowance and credit use, and records of investigation, restriction and review; derived from lawfully collected Ludyte service activity as described in section 6 |
| Advertising and inferred interests | Advertising or analytics identifiers where the relevant processing is introduced and required conditions are met, referral and campaign information, conversion events and inferred interests based on permitted activity; from your interaction with Ludyte, campaigns and disclosed partners |
| Communications, feedback and permissions | Support messages, reports, feedback, email delivery information, purpose-specific consent and withdrawal records, publication confirmations, and export, deletion or other rights requests |
Music creation information. Depending on the feature you choose, we process lyrics and style descriptions you enter, reference audio, images or vocal samples you upload, generated tracks and separate instrument or vocal tracks, and project edits. If you create a voice profile, we also process the selected sample, the scope of permission and records of permission or withdrawal.
Payment details are handled by the payment provider identified at checkout and in section 7. Ludyte uses payment references and transaction records; do not send full card numbers or security codes to support.
Materials you submit may contain information about other people or sensitive information. Provide only what you have authority to use and what is necessary. A photograph or voice recording is not automatically a biometric identifier, but using it to identify a person may involve additional legal requirements. A general content license does not authorize a separate biometric-identification program. We obtain additional permission and apply protections where legally required for sensitive information; unnecessary sensitive records, account credentials and payment secrets are not eligible training, advertising or promotional material. An uploader cannot waive another person's rights simply by checking a box.
3. How and why we use information
| Purpose | Information and use |
|---|---|
| Provide requested services | Account, content, Library and job information for sign-in, generation, storage, organization and delivery |
| Publication and reuse | The public package, public profile and confirmation records when you choose Public under section 5 |
| Manage purchases | Account, transaction and related support information for subscriptions, billing, refunds and records |
| Protect the service and meet obligations | Information necessary for security, unauthorized AI-agent automation and multi-account/device abuse prevention and investigation, proportionate restrictions and review, DDoS prevention, failure investigation, legal compliance and disputes; see section 6 |
| Support and rights requests | Information reasonably needed to resolve requests and verify authority where appropriate |
| Service personalization | Language and preference settings, permitted service activity and interest information |
| Service improvement, analytics and AI development | Feature-use, technical, error and feedback information, and Inputs and Outputs eligible for use under section 4 |
| Advertising and measurement | Identifiers, activity, interest and campaign information meeting the conditions in section 8 |
| Marketing communications | Contact, interest and preference information lawfully usable for the relevant marketing |
| Content promotion | Public or separately authorized content and related public profile information under section 9 of the Terms and section 8 of this Policy |
We use music creation information to compose or edit music, process voices, play, store and export files, and share them as you direct. Section 4 covers model training, section 5 explains who can access shared materials, and section 6 covers operations, security and investigation of suspected abuse.
3.1 Service personalization. We may use information you provide, permitted service activity and your selected settings to understand your needs and interests, tailor your service experience and service-related communications, and remember language choices, selections and preferences. Optional cookies, analytics and advertising are subject to section 8.
3.2 Service improvement and analytics. We may analyze feature use, user journeys, page visits, permitted email interactions, technical and error information, feedback and lawfully usable content to improve generation quality, reliability and usability and develop new features, products and services. These activities may include evaluation, classification and safety review of Inputs and Outputs, and training or improvement of NationA's AI models, algorithms and related technology under section 4. You may end future training use of affected content by deleting it or requesting account deletion. Section 9 governs deletion and retention.
3.3 Marketing. We and service providers acting on our behalf may use lawfully available contact, interest and preference information to send product news, offers and promotions and personalize those messages. We obtain prior consent where required by law. You may unsubscribe using the mechanism in the message or by contacting support@ludyte.com. Use of content in advertising or promotion is limited to content you make public on the service or separately authorize for promotion. Private content, including private content created for clients, requires your separate consent and the necessary rights. Section 8 explains the conditions.
Necessary information supports requested features and legal or security obligations; without it, we may be unable to provide the affected feature. Consents that must be optional under law are presented separately and are not replaced by acceptance of the Terms or made an improper condition of service. Section 13 explains purpose-specific bases and regional conditions. Deleting content does not always require deletion of limited necessary security or transaction records or previously lawfully anonymized aggregate findings; section 9 applies.
4. AI processing, shared training, and resulting models
Requested generation. NationA and its AI and compute providers process the prompts, relevant conversation context and reference media needed to generate, edit and deliver the content you request. This may include extracting frames, audio or transcripts, adapting materials for the selected model and safety review.
Music Studio’s song-generation model runs on GPU infrastructure we manage. This operation does not send your lyrics, reference audio, voice samples or generated tracks to the model developer. The shared-model training rules below also apply to music inputs and outputs.
Current training use. NationA does not currently use users' Inputs or Outputs to train shared AI models. The provisions below describe potential future uses within the disclosed scope and applicable law. Training use begins only after we satisfy applicable notice, lawful-basis, and consent requirements.
External AI features. We use the OpenAI API for creation-related features and request that responses to those requests not be separately stored. Data use and retention by external AI providers also depend on the features used, applicable account settings and contracts, and the provider's security and abuse-monitoring policies. A response-storage setting does not determine all provider retention or settings governing training of the provider's own models. Sections 9 and 12 govern related retention and privacy rights.
Lyrics and style suggestions, and assistance based on an image, are separate features. Where an assistant uses an external AI provider, we identify the provider and the information to be sent before you submit the request. We send only the descriptions, lyrics or selected images needed for that request, disclose the applicable provider, transfer countries and retention terms under sections 7, 9 and 10, and obtain any required consent before transmission.
Development and training of shared AI models and related technology. NationA and its affiliates may use Inputs, Outputs and related feedback to develop, evaluate, train, fine-tune and improve NationA's shared AI models, algorithms and related AI, creative and media technology, products and services, subject to the content license in section 9 of the Terms and an applicable lawful basis for personal information processing. Eligible material may include creation-related prompts, conversations, images, videos, audio, references and private work. Activities may include selection, extraction, transformation, labeling, classification, filtering, testing, safety evaluation and dataset preparation. The resulting technology may be offered commercially.
Within the disclosed and lawfully authorized scope, we determine timing and methods without obtaining additional approval or paying compensation for each dataset or training run. We begin processing that requires separate consent, additional notice, sensitive-information safeguards or other legal conditions only after satisfying those requirements. New or materially different purposes are governed by section 15. Use of previously collected content remains subject to its collection terms, valid permissions and any necessary additional consent.
Deleting content or an account. You may end future training use of affected content by deleting it or requesting deletion of your account. Content requested for deletion before training begins is excluded from future training, and deleted content will not be used in subsequent model training. An account recovery period or restricted backup retention does not authorize inclusion in new training. Section 9 governs deletion, retention exceptions and models already trained; section 12 governs rights requests and deadlines.
Processors and scope. Authorized personnel and contracted providers may process necessary material on our behalf under purpose and access restrictions. This does not permit unrelated training of suppliers' own models, standalone sales of identifiable source datasets, or training use of credentials, payment secrets or unnecessary sensitive information. Training on private material does not authorize its public disclosure, advertising or promotion; section 8 governs promotion. Training restrictions and confidentiality terms in a separate enterprise agreement prevail for the processing it covers.
Retention and existing models. Identifiable source materials, derived training copies and evaluation data are retained only while a lawful basis and content permission remain and retention is reasonably necessary for disclosed purposes, subject to section 9. Source deletion does not necessarily reverse all parameters or influences in a model already trained. Lawfully developed models, aggregate findings and improvements that are no longer personal information may continue to be used within the applicable license and law. Where a model retains personal information or a legal remedy requires action, we implement the necessary restriction, deletion or other remedy. Removing a name, pseudonymizing data or converting it to embeddings does not itself make it non-personal.
5. Public video posts, creation materials and music sharing
Public publishes the work and its creation materials together by default. After you review and confirm the publication notice, the public package includes the final video, published title and description, relevant public profile information, the prompt used for that generation, and the reference images, reference videos and other user-supplied materials actually used for that work and identified in the preview. It does not include unrelated private conversations or files, account credentials, billing information, or hidden system instructions.
The package is available through discovery, search and shared links. Public viewers may view, copy or download exposed material, and other Ludyte users may reuse it under section 10 of the Terms, including to create commercially used results. Do not publish the package if you want those inputs to remain private or lack permission to disclose them. Keeping a work private prevents community publication. Training is governed by section 9 of the Terms and section 4 of this Policy; advertising or promotion of private work requires the separate consent described in section 8. A package you make public may be used in advertising or promotion under section 8.
You can request publication removal or an end to new reuse through available controls or support@ludyte.com. Library archive/delete and community removal are separate. We stop corresponding service-side access or new reuse after processing, including associated materials, subject to necessary cache propagation. Independently downloaded copies, shares and lawfully created results may remain; applicable rights and remedies still apply.
Music sharing. New songs and music projects are private by default. Members who receive a link to a shared song, project or playlist can listen after signing in to Ludyte. If you choose organization sharing, only authorized members of that organization can listen after signing in. You can review the audience and download or remix permissions before sharing. A listener can hear material embodied in the song, including lyrics. Link or organization sharing alone does not authorize separate publication of private prompts or reference files, a public community post, or advertising or promotional use.
6. Service operations, support, and security
We use operational, diagnostic and incident-management systems to monitor availability, payment status and trends, processing failures, suspected abuse, and security threats such as DDoS attacks. These systems may process event type and time, status or error information, and relevant account, job, transaction, device or network references. Identifiers that can be linked to a user remain personal information.
Section 7 identifies the service provider and data used to investigate suspected abuse. Sentry error and performance diagnostics may also contain relevant prompts, email addresses, media-access URLs and other context needed to investigate a problem. Access by authorized personnel and providers is limited to work purposes, and authentication secrets are masked in logs and diagnostics. This operational processing does not authorize publication of private content or unrelated training or advertising. Sections 7 and 9 describe providers and retention.
User music. We do not send users’ music to an internal Slack music feed, and our operations staff do not listen to music users generate.
Customer support and privacy inquiries are received at support@ludyte.com. We receive and respond to inquiries through Google's email service, using the email address, inquiry and any attachments you provide to resolve the request. Resend is used separately to send service, transaction and other permitted messages.
We may use automated filters to detect abuse and assess safety, and analyze technical information to diagnose service failures. We process complaint identifiers, authority and contact information, evidence, and response records for rights or safety reports. Copyright notices or counter-notices may be forwarded as required by the applicable procedure; unnecessary sensitive information is limited. Intimate-image complainants’ identity or evidence is not routinely disclosed to uploaders. We may preserve relevant evidence under a lawful hold, restrict access, and disclose only what is necessary for the permitted legal or protective purpose. Such material is not automatically included in training or advertising.
Requested generation may involve technical normalization, translation, safety filtering, instruction adjustment, and extraction of relevant media features. We may use limited content and metadata for necessary moderation and to determine public-discovery eligibility. These operations do not create permission to use unrelated private material for advertising or shared model training. A safety-related feature extraction is not a promise that every input feature is immediately deleted, nor authorization for biometric identification; the applicable processing, sensitivity, retention, and provider rules still apply.
Automated and multi-account abuse prevention. We may analyze relevant first-party Ludyte account, session, request, job, allowance and transaction records to detect or investigate unauthorized AI-agent or bot access, repeated or continuous automated generation, concurrent use that evades controls, duplicate benefit claims, coordinated accounts and circumvention of restrictions. Relevant signals can include request timestamps and intervals, frequency, sequences, concurrent jobs or sessions, job outcomes, allowance and credit use, and account/session or available network/device references. We use information already collected lawfully for these purposes and link records only where reasonably necessary. This does not authorize surveillance of activity outside Ludyte or collection of new device fingerprints without the required disclosure and lawful basis. A hashed or pseudonymous identifier remains personal information when it can be linked to a person.
Automated analysis and authorized human review may help assess signals and relevant evidence; an unusual pattern, shared IP address or device, high use, or model choice alone does not prove abuse. We use the information to investigate, apply and review proportionate protections under sections 12 and 16 of the Terms, including restrictions without advance warning where permitted, prevent repeat abuse, and handle disputes. This is necessary service-security processing, separate from optional product analytics, advertising and AI-model training. It relies on the applicable legal basis, such as processing necessary to provide and protect the contracted service or a legally recognized legitimate interest assessed against your rights; where specific consent or additional safeguards are required, we apply them. Declining optional analytics does not itself disable necessary security processing. We limit information, access and retention to what that purpose requires.
If someone reports that an output was used off the service for phishing, a fraudulent payment request or deceptive impersonation, we may use the links or examples they provide, relevant output or job identifiers, and necessary account and access records to investigate, prevent harm and review enforcement. The security-incident retention rules in section 9 and the rights process in section 12 apply.
Contact support@ludyte.com to seek review of an account restriction or correct information you believe is inaccurate. Section 12 preserves applicable rights concerning automated decisions, including explanation and human review where required.
7. Service providers, partners, and other recipients
The table below describes providers and processing scopes by function for service delivery and operations, payments, support, security, analytics, and lawful marketing. We disclose the personal information needed for the relevant work according to the features actually used and the applicable lawful basis.
7.1 Providers and processing activities.
| Provider or service | Processing activities | Personal information involved | Contact |
|---|---|---|---|
| Google / Firebase Authentication | Google account sign-in, authentication, and account security | Google and Firebase identifiers, email, display name, authentication status and time | Google Cloud privacy contact |
| Google Workspace / Gmail | Receiving, answering and storing customer support and privacy correspondence | Email address, inquiries, replies, attachments and related email information | Google privacy contact |
| Amazon Web Services (AWS) | Service infrastructure, databases, video-generation compute, operational records, and backups | Account, job, and transaction references; content, references, and results needed for generation; technical and security records | AWS privacy contact |
| Runpod, Inc. | Compute for video generation and processing of related job materials | Prompts, reference media, generated results and job references needed for the relevant task | Runpod privacy contact |
| Cloudflare, Inc. (R2) | Storage and delivery of uploaded and generated content | Images, video, audio, and other content; file identifiers and related access and delivery information. Includes original audio and separate vocal or instrument tracks from supported music features. | privacyquestions@cloudflare.com |
| Vercel Inc. | Hosting and delivery of the website and administrative interface | IP address, request, device, and browser information, and information needed to serve pages | privacy@vercel.com |
| Stripe | Payments, subscriptions, customer billing portal, refunds, disputes, and payment-fraud response | Contact, transaction, and billing information needed for payment; payment references and related device and network information | dpo@stripe.com |
| OpenAI OpCo, LLC | Creation-related conversations, planning, and related image analysis and other AI features | Prompts and relevant conversations, images or extracted frames needed for the task, task context, and pseudonymized user references | contract-notices@openai.com |
| Plus Five Five, Inc. (Resend) | Service and transaction messages, lawful marketing email, and contact and delivery-event management | Email, name, relevant account and subscription information, delivery and unsubscribe records, and permitted message-interaction information | privacy@resend.com |
| Amplitude, Inc. | Product usage analytics | User and device references, feature and page activity, and related product events | privacy@amplitude.com |
| AB180 Inc. (Airbridge) | Attribution and conversion analytics and lawfully introduced performance measurement | User and device references, referral, campaign, conversion, and related events | compliance@ab180.co |
| Google Analytics 4 | Website and service usage and conversion analytics | User and device references, page and feature activity, referral, campaign, and conversion events | Google privacy contact |
| Google Ads | Importing GA4 purchase conversions, measuring advertising performance and campaign operations | Purchase-conversion events, transaction and campaign references, and measurement information needed for the connection | Google privacy contact |
| Google Cloud / BigQuery | Analysis and reporting of service events and operational records, including account and payment records | User, job, and transaction references; usage, subscription, and payment events; operational records needed for analysis | Google Cloud privacy contact |
| Functional Software, Inc. (Sentry) | Error and performance diagnostics and troubleshooting | Technical, request, and error information and diagnostic context, which may include relevant prompts, email addresses, and media-access URLs | compliance@sentry.io |
| Slack | Support for investigating suspected service abuse | Video or voice material, relevant prompts and references, account and job identifiers, email and job status as necessary for the particular case | privacy@slack.com |
Video-generation models run on compute infrastructure managed by NationA, including AWS and Runpod. Using a model does not by itself mean that user content is sent to its developer. Separate AI features using OpenAI are subject to the processing scope in the table above.
Running a music model on infrastructure we manage does not, by itself, make the model distributor a recipient of personal information. Providers handling music storage or delivery, or an assistant you choose to use, process data according to the feature and the activities disclosed in this Policy.
7.2 Processing scope and safeguards. Providers acting on our behalf receive access needed for their work, subject to contractual, security, and oversight measures required by applicable law. Payment and identity providers may also process information under their own legal obligations or for independent purposes, subject to their respective roles and notices. A provider's separate policy does not expand the training, promotional, or publication permissions you grant NationA. Section 9 governs retention and deletion, and section 10 governs international processing.
7.3 Other recipients. Within disclosed purposes and applicable law, we may disclose necessary information to affiliates, professional advisers, authorities making lawful requests, and parties to actual or proposed financing, acquisition, reorganization, or business transfers. Applicable confidentiality, access restrictions, and statutory notices apply. Public audiences may see publication packages you confirm or authorized promotional placements; other users' reuse is governed by the Terms.
7.4 Provider changes and inquiries. When providers or processing activities change, we update this Policy and provide any notice or obtain any consent required by applicable law. Contact support@ludyte.com for customer support or privacy inquiries.
8. Analytics, advertising, marketing, and content promotion
Necessary functions and preferences. Cookies, local storage and similar technologies may support sign-in, security, necessary sessions, requested functionality, and language or preference settings. Optional analytics and advertising technologies are subject to the conditions below.
Current advertising connections. We import GA4 purchase conversions into Google Ads to measure advertising performance and support campaign operations. Personalized advertising is disabled for this connection. Product analytics, advertising-conversion measurement and marketing communications are treated according to their respective purposes and lawful bases. Additional personalized-advertising processing begins only after the notice, consent, opt-out and other applicable requirements below have been met.
Analytics and advertising. We and disclosed partners may use lawfully available identifiers, service activity, interests and campaign information for product analytics, personalized or targeted advertising, audience selection and performance measurement. Where prior consent is required for optional tracking or personal information processing, collection and transmission do not begin before that consent and stop following withdrawal within applicable deadlines. Required optional consent is obtained separately by purpose without preselected choices. You may withdraw through controls for the applicable consent or preference and the contact channel in section 12; withdrawal is made as easy as giving consent. Targeted advertising may use permitted activity across services and appear on or off Ludyte. Advertising that does not use optional tracking may continue.
Marketing communications and unsubscribe. We and providers acting on our behalf may use eligible contact information to send news, offers and promotions about Ludyte and related NationA products, and tailor messages using permitted interests and preferences. We obtain any legally required prior consent for the relevant channel. You may unsubscribe through the message or by contacting support@ludyte.com. Necessary account, security and transaction communications may continue. Consent for one channel does not replace consent required for another.
Using content in advertising and promotion. We may use content you make public on the service or separately authorize for promotion in advertising or promotional materials for NationA and its AI, creative and media products and services. For Public posts, eligible material is the confirmed package actually published, including the video, prompts and references, and related public profile name or handle. Likeness or voice may be included where the necessary rights have been secured. We do not use private content, including private content created for a client, in advertising or promotion without your separate consent and the necessary rights. Public status does not replace additional privacy consent or third-party permission required by law.
Authorized materials may be selected, edited, excerpted, translated, published and distributed for the format, language and audience of websites, demonstrations, social posts, email campaigns, press materials and paid advertisements. Section 9 of the Terms permits individual edits or placements within the authorized scope without further approval or compensation. Fabricated testimonials, false endorsements, unauthorized material, credentials, payment secrets and unrelated private support communications are excluded. Contracted creative and distribution partners receive only necessary materials and limited permissions.
Content licenses and privacy rights. Sections 9 and 11 of the Terms govern license termination on content or account deletion, publication removal, and exceptions for public or reused content. Not every promotional copy will be recalled or every campaign automatically ended. You may withdraw consent for consent-based personal information processing; applicable deletion, restriction, objection and other requests are handled under the conditions and deadlines in section 12. Content-license exceptions do not limit these statutory rights. Marketing-message unsubscribe follows the instructions above. You may send related requests to support@ludyte.com.
US sale, sharing and opt-out rights. Providing identifiers or activity for cross-context behavioral advertising may constitute a sale, sharing or targeted advertising under applicable state law even without monetary payment. Where required, we provide an accessible Your Privacy Choices or Do Not Sell or Share My Personal Information control and honor legally recognized signals such as Global Privacy Control. Prior consent does not remove applicable opt-out rights, and we do not discriminate for exercising protected rights. Do Not Track is not itself an authorization signal.
Section 7 describes analytics and communications providers and the information involved; section 10 addresses international processing. Removing browser storage may reset preferences; any required consent is obtained again before optional processing restarts. Section 9 governs retention, and section 12 explains requests and deadlines.
9. Retention, deletion, and continuing model use
We retain each category of information for no longer than reasonably necessary and proportionate for its disclosed purposes, unless a specific law requires or permits limited additional retention. Where a fixed period is not reasonably possible, we use the criteria below. Retention is not unlimited merely because you once consented, and we periodically assess whether the purpose and need remain. Requests are handled under section 12; a shorter mandatory period takes precedence.
| Category | Retention period or determining criteria |
|---|---|
| Account, projects, uploads, and generated-content library | While necessary to provide the account, requested storage, publication, and related services. Content and account deletion requests are handled as described below; canceling a subscription does not itself delete an account or its content. The file removal schedule following permanent deletion of images, videos and music, and the separate account recovery period, are set out below |
| Temporary generation input and output files | Temporary staging objects have an expiration rule of one day from creation. Actual removal follows the storage service's processing cycle. Ongoing job materials and ordinary uploads or final results in the library are treated separately. Information that becomes unnecessary earlier is destroyed without delay where required by law |
| General support inquiries, replies, and attachments | While needed to resolve the inquiry and provide necessary follow-up, with deletion under applicable law when no longer needed. Only relevant portions subject to the complaint, dispute or transaction record duties below are retained separately |
| Materials sent to Slack to investigate suspected abuse | The workspace currently has no automatic expiration period for messages or files, so they remain until separately deleted. Materials no longer needed for work purposes or covered by a valid deletion request are handled through separate deletion or restriction procedures under applicable law. Limited legal retention follows the exceptions below |
| Raw product-analytics events in Amplitude | Retained based on the period necessary for product-usage analysis and improvement. Information no longer needed and valid deletion or withdrawal requests are handled under applicable legal conditions and deadlines |
| Raw analytics events in BigQuery | Daily partitions have a 425-day expiration setting. Separately retained statutory transaction records and limited provider recovery copies follow their applicable rules |
| User- and event-level analytics information in Google Analytics 4 | Event data: two months. User data: 14 months, with the user-data retention period restarting on new activity. Deletion follows the provider's scheduled cycle; this does not delete all aggregate reports or separately exported copies |
| Raw attribution and conversion analytics in Airbridge | Retained based on the period necessary for attribution and conversion analysis. Information no longer needed and valid deletion or withdrawal requests are handled under applicable legal conditions and deadlines |
| General operational logs for the service API, database, load balancer, and generation servers | Up to 90 days; container performance records up to 30 days. Statutory access-audit records, restricted incident evidence, and separate provider records are treated separately |
| Vercel runtime logs for the website and administrative interface | One day. No separate retention through an external Log Drain is used for these projects |
| Sentry error and performance diagnostic information | Error events: 90 days; logs and spans: 30 days; summarized trace metrics: 396 days. Each information type follows its applicable period; separate copies follow applicable retention and deletion rules |
| Access-audit records for operators and others accessing personal information processing systems | Where South Korea's applicable security standards require it, at least one year, or at least two years for statutory conditions such as systems processing information about at least 50,000 individuals or sensitive or unique-identification information. Retained only as needed for the applicable duty and purpose, separately from ordinary user visit logs |
| Identifiable training sources, transformed copies, evaluation sets, and linked feedback | Only if future training use begins, and while a valid license and lawful basis support retention necessary for disclosed development and validation. Content requested for deletion before training begins, and deleted content, is excluded from subsequent training |
| Lawfully developed models and de-identified or aggregate results that are no longer personal information | While useful for disclosed purposes and permitted by the license and law. Models that retain personal information remain subject to applicable rights and remedies |
| Advertising-conversion measurement and future personalized-advertising information | Current GA4 source data follows the GA4 periods above. Purchase conversions sent to Google Ads are handled under applicable provider retention and deletion rules while needed for advertising measurement and campaign operations. Purposes, periods and required choices for additional advertising processing are disclosed before it begins |
| Promotional originals, edits, and placements | While necessary for campaign preparation, distribution, evaluation, and management under a valid publication or promotional license. Section 8 governs license termination, exceptions, and privacy rights |
| Marketing contacts and preferences | Until the relevant choice is withdrawn or the purpose ends. Minimal suppression records needed to prevent unwanted messages are managed separately while that purpose and lawful basis remain |
| Consent, publication-permission, rights-request, and suppression records | While necessary to demonstrate compliance and resolve disputes, considering statutory record duties, relevant claim periods, and continuing restrictions. Not used as an alternative training or marketing dataset |
| Payments, billing, refunds, consumer complaints, and disputes | While necessary for the transaction and applicable tax, accounting, dispute, and record duties. Where Korean e-commerce rules apply: advertising records six months; contract/withdrawal and payment/supply records five years; consumer complaint/dispute records three years. Only the relevant records are retained separately |
| Restricted security and abuse-incident evidence | For the period lawfully necessary to investigate an incident, apply or review a restriction, prevent repeat abuse, or address a related claim. Necessity is reviewed periodically and records are destroyed when the purpose ends. This is not a blanket ground to retain all content long-term |
| Prepared account export | Download access lasts seven days after preparation; expired working copies are removed through scheduled cleanup and applicable request rules |
| Specified technical billing-event and restricted service-request tracing records | Scheduled cleanup of processed/skipped billing events after 90 days and specified service-request tracing records after 180 days, subject to lawful holds. These are not the periods for statutory personal-information-system access audits or all financial records |
| Restricted backups and recovery copies | Operational database automated backups: 35 days. Separate AWS Backup copies: daily 35 days, weekly 84 days and monthly 365 days, including the corresponding copies in Japan. Retention and deletion remain subject to lawful purposes and the restricted-backup rules below |
Content or account deletion and future training. You may end future training use of affected content by deleting it or requesting account deletion. Content requested for deletion before training begins is excluded from future training, and deleted content will not be used in subsequent model training. Account recovery or backup retention does not permit inclusion of that content in new training. This section and section 13 of the Terms govern the account's 30-day recovery period, limited backups and lawful retention exceptions. Deletion, restriction and consent-withdrawal requests are handled with necessary verification and under applicable legal conditions and deadlines, including any requirement for action without delay or a shorter deadline. Section 12 governs statutory deadlines and the availability of exceptions.
Deletion procedures and recovery copies. Deleting ordinary content in the service marks the item as deleted; its source file may remain in storage until a separate removal procedure is completed. Account deletion includes cleanup of linked files and the authentication account. Copies sent to external services require the relevant deletion or restriction action for each service; a deleted status in the interface does not mean that all copies have been removed simultaneously. The 30-day account recovery period, 35-day automated database backups and separate 35-, 84- and 365-day backup cycles are distinct. Removing one user's information immediately from a full database backup may not be technically feasible. Restricted recovery copies are retained only where law permits, and deletion requests must be reapplied before restored copies return to ordinary use. Backups and technical limitations do not authorize new training or advertising or override mandatory deletion duties. Valid deletion and withdrawal requests follow the legal conditions and deadlines in section 12.
Image, video and music files. When you confirm permanent deletion of an asset, video, song or music project, access to that item through the service ends immediately. We remove the private image and video originals, and the original audio, previews and separate vocal or instrument tracks belonging to that item from active storage once 30 days have elapsed from the recorded permanent deletion. You cannot restore the permanently deleted item during that period. If a separate copy exists in your Library, the same schedule applies when you delete that copy. Where a published work or another asset still lawfully uses the same file, we retain it only for as long as needed for that use. This section’s separate rules apply to legal holds and restricted backups. A shorter period required by law takes precedence. For the scope or status of an individual deletion, contact support@ludyte.com.
Consent withdrawal and restrictions. Withdrawal of processing based on consent is implemented within any applicable shorter deadline. We do not switch to an unrelated new legal basis to continue the same optional processing after consent is withdrawn. Necessary retained records are access-restricted and used only for their legal or protective purpose. Models lawfully developed before deletion and other copies remain subject to the conditions below.
Models and other copies. An already trained model is not simply a directory of source files. Source deletion does not necessarily reverse every learned parameter, and no automatic destruction or retraining of every model is promised. Continuing use is limited by the conditions in section 4 and applicable law; if personal information remains, required rights and remedies still apply. Independent public copies, previously authorized user results and distributed promotional copies may not all be retrievable. We continue to address lawful removal and rights requests.
Limited retained records. A binding legal duty, reasonably necessary defense of a claim or documented security incident may justify keeping relevant records for the applicable period. They remain access-restricted and used for that purpose, rather than for unrelated training or advertising. Where Korean e-commerce record rules apply, the relevant advertising records are retained six months, contract/withdrawal and payment/supply records five years, and consumer complaint/dispute records three years. Those periods do not require storing all videos or prompts.
When a retention purpose ends and no exception applies, we destroy personal information without delay as required by applicable law, or may properly anonymize it where law permits. Statutory records are separated from other information and managed only for the required retention purpose. Removing an account name alone is not de-identification.
Retention assessment and exceptions. We may consider model usefulness and lifecycle, dataset relevance and reproducibility, service continuity, the nature and sensitivity of the data, fraud patterns, outstanding disputes, limitation periods, legal duties, and technically necessary backup cycles. An exception preserves only the information reasonably needed for its purpose. Properly de-identified data that is no longer personal information may be used and disclosed without a fixed end date for lawful research, product development, security, aggregate reporting, and business purposes within the applicable content license. We maintain non-reidentification safeguards and appropriate recipient restrictions. Neither encryption, removal of a name, nor conversion to an embedding automatically makes information non-personal.
Provider records and recovery copies. Our general support-inquiry period and an email-delivery provider's sending records are different categories, as are a content library and an external authentication provider's records. For example, Firebase Authentication may take up to 180 days to remove authentication data from its live and backup systems after we initiate user deletion; default OpenAI API abuse-monitoring logs may be kept for up to 30 days, subject to applicable exceptions. These periods do not automatically apply to other data. Where a shorter deletion duty applies, we take the necessary steps to meet it.
Provider-specific retention rule. Our category-level rules apply across providers processing for us. A hosting, inference, email or analytics supplier is not given an unlimited independent retention right merely because its commercial contract continues. We may retain information needed for an authorized development cycle, reproduce or audit results, protect against repeat abuse, resolve a claim, or satisfy a record obligation, considering necessity and proportionality and recording the relevant reason. We may separate active records, restricted legal evidence and backups; moving a record into an archive does not change its permitted purposes. When a provider independently determines a legally required payment or security record, its own lawful obligations may require a different period. For inactive backups where deferred deletion is legally permitted, access is restricted until the documented deletion/overwrite cycle, and deletion instructions apply before restored copies return to ordinary use. No universal supplier-wide deletion date, zero-retention promise, or automatic minimum period for all personal content is created by this Policy.
10. International processing
NationA is incorporated in the United States, and personal information may be stored, processed or accessed outside your country of residence. The service API and operational database use AWS infrastructure in South Korea, and database backups are also copied to Japan. Video-generation processing includes an AWS compute path in India (Mumbai) and Runpod compute paths in the United States, India and Europe. Actual processing locations may vary by job allocation and feature.
10.1 Processing and storage locations by service.
| Service | Processing or storage location and scope |
|---|---|
| Google / Firebase Authentication | Authentication information is processed in the United States |
| Google Cloud / BigQuery | Service events and operational reporting data are processed in the United States |
| AWS | Operational API and database: South Korea. Database backup copies: Japan. Generation-compute path: India |
| Runpod | Compute infrastructure in the United States, India and Europe, depending on job allocation |
| Vercel | Website and administrative function execution: South Korea (Seoul) and the United States (Northern Virginia). CDN and operational metadata follow the provider's applicable processing scope |
| Sentry | Error and performance diagnostic information is processed and stored in the United States region |
| Cloudflare R2 | Object storage uses an APAC placement preference, which does not guarantee storage within any particular country |
| Amplitude | Product analytics information is sent to its United States collection endpoint |
| Resend | Email is sent through its Japan (Tokyo) region; customer data, including message content, delivery logs and webhooks, is stored in the United States |
| Airbridge | Analytics information is stored on AWS infrastructure in Japan (Tokyo) |
Storage locations may differ from transmission and remote-access locations. International processing by other hosting, storage, payment, AI, diagnostics and collaboration services follows the applicable service configuration, contracts and lawful transfer scope. We provide legally required country, recipient and other transfer disclosures before the relevant processing. Changes to disclosed countries, recipients or other transfer details follow applicable notice and consent procedures.
Song generation, audio storage and delivery, and external assistants may use different processing routes. Before introducing a new international transfer for a music feature, we disclose the actual recipient and countries, data, purpose, timing, method and retention period, as well as applicable ways to decline, and obtain any consent required by law.
10.2 Information, purposes, timing and methods. The information transferred, purposes and provider contacts are described in the provider table in section 7. Retention, use periods and deletion follow the rules in section 9 for each information category. Information is transmitted over encrypted network connections when the relevant feature is used or the activities below take place.
| Provider or service | Transfer timing | Transmission method |
|---|---|---|
| Google / Firebase Authentication | Sign-in, authentication and account management | Encrypted transmission through authentication SDKs and APIs |
| Google Workspace / Gmail | Receiving, answering and storing customer support and privacy inquiries | Encrypted email and administration-service connections |
| AWS | Service requests, generation, storage and operational-record processing | Encrypted service connections and APIs |
| Runpod | Allocation of generation jobs to the compute infrastructure and processing of inputs and results | Encrypted job-control connections and file transfers |
| Cloudflare R2 | Content upload, storage, delivery of generated results and viewing | HTTPS and object-storage APIs |
| Vercel | Webpage or feature requests and related diagnostics | HTTPS |
| Stripe | Payments, subscriptions, customer billing portal, refunds and disputes | HTTPS, payment APIs and webhooks |
| OpenAI | Requests using the relevant AI features | Encrypted API requests |
| Resend | Service, transactional or permitted marketing emails, and contact or delivery-event processing | Encrypted API and webhook connections |
| Amplitude | Permitted product-event collection and transmission | Encrypted SDK and API transmission |
| Airbridge | Permitted attribution and conversion-event collection and transmission | Encrypted SDK and API transmission |
| Google Analytics 4 | Permitted page, feature and conversion-event collection and transmission | Encrypted transmission through tags and measurement APIs |
| Google Ads | Importing GA4 purchase conversions and measuring advertising performance | Encrypted connections between Google services |
| Google Cloud / BigQuery | Loading, updating and reporting on event or operational analytics data | Encrypted API connections |
| Sentry | Error and performance diagnostic collection and transmission | Encrypted SDK transmission |
| Slack | When relevant material is sent for review in a suspected abuse case | HTTPS or encrypted API connections |
10.3 Transfer grounds and safeguards. International transfers are subject to the legal grounds and safeguards required by applicable law. Where South Korea's Personal Information Protection Act applies, we rely on contractual necessity for entrusted processing or storage only when the statutory disclosure and notification conditions are met, and obtain separate consent where required. Transfers from the EEA or UK are subject to applicable adequacy decisions, properly executed standard contractual clauses, or other safeguards required by law.
10.4 Refusing or withdrawing from transfers. Send international-transfer inquiries and applicable refusal or withdrawal requests to support@ludyte.com. Identify your account and the processing you wish to refuse or withdraw from. Following any necessary identity verification, we handle the request under the procedure and deadline required by applicable law. Refusing a transfer necessary for a requested feature may prevent us from providing that feature. Refusing optional processing does not restrict unrelated core functionality. Sections 9 and 12 govern retention, deletion and the exercise of rights.
11. Security
We use access restrictions, authentication controls, secure credential handling and measures to limit unnecessary personal information in diagnostics. Access by personnel is limited to their responsibilities. No service can guarantee absolute security, and Ludyte is not an end-to-end encrypted messaging service.
Report suspected exposure or unauthorized access to support@ludyte.com. We investigate and provide notices required by applicable breach-notification law.
No internet service can guarantee absolute confidentiality, uninterrupted storage, or complete prevention of unauthorized access. You should protect your account and avoid submitting unnecessary sensitive material. These limitations do not waive our statutory security or breach-notification duties or make you responsible for a breach caused by us.
12. Requests, withdrawal, and applicable time limits
Requests for access, correction, deletion, restriction, portability, recipient information, applicable objections or withdrawal of consent may be sent to support@ludyte.com. We process requests under the conditions, procedures and deadlines of applicable law. Sections 4 and 9 govern ending future training use through content or account deletion; section 8 governs advertising, marketing and promotion requests. We do not improperly restrict core generation for exercising protected rights or declining legally optional consent, and no new account is required to exercise rights.
Receipt and implementation. We receive and respond to requests at support@ludyte.com. After any necessary verification, we stop, delete, or restrict the relevant processing according to the request and applicable law, and implement necessary action for related copies held by processors acting on our behalf. Information that must be retained by law is separated or restricted to that purpose; we explain the outcome and applicable exceptions as required by law.
Ordinary requests. Unless a shorter period applies, we generally respond to access, correction and deletion requests within 45 calendar days after receipt. Where reasonably necessary and legally permitted, we may extend by up to a further 45 calendar days, for a total of 90 days, after giving the required notice and reasons within the initial period. Verification does not restart the clock. Where California's acknowledgment rule applies, we confirm receipt within 10 business days. Extensions are not automatic or a reason to delay unnecessarily.
Consent withdrawal and advertising opt-outs. These may have shorter limits than ordinary requests. We implement them as soon as reasonably practicable within the applicable deadline. Where Delaware's consent-withdrawal rule applies, consent-based processing stops no later than 15 calendar days after receipt. Where California's sale/sharing or sensitive-information limitation rule applies, the applicable request is implemented as soon as feasibly possible and no later than 15 business days. Other applicable shorter deadlines prevail. Marketing emails can be stopped using the unsubscribe mechanism, and applicable marketing-law time limits are respected. The 45/90-day ordinary request window does not extend these limits.
Verification and exceptions. We request only information reasonably needed to verify a request that requires verification or an agent's authority, and do not impose verification on an opt-out when prohibited. We may deny or limit a request only as law permits, explain the reason and process the remainder where required. Necessary legal, security, dispute and recordkeeping exceptions are limited as described in section 9; they are not broad permission for continued optional use. We do not discriminate for exercising protected rights. Applicable sale/sharing, targeted-advertising, profiling and sensitive-information rights and recognized preference signals are respected as described in section 8.
Appeal and review. Reply to our decision or email support with the request reference to seek review. Where an appeal right applies, we follow its procedure and deadline, including a response within 60 days under applicable Delaware law, and explain the result and complaint route. Where law grants rights concerning solely automated decisions with legal or similarly significant effects, you may request the required information, challenge or human review. You can contact the competent regulator or pursue an available legal remedy without first completing our internal process.
Withdrawal does not retroactively invalidate lawful earlier processing. Sections 4 and 9 explain already developed models, de-identified information, backups and retained records; sections 5 and 8 address publication and promotion. One request may address several choices if you identify them.
Legally permitted limits. We may decline requests we cannot reasonably verify where verification is allowed, or requests subject to a statutory exception. We may charge a reasonable fee or decline a manifestly unfounded, excessive, or repetitive request only to the extent the applicable law permits and after giving the required explanation. For EEA/UK rights requests, the ordinary response period is one month, extendable by up to two further months when legally justified with notice within the first month; shorter applicable rules prevail. Urgent intimate-image removal and other special legal processes are not governed by the ordinary 45/90-day privacy-request window. Nothing in the Terms’ arbitration or liability provisions prevents an applicable regulatory complaint or waives a non-waivable privacy remedy.
Abuse decisions and relevant information. To ask about or contest an abuse-related restriction, seek correction of relevant information, or request any explanation, objection or human review available under applicable law for an automated decision, email support@ludyte.com with your account reference and the decision you are questioning. We apply the relevant legal procedure and deadline. Security-based limits on disclosing detection details do not remove rights we are legally required to provide. The ability to take an immediate protective measure under the Terms does not waive these rights.
13. US state rights, regional supplements, and privacy contact
US state laws. The rights that apply depend on your residence, the processing involved and the law's scope, including applicable thresholds and exceptions. Where relevant, sections 2–3 identify categories, sources and purposes; section 7 identifies recipients; section 8 addresses sale, sharing and targeted advertising; section 9 explains retention; and section 12 explains rights, verification and appeal. Additional collection, recipient, sale/sharing, and sensitive-information disclosures are provided as required by the law applicable to the processing. A prior consent does not waive a protected right. Delaware residents can also contact the Delaware Department of Justice; California residents can consult the California Attorney General's privacy information.
Privacy contact. Ludyte Customer Support Team; contact person: Jay. Email support@ludyte.com or write to NationA, Inc., 2810 N Church St STE 90780, Wilmington, DE 19802, United States. We provide additional legally required contact methods or local-representative information in the service where applicable.
South Korea. Where Korean law applies, collection/use, entrusted processing, overseas transfers, security, disposal and individual rights follow its applicable requirements in addition to this Policy. The transaction-record periods in section 9 apply only where the relevant Korean law applies, not to every US user's content. Additional legally required notices or consents for optional processing, sensitive information or overseas transfers are not replaced by general Terms acceptance. For complaints, consult the Personal Information Protection Commission. Any applicable rule favoring the data subject where a policy and contract conflict is preserved.
EEA and UK. Where the GDPR or UK GDPR applies, we rely on contractual necessity for requested account, generation, storage and publication functions and legal obligations for required records and rights handling. Security and abuse prevention, personalization, quality improvement, analytics and research or development including shared AI models may rely on legitimate interests where the processing is necessary for those interests and they are not overridden by your interests or fundamental rights. We obtain consent for optional tracking, marketing, sensitive-information processing and other activities where legally required. A content license does not replace a lawful basis for personal information processing; existing consent-based processing remains subject to that consent and its withdrawal conditions. You may withdraw consent, object or seek restriction where applicable, and exercise the rights in section 12. Section 10 governs international transfers. You may complain to your supervisory authority; UK users may contact the Information Commissioner's Office.
California residents may also request applicable disclosures about third-party direct marketing under the state’s Shine the Light law. We provide required free contact methods and any legally required representative or officer details where applicable. Where a separate business data-processing agreement applies, it governs processing performed solely on the business customer’s documented instructions within its scope; it does not automatically cover an ordinary individual account.
14. Adult eligibility and children
Ludyte is offered only to people who are at least 18 years old and have reached the legal age of majority in their country of residence. Ludyte does not offer access to minors through parental permission.
If you believe we have received information from an ineligible minor, contact support@ludyte.com. We will investigate and take appropriate steps, including restricting the account and deleting information where required, subject to applicable legal retention requirements.
15. Changes, language, and contact
We identify the effective date of material Policy changes and give at least 30 days' advance notice, or a longer period required by law. Urgent changes necessary for legal compliance or security may take effect sooner, with the reason and substance communicated as soon as reasonably practicable. Previously collected content remains subject to valid conditions at collection and applicable legal restrictions. Where additional notice or consent is required for a new or changed purpose, we meet that requirement before the processing begins. Continued use after a change may acknowledge the revised Policy, but notice, continued use or acceptance of the Terms does not replace separate consent required by law.
We provide an English original and an official Korean translation. The English text controls to the extent permitted by law, without limiting mandatory local-language requirements or privacy and consumer rights.
NationA, Inc. 2810 N Church St STE 90780 Wilmington, DE 19802 United States
Privacy contact: support@ludyte.com
© 2026 NationA, Inc. · 2810 N Church St, STE 90780, Wilmington, DE 19802, USA