Privacy and data handling
This notice explains the personal data used by Talk2Publish, external providers and international processing, retention and deletion, and your rights. The effective date appears above.
1. Operator and contact
Operated by ZeroGravity Lab (제로그래비티랩). Send requests to access, correct, delete or restrict processing of personal data to support@talk2publish.com. We will explain the minimum identity verification and the scope of processing your request.
Payment, refund and consumer-case evidence
We separately retain minimum provider-verified amounts, currency, tax, available processing times and service periods, together with the offer and versions of terms and refund information captured at checkout. Each version separately records publication status and its effective date. Preserving a review draft does not establish acceptance of finalized terms. Necessary consumer complaint or dispute references and actual closure dates are tracked separately.
Unknown historical amounts or terms are not replaced with current values. Card details and full correspondence are not added to these records. The periods and starting rules below apply, with individual tax and accounting originals classified separately using actual filing deadlines. Automatic financial deletion is disabled. The operator reviews the due list, starting dates and additional retention duties, then explicitly confirms disposal of selected minimum server evidence. This does not dispose of separate tax originals, payment-provider records or backups.
2. What information is used?
| Information | Purpose and storage |
|---|---|
| Email, user identifier and authentication information | Firebase account authentication. Social account passwords are not stored in Talk2Publish profiles. |
| Name, role, audience, tone, private boundaries, language and account lists | Personalization and profile restoration. Stored in the account profile; some settings also remain in the browser. |
| Interview audio, topic, conversation and reviewed brief | Sent to AI services for interviews and draft generation. Conversations and drafts may be saved in your browser. |
| Retry copies of results, request identifiers, hashes and counts | Recovery and duplicate-credit prevention. Result copies can be retrieved for 24 hours, separately from usage records. |
| Encrypted pause copy of conversation, topic, profile and interview progress | Resume the same interview. Cloudflare permits resumption for up to 5 minutes and clears the copy on resume/finish. Expiry blocks access before scheduled cleanup; no audio file is stored. |
| Connected account identifiers, names, authorization tokens and expiry | Access to approved accounts. Tokens are encrypted on the server; disconnecting deletes the stored connection information. |
| Approved publishing content, destinations, status and external post identifiers | Content is sent to your selected platform. Direct-posting and newsletter job records store content hashes, lengths, destinations and status. |
| Payment and subscription identifiers, allowance and refund status | Entitlements and payment verification. Full card numbers are not stored in service profiles. |
| Request counts, models, tokens, voice duration, error categories, processing times and request identifiers | Usage limits, costs and fault diagnosis. Diagnostics contain no conversation text, audio or keys and follow the 90-day rule for completed operational records. |
| Support email, messages, attachments and replies | Service support and privacy requests. Emails sent to support@talk2publish.com are processed in Zoho Mail. |
3. Processing services, locations and contacts
Contract domicile, storage location and network/support processing countries can differ. OpenAI Global and D1 APAC without a jurisdiction restriction do not promise single-country processing. Linked provider location and sub-processor lists describe possible scope, not delivery of every request to every country.
OpenAI’s October 14, 2026 API infrastructure list covers the United States, Canada, Brazil, Mexico, United Kingdom, Ireland, Belgium, Denmark, Finland, France, Germany, Italy, Netherlands, New Zealand, Norway, Poland, Spain, Sweden, Switzerland, Australia, India, Indonesia, Japan, Malaysia, Singapore, South Korea, South Africa and United Arab Emirates; moderation support also lists the Philippines. Network delivery can use Cloudflare near the user. Actual routing varies by request and service.
Cloudflare delivery and Workers can process requests across its published network locations. Verified D1 APAC is a region, with no country-specific restriction configured. Firebase authentication and selected profile-storage locations differ; support and other processing can use the published Google facilities and sub-processors.
Paddle processes buyer information as the payment seller under its own notice; the applicable entity appears at checkout or on the receipt. Our retention periods do not set a uniform provider-wide erasure deadline. The next table explains transfer timing and choices; the sections below explain retention and deletion scope.
| Service and recipient | Purpose and data | Verified location and contact |
|---|---|---|
| Google Firebase — Google LLC and the Google entities under the service agreement | Sign-in and account profiles: email, account identifier, authentication and profile information | Authentication: United States. Profiles: US nam5 storage. Standard Google Cloud terms for Korean customers distinguish Google Asia Pacific Pte. Ltd. and local reseller Google Cloud Korea LLC. A processing service and contracting party have different roles. Contact: Firebase privacy channel below |
| OpenAI OpCo, LLC | Voice interviews and writing: audio, conversation, necessary profile and evidence | Project verified on October 13, 2026: Global, Standard Retention. No US-only processing promise. Contact: privacy@openai.com |
| Cloudflare, Inc. | Site delivery, server processing and service records: requests, account identifiers, usage, connection and recovery records | D1 verified: APAC, read replication disabled, no jurisdiction constraint. Workers and delivery use a global network; no single-country residency guarantee. Contact: legal@cloudflare.com |
| OpenAI OpCo, LLC — former ChatGPT Sites | Restricted rollback copy of pre-migration server data | Historical recovery copies; no new service data is sent here. Operator-managed copies follow the 30-day rule below. Provider-held disposal dates are unverified; immediate erasure or the Cloudflare recovery period is not promised. Contact: privacy@openai.com |
| Paddle.com Inc. / Paddle.com Market Limited and the applicable Paddle seller entity | Payment sale, subscriptions, invoices and refunds: checkout information and minimal transaction/account references | Standard terms distinguish US buyers (US entity) and other transactions for a Korean supplier (UK entity). Paddle processing and sub-processors follow its privacy notice. Contact: Paddle privacy channel |
| Zoho Corporation Pte. Ltd. (standard Korean-customer contract) / Zoho Group | Support and privacy requests: reply address, inquiry, response and necessary attachments | Standard contracting entity: Singapore. Current mail-account data center verified as United States. Contract domicile is not the same as mail storage. Contact: Zoho privacy channel |
| Your selected publishing platform — including LinkedIn | Optional account access and approved publishing: identifiers, tokens, approved content and publishing information | LinkedIn Corporation (US) for members outside Designated Countries, including Korea; LinkedIn Ireland Unlimited Company for designated European countries. Platform-specific transfers and retention. Contact: platform privacy channel |
International processing: timing, method and choices
Processing necessary for contract performance is distinguished from optional publishing. Transfers to all providers are not treated as one blanket optional consent. Account deletion does not immediately erase existing payment evidence or every provider recovery copy.
| Step | Transfer timing and method | Declining and effect |
|---|---|---|
| Sign-in / Firebase | At registration, authentication and profile saving over encrypted browser/server connections | Do not create an account or request account deletion; account-based workspace access is unavailable. |
| Interview and writing / OpenAI API | When you start audio, send a response or request generation, via encrypted voice connections or server APIs | Decline microphone permission or the interview/generation request; that AI function is unavailable. Audio already spoken may have been processed. |
| Site and records / Cloudflare | On site and service requests, via HTTPS and server/database connections | Stop accessing the site or request account-data deletion; server-based functions are unavailable. |
| Checkout / Paddle | At checkout and server transaction requests, and signed payment notifications | Do not purchase or cancel the next renewal. No new paid allowance is issued; existing transaction evidence is retained separately. |
| Support / Zoho Mail | When sending inquiries and responses through mail transfer/storage systems | Do not send an email; that email inquiry cannot proceed. Do not send passwords or sensitive documents. |
| Optional publishing / connected platform | At account authorization and approved publishing, via OAuth and encrypted APIs | Decline/disconnect publishing. Draft creation and copying remain available; remove external posts separately on the platform. |
4. Retention and deletion: service rules
Record-specific rules were selected on October 13, 2026. Conversations and drafts are not treated as long-term transaction evidence. Unnecessary data is disposed of when its purpose and applicable retention/case obligations end. Electronic data is removed using methods preventing recovery or reproduction; paper records are shredded or incinerated.
Account deletion removes profiles, authentication accounts, connection tokens, conversations, generations and ordinary usage records. Minimum legally retained evidence and deletion records are kept separately. We explain the scope and grounds where a dispute or legal request requires retention.
Server retries expire after 24 hours, but database cleanup and provider recovery-history expiry are separate. Restored data must have the latest deletion records reapplied before use.
| Data | Retention rule | Deletion and exceptions |
|---|---|---|
| Browser conversations and drafts | Until you delete them | Reset, account deletion or browser site-data removal; other devices and downloads require separate deletion |
| Server generation recovery | Retrievable for up to 24 hours | Then hourly/request-driven cleanup; access expiry and physical database cleanup can differ |
| Encrypted paused-interview continuation copy | Resume window up to 5 minutes | Cleared on resume/finish. No resume after expiry; expired copies are cleaned hourly and during requests. Database recovery history is separate |
| Completed AI and successful publishing records | 90 days after completion | Pending, uncertain, held and financial records are excluded from ordinary cleanup |
| Cloudflare D1 recovery history | Up to 30 days on Paid | App deletion and provider recovery-history expiry differ; manual backups have separate rules below |
| Closed ordinary support email | One year after inquiry closure | Manual deadline review; consumer complaints, disputes and legal evidence are classified separately |
| Contract, payment, refund, dispute and tax evidence | Transactions/refunds: 5 years; closed consumer cases: 3 years; record-specific rules below | Minimum evidence retained separately; longer tax/accounting duties and ongoing cases checked before manual disposal |
Transaction, dispute and accounting periods
The service adopts the record-specific periods in Article 6 of the Korean e-commerce enforcement decree. Where another legal duty actually applies, the minimum relevant evidence and deadline are managed separately. Actual filing deadlines and case-closure dates are not replaced by today or an arbitrary payment date.
There is no automatic financial purge. The operator checks classification, due dates, ongoing subscriptions/work/cases and holds, then manually disposes of expired unnecessary evidence. Selecting a period does not authorize deletion of current transactions.
| Record and purpose | Period and starting point | Separation and disposal |
|---|---|---|
| Minimum contract, withdrawal, payment, supply and refund evidence | 5 years. Service evidence uses the later of service-period end and verified payment completion; refunds use verified final processing time | Minimum references, amounts, currencies, periods and policy versions; no extra conversation or card-number retention |
| Consumer complaint/dispute records | 3 years after the case closes | Necessary inquiry/decision evidence separated from ordinary support; unresolved cases retain only what is needed |
| Advertising/display records | 6 months | Track actual display/end dates; do not retain entire customer conversations as advertising evidence |
| Tax books and supporting originals | 5 years from the relevant statutory filing deadline; 7 years for qualifying offshore transactions, with statutory exceptions | Paddle payout, fee, deposit and filing originals managed separately using actual tax periods/deadlines |
| Commercial books/important business records and vouchers | Books/important records: 10 years; vouchers/similar records: 5 years. Books measured from closure | Applies to qualifying documents, not blanket ten-year retention of customer personal data |
| Sandbox records | No real charge or taxable transaction evidence | No automatic financial purge; review the actual test completion and necessary reproduction scope separately |
Migration copies and manual-backup rules
Operator-managed originals/encrypted copies and provider-held recovery copies differ. Registered external tasks show due dates and seven-day reminders on the operator dashboard. External email or copies are removed in their own systems and completion is recorded afterward; the dashboard does not automatically erase them. Former Sites provider retention is not assigned Cloudflare D1’s thirty-day period. A planned/due date is not proof of provider deletion.
Record any justified extension, minimum scope, grounds and next review date separately. Permanent cleanup requires checking the exact original and recovery scope at execution.
| Copy | Period and review rule | Current state |
|---|---|---|
| Encrypted migration copies containing personal data and operator-managed former Sites originals | 30-day default after migration completion. Review-by date for the October 10, 2026 cutover: November 9, 2026 | Restricted access/writes; not marked deleted. Manually reconcile migration verification and separate necessary credentials before final cleanup |
| New personal-data recovery backups | 30-day default from creation | Separate only minimum evidence subject to a legal/dispute hold; source-code backups without customer content are outside this rule |
| Minimum deletion journal | Review disposal 30 days after the last relevant recovery copy is confirmed expired or erased | No conversations, emails or tokens; do not remove the journal while a relevant recovery copy remains |
Removing browser copies
After account deletion completes, the current account’s conversations and drafts are also cleared from this browser. If storage access is blocked or automatic sign-out cannot finish, you are directed to additional cleanup guidance. Check the remaining browser step rather than requesting server account deletion again.
First close other Talk2Publish tabs. In your browser settings, open site data or storage, find talk2publish.com and remove its data. This can also erase drafts for other Talk2Publish accounts and sign-in or language settings in this browser. Download anything you want to keep before clearing site data.
Remove copies on other browsers, devices and earlier site addresses, downloaded files and external platform posts separately. Clearing browser data does not itself delete a server account, cancel a subscription or issue a refund. Contact support if account deletion or remaining data is unclear.
Deletion records and recovery safeguards
A separate Cloudflare D1 journal keeps account identifiers, deletion phase and request/completion/update timestamps to prevent erased data returning after an older restore. Reviewed disposal of individual financial evidence or consumer cases records a one-way reference hash and requested/outcome state. This independent journal excludes emails, drafts, social tokens, payment instruments and transaction content. Uncertain outcomes require review before recovery.
The latest independent journal is reapplied before recovery; account access and social callbacks check it too. Review journal disposal thirty days after the last relevant recovery copy is confirmed expired or erased; never remove it first while copies remain or are unverified.
Provider deletion and recovery copies
Firebase states that removing authentication information from live and backup systems can take up to 180 days after the account-deletion request. Authentication security IP logs are kept for a few weeks. These periods do not establish a common deletion period for profiles or every service record.
The current site runs in the operator’s own Cloudflare Workers and D1 account; Cloudflare, Inc. is the hosting processor. Paid D1 Time Travel supports recovery to a point within the previous 30 days. This differs from the service’s 24-hour result-retrieval period. Database deletion does not immediately erase every provider recovery copy. Prior account-deletion and erasure requests are reapplied before restored data is used.
Operator-managed former Sites originals and encrypted personal-data copies use the thirty-day post-migration cleanup rule above. They are not marked deleted, and provider-held recovery-copy conditions remain separate.
Support emails and account deletion
The selected retention period for inquiry emails, replies and necessary attachments is one year after the inquiry closes. The operator tracks closure dates and due dates and removes expired records manually. Emails are not automatically deleted based on inquiry closure dates. Minimum evidence needed for ongoing disputes or legal retention is managed separately.
On October 5, 2026, we verified a 30-day Spam/Trash cleanup setting for the support mailbox. It periodically removes messages in these folders based on receipt age; it does not guarantee 30 days in Trash after deletion. Zoho states that recovery copies remain for an additional 30 days after Trash removal. One year after closure is the operator’s cleanup rule, not immediate erasure of every provider copy.
Deleting your service account does not automatically erase inquiry emails in Zoho Mail. Contact support to request their deletion. We explain any limits where a request, dispute or legal retention is ongoing.
5. AI provider retention and sharing
Requests disable separate text-response and voice-session storage. We do not use stored voice recordings for download or continuation. Storage and training sharing are separate settings. OpenAI states that API data is not used for training by default unless sharing is enabled.
On October 5, 2026, we verified disabled input/output sharing and the service’s organization/project connection. Public AI availability is shown separately at the top of this page. The project was additionally verified as Global with Standard Retention on October 13, 2026. The standard DPA recipient is OpenAI OpCo, LLC; this does not promise single-country processing or Zero Data Retention.
Abuse-monitoring logs may remain up to 30 days and some temporary caches up to 24 hours, with exceptions. API call logging was verified as enabled per call. Disabling storage or sharing does not immediately erase past data or every provider record or establish approved Zero Data Retention. Provider retention is separate from the service’s 24-hour recovery copy.
6. Your choices
Voice interviews require browser microphone permission. They cannot proceed if permission is withheld. Social connections are optional; draft creation does not require them.
Turns marked private are excluded from subsequent text-generation inputs. Audio already spoken may have been processed by the interview AI, and your profile’s private-boundary instructions are themselves sent to AI. The private flag does not prevent all AI transmission in advance. Do not input sensitive or confidential information belonging to others.
7. Privacy requests and objections
Send your registration email, reply email, request type and scope to support@talk2publish.com. Do not send passwords, verification codes, API keys or full identity-document copies. We will explain the minimum verification needed to confirm you or an authorized representative.
After reviewing identity verification and scope, we respond within the applicable statutory time limits. If access is deferred or part of a request must be restricted, we explain the affected records, reasons and how to object. You can request reconsideration in the same inquiry or use external privacy advice and redress channels.
‘Download current conversation and drafts’ in account settings exports content from the current browser. It is not a complete personal-data export including profile, usage and payment evidence. Request other records separately if needed.
Account deletion, removal of support emails and removal of external platform posts have different scopes. Minimum records required by law and provider recovery copies may not be erased at the same time. We distinguish completed actions, separately retained records and grounds, and any other responsible provider.
8. Privacy contact
Joonho Jang (장준호), the representative of ZeroGravity Lab, serves as the privacy officer and handles privacy inquiries.
Send access, correction, deletion or processing-restriction requests, privacy questions and complaints to support@talk2publish.com. We will explain the necessary identity verification and request scope.
9. Effective date and updates
This notice applies from the effective date above. Material changes to purposes, providers, data, international processing or retention are reflected here and in service notices with their effective date and impact. Any legally required notice or consent procedure applies. Earlier review-draft acknowledgements are not retrospectively treated as acceptance of this notice. Contact support@talk2publish.com with questions.