Risecraft, LLC (a Delaware company)
Effective date: September 3, 2026
Risecraft, LLC ("DocuRise", "we") provides document sharing and protection, engagement analytics, lead capture, contact management, messaging, and digital product sales (the "Service"). This policy explains what personal information we handle, why, who receives it, and how long we keep it.
One thing to read before anything else: Section 13 explains when a creator is the controller of your data and we are only their processor. Which side applies decides who you send a request to.
If you use the Korea-only payment path for a creator's product, additional notices may appear at checkout, on the payment page or on a receipt, and those supplement this policy for that transaction. The Korean-language version of this policy is here.
We collect the minimum information needed to run the Service. What we hold depends on whether you are a creator, a viewer or a buyer, and on which features the creator enabled.
Users who register with DocuRise to create and sell documents
Creators on a paid plan or receiving sales payouts
We do not store full card numbers. Account numbers and verification data are stored encrypted. We never collect a full Korean resident registration number.
Users who interact with a creator's documents, folders, lead forms or checkout. We process this information on that creator's behalf.
Users who consented to data collection or marketing communications
Consent evidence exists to demonstrate that valid consent was obtained. It is stored immutably rather than updated.
Everyone who accesses the Service
Viewers of a document where the creator enabled watermarking
Processed only where a creator connected an Instagram account.
Users who contact us or leave feedback
We process personal information for the purposes below. If we ever need it for a new and incompatible purpose, we will ask for consent first.
Marketing messages are sent only to people who separately consented to receive them.
We destroy personal information without delay once its purpose is fulfilled, except for the periods below. Where a law requires retention, that data is stored separately from active records and destroyed when the period ends.
| Data | Retention period | Statutory basis |
|---|---|---|
| Account and member information | Kept while the account is active. Destroyed without delay when closure is requested; copies in backups are removed within the backup rotation, at most 30 days later | — |
| Viewer, lead and buyer information processed on behalf of a creator | Until the creator deletes it, or destroyed together with the creator account on closure. A data subject may also request destruction directly under Section 8 | — |
| Marketing communications consent | Two years from consent or last reconfirmation. After two years a reconfirmation notice is sent, and contacts that are not reconfirmed are excluded from sending | Network Act Article 50(8) |
| Consent records — timestamp, verbatim consent text, IP address, browser information | Kept while processing under that consent continues, and destroyed with the creator account on closure. Where a law requires it for dispute handling, kept separately for that period | Act on Consumer Protection in Electronic Commerce (Korea) |
| Email verification data and verification tokens | Destroyed within 24 hours of expiry | — |
| Section-level document engagement records | 90 days from collection | — |
| Instagram comment and DM event records, where a creator connected the integration | 90 days from collection | — |
| Instagram viewer identity tokens | Seven days from issuance; expired tokens are purged automatically | — |
| Cached content from a connected Notion page | 30 days from last refresh | — |
| Email and Kakao send records — recipient, timestamp, open / click / bounce status | Destroyed with the creator account on closure. Unsubscribe and bounce records exist to prevent re-sending, so they are kept even if the contact is deleted | Act on Consumer Protection in Electronic Commerce (Korea) |
| Records of contracts, withdrawal of subscription, payment and supply of goods | 5 years | Act on Consumer Protection in Electronic Commerce (Korea) |
| Records of consumer complaints and dispute resolution | 3 years | Act on Consumer Protection in Electronic Commerce (Korea) |
| Records of labelling and advertising | 6 months | Act on Consumer Protection in Electronic Commerce (Korea) |
| Tax and accounting records | 5 years | Framework Act on National Taxes and related laws |
| Access and operational logs — IP address, request path, error records | Retained and then automatically expired under the retention policies of our log processors, Axiom and Sentry | — |
We do not sell personal information. We share it only in the cases listed below, and only to the extent each purpose requires.
When you submit information through a creator's document, folder, lead form or checkout, that information goes to that creator so they can fulfil the purpose you gave it for. The creator is the controller of that data; we process it on their behalf. See Section 13.
Where a creator has connected their own advertising account, we transmit the events below so that creator can measure and optimise their advertising. Email addresses and phone numbers are hashed before transmission — the plain values are never sent. On pages where no advertising account is connected, nothing is transmitted.
| Recipient | Purpose | Items provided | Retention |
|---|---|---|---|
| Meta Platforms, Inc. (Meta Pixel / Conversions API) United States | Advertising measurement and optimisation on behalf of the creatorOnly where a creator connected it | SHA-256 hashed email address and phone number, hashed viewer identifier, IP address, browser user agent, Meta advertising cookie identifiers (_fbp / _fbc), page URL, and for a completed purchase the order amount and currency | Per Meta's data retention policies |
See Section 12 for how to refuse behavioural data collection.
Where a creator connected an outside tool such as Slack or Google Sheets, lead and order information is delivered to it. The destination is an account the creator chose and connected themselves — not a processor we selected. We carry out the delivery on their instruction and record that it happened and when, but storage, use and deletion after delivery are that creator's responsibility.
| Destination | Purpose | Items delivered | After delivery |
|---|---|---|---|
| Slack Technologies, LLC United States | Delivering lead and order notifications to the creator's own Slack workspace | Lead email address, name, phone number, company, form responses, order information | Per that Slack workspace's retention settings, which the creator controls |
| Google LLC (Google Sheets) United States | Automatically appending lead information to the creator's chosen spreadsheet | Lead email address, name, phone number, company, form responses, submission timestamp | Until the creator deletes it from the spreadsheet, which the creator controls |
We disclose information where a law requires it, or where a law enforcement or regulatory body requests it through a lawful process. We verify that such requests have a legal basis, and we try to notify the affected person where we are not prohibited from doing so.
We entrust the processing below to the parties listed. Our agreements with them restrict use to our instructions, require security measures, restrict onward sub-processing, and provide for audit and liability, as required by Article 26 of the Korean Personal Information Protection Act. We publish changes to this list in this policy.
| Processor | Entrusted work | Items transferred | Retention |
|---|---|---|---|
| Traffic Machine Co., Ltd. Republic of Korea | Brokering Korean transactions, refund/cancellation support, payment-related customer service, transaction record keeping, intake of Korean privacy enquiries | Order and payment records, buyer name / email / phone, refund and enquiry records | Until the transaction purpose is fulfilled, including statutory retention periods |
| Payple Co., Ltd. Republic of Korea | Korean payment processing, payout disbursement, bank account holder verification, payment record keeping | Payment authorisation data, transaction identifiers, payment method type / (for creators receiving payouts) bank account number, account holder name, date of birth or business registration number | Until the transaction purpose is fulfilled and for statutory retention periods |
| Stripe, Inc. United States | Global subscription payments, creator payouts via Stripe Connect, dispute and refund handling | Email address, payment identifiers, billing information, payment / refund / dispute history / (for creators receiving payouts) Stripe account identifier and country | Per Stripe's retention policy, including statutory periods |
| Supabase Inc. United States | Database and authentication infrastructure | Personal data required to operate the Service (items in Section 1) | Until the processing purpose is fulfilled |
| Vercel Inc. United States | Web hosting and edge network | IP address, request headers, access logs | Per Vercel's retention policy |
| Amazon Web Services, Inc. United States | Email delivery (SES), uploaded file storage (S3), document / PDF conversion (Lambda), infrastructure monitoring (CloudWatch) | Recipient email address, email subject and body, send / delivery / bounce records, uploaded document files, operational logs | Until the processing purpose is fulfilled; send logs per Section 3 |
| Resend, Inc. United States | Transactional and notification email delivery | Recipient email address, email subject and body | Per Resend's retention policy |
| Upstash, Inc. United States | Cache and queue infrastructure, rate limiting | Rate-limit identifiers such as IP address, encrypted job payloads | Short-lived; automatically expired rather than stored long term |
| BunnyWay d.o.o. (Bunny.net) Slovenia and other locations | Video storage, encoding and playback delivery | IP address, playback request records, device and browser information, uploaded video files | Until the creator deletes the video |
| Sendon (주식회사 알리는사람들) Republic of Korea | KakaoTalk alimtalk / friendtalk delivery and delivery-result handling | Recipient phone number, recipient name, message body and substituted variables, send / delivery / failure records | Until delivery is complete, plus the send-log retention period in Section 3 |
| Functional Software, Inc. (Sentry) United States | Error and exception monitoring | IP address, request context, error stack traces, account identifier | Per Sentry's retention policy |
| Axiom, Inc. United States | Server log collection and operational monitoring | IP address, request identifier, request path and outcome, account identifier, operational event records | Per Axiom's retention policy |
| PostHog, Inc. United States | Product usage analytics and feature improvement | Usage events, navigation records, session identifier, account identifier, device and browser information | Per PostHog's retention policy |
| Google LLC (Google Analytics) United States | Website usage analytics | Page view records, client identifier, IP address, referrer, device and browser information | Per Google's retention policy |
| Chatwoot Inc. United States and other locations | Customer support chat | Email address, name, support conversation content, account identifier | Three years after resolution, per the Korean E-Commerce Act record-keeping requirement |
| Meta Platforms, Inc. (Instagram Graph API) United States | Instagram comment and DM automationOnly where a creator connected it | Instagram account ID, username, comment content, DM content, hashed author identifier | Per Meta's data retention policies |
| Notion Labs, Inc. United States | Fetching and caching the content of a Notion page the creator connectedOnly where a creator connected it | Notion page content and page identifiers. No viewer personal data is sent to Notion. | Cached until the document is deleted |
DocuRise is operated by Risecraft, LLC in the United States, so personal information is transferred to and processed outside Korea to the extent the Service requires. The recipients and items are listed below.
| Recipient | Country | Items transferred | Timing and method | Purpose | Retention |
|---|---|---|---|---|---|
| Risecraft, LLC (DocuRise) | United States (Delaware) | All items listed in Section 1 (Information We Collect) | Transmitted over the network at the time of use | Providing, operating and improving the Service, account management, abuse prevention | Per the retention periods in Section 3 |
| Stripe, Inc. | United States | Email address, payment identifiers, billing information, payment / refund / dispute history / (for creators receiving payouts) Stripe account identifier and country | Transmitted when a payment or payout is processed | Global subscription payments, creator payouts via Stripe Connect, dispute and refund handling | Per Stripe's retention policy, including statutory periods |
| Supabase Inc. | United States | Personal data required to operate the Service (items in Section 1) | Transmitted and stored continuously during use of the Service | Database and authentication infrastructure | Until the processing purpose is fulfilled |
| Vercel Inc. | United States | IP address, request headers, access logs | Transmitted on each request | Web hosting and edge network | Per Vercel's retention policy |
| Amazon Web Services, Inc. | United States | Recipient email address, email subject and body, send / delivery / bounce records, uploaded document files, operational logs | Transmitted when an email is sent, a file is uploaded, or a document is converted | Email delivery (SES), uploaded file storage (S3), document / PDF conversion (Lambda), infrastructure monitoring (CloudWatch) | Until the processing purpose is fulfilled; send logs per Section 3 |
| Resend, Inc. | United States | Recipient email address, email subject and body | Transmitted when an email is sent | Transactional and notification email delivery | Per Resend's retention policy |
| Upstash, Inc. | United States | Rate-limit identifiers such as IP address, encrypted job payloads | Transmitted while handling the request | Cache and queue infrastructure, rate limiting | Short-lived; automatically expired rather than stored long term |
| BunnyWay d.o.o. (Bunny.net) | Slovenia and other locations | IP address, playback request records, device and browser information, uploaded video files | Transmitted on video upload and playback | Video storage, encoding and playback delivery | Until the creator deletes the video |
| Functional Software, Inc. (Sentry) | United States | IP address, request context, error stack traces, account identifier | Transmitted when an error occurs | Error and exception monitoring | Per Sentry's retention policy |
| Axiom, Inc. | United States | IP address, request identifier, request path and outcome, account identifier, operational event records | Transmitted continuously during use | Server log collection and operational monitoring | Per Axiom's retention policy |
| PostHog, Inc. | United States | Usage events, navigation records, session identifier, account identifier, device and browser information | Transmitted during use of the Service | Product usage analytics and feature improvement | Per PostHog's retention policy |
| Google LLC (Google Analytics) | United States | Page view records, client identifier, IP address, referrer, device and browser information | Transmitted on page view | Website usage analytics | Per Google's retention policy |
| Meta Platforms, Inc. (Meta Pixel / Conversions API) | United States | SHA-256 hashed email address and phone number, hashed viewer identifier, IP address, browser user agent, Meta advertising cookie identifiers (_fbp / _fbc), page URL, and for a completed purchase the order amount and currency | Transmitted when the corresponding event occurs — page view, lead submission, or completed purchase | Advertising measurement and optimisation on behalf of the creatorOnly where a creator connected it | Per Meta's data retention policies |
| Chatwoot Inc. | United States and other locations | Email address, name, support conversation content, account identifier | Transmitted when the support chat is used | Customer support chat | Three years after resolution, per the Korean E-Commerce Act record-keeping requirement |
| Meta Platforms, Inc. (Instagram Graph API) | United States | Instagram account ID, username, comment content, DM content, hashed author identifier | Transmitted when an automation rule runs | Instagram comment and DM automationOnly where a creator connected it | Per Meta's data retention policies |
| Slack Technologies, LLC | United States | Lead email address, name, phone number, company, form responses, order information | Transmitted when a lead is submitted or an order is placed | Delivering lead and order notifications to the creator's own Slack workspaceOnly where a creator connected it | Per that Slack workspace's retention settings, which the creator controls |
| Google LLC (Google Sheets) | United States | Lead email address, name, phone number, company, form responses, submission timestamp | Transmitted when a lead is submitted | Automatically appending lead information to the creator's chosen spreadsheetOnly where a creator connected it | Until the creator deletes it from the spreadsheet, which the creator controls |
| Notion Labs, Inc. | United States | Notion page content and page identifiers. No viewer personal data is sent to Notion. | Fetched on document creation and content refresh | Fetching and caching the content of a Notion page the creator connectedOnly where a creator connected it | Cached until the document is deleted |
Traffic Machine Co., Ltd., Payple and Sendon process personal information inside Korea, so those are not overseas transfers.
You may refuse an overseas transfer. What happens depends on the transfer:
Contact us at the address in Section 18 with any question about, or objection to, an overseas transfer.
You may at any time ask us to:
Email support@docurise.io, or use the Korean contact point in Section 17. We act within 10 days of receiving a request and tell you the outcome. Where a law lets us decline part of a request, we explain why.
For information collected through a creator's documents, lead forms or CRM, that creator is the controller — see Section 13. Direct those requests to the creator.
If you cannot identify the creator, or they do not respond within a reasonable time, contact us. As their processor we pass the request on and assist with it, and we act immediately ourselves on anything we can handle directly, such as stopping marketing messages.
Every marketing email carries an unsubscribe link. You can also email us and we will remove your address from sending. For KakaoTalk messages, block the channel or contact us.
We process personal information in accordance with the Personal Information Protection Act. Personal information is destroyed securely once its purpose is achieved unless another law requires retention, in which case it is stored separately for only the required period. The Korean-language version of this policy, our data protection officer, and the domestic contact point are in Sections 15 and 17. Korean data subjects may also bring a dispute to the bodies listed in Section 16.
We do not sell personal information and we receive no consideration for disclosing it.
We do, however, share information for cross-context behavioural advertising in one narrow case: where a creator has connected their own Meta advertising account to their pages, we transmit the hashed identifiers and event data described in Section 5.2.
If you are a California resident and want us to stop this, email support@docurise.io with the subject "Do Not Sell or Share My Personal Information", or refuse the trackers using the methods in Section 12. We will not discriminate against you for exercising any of these rights.
Several other states — including Virginia, Colorado, Connecticut and Texas — give residents comparable rights to know, correct, delete, obtain a copy of, and opt out of targeted advertising using their personal information. Where one of those laws applies to us, residents of that state may exercise those rights through the same email address, and we will not discriminate against them for doing so.
Each of these statutes, including the CCPA as amended by the CPRA, applies only above thresholds tied to revenue and to the number of residents whose data a business handles. Where a statute applies to us we additionally honour an opt-out preference signal such as Global Privacy Control, publish a "Your Privacy Choices" link, and give the notice-at-collection and category disclosures it requires. We reassess which of these apply as the business grows. The email routes above are open to residents of any state either way.
California residents may also request to know, correct, delete, or receive a portable copy of their personal information, and may designate an authorised agent to act for them.
We take this seriously, but no method of transmission or storage over the internet is completely secure.
If we learn that personal information has been lost, stolen, disclosed, altered or destroyed, we tell the affected people without delay — what was involved, when and how it happened, what we have done, what they can do to limit harm, and where to reach us — and we report it to the Korean Personal Information Protection Commission or the Korea Internet & Security Agency where the statutory thresholds apply. This is the duty Article 34 of the Personal Information Protection Act places on us.
Where the breach involves data we process on a creator's behalf, we notify that creator without delay and give them the information and technical help they need to meet their own notification and reporting duties. In that case the creator, as controller, is the one who notifies the affected people — see Section 13.
We use cookies and local storage to keep you signed in, remember settings and manage document viewing sessions. The cookies the Service needs to function are:
| Cookie or technology | Purpose |
|---|---|
NEXT_LOCALE | Stores the selected language |
viewer_session_{문서 ID} | Maintains the document viewing session and prevents duplicate view counting |
password_verified_{문서 ID} | Remembers that a password-protected document was unlocked |
_dr_accounts, _dr_adding_account | Manages sign-in across multiple accounts and the add-account flow |
_dr_auth_gate_ok | Records that access to a pre-release page was granted |
oauth_next | Remembers where to return after social sign-in |
_dxt | Identifies viewers arriving from Instagram, where the creator connected the integration |
You can block cookies in your browser. Doing so limits features such as staying signed in and opening password-protected documents.
We collect data about online activity for product improvement and advertising measurement. The collectors, purposes and refusal methods are:
| Cookie or technology | Purpose | How to refuse |
|---|---|---|
| Meta 픽셀 (_fbp, _fbc) | Advertising measurement and optimisation for a creator who connected their own Meta Pixel to their pages | Nothing is collected on pages where the creator has not connected a Pixel. Blocking cookies in your browser stops the browser-side identifiers (_fbp / _fbc), but it does NOT stop the server-side Conversions API events, which are sent from our servers rather than your browser. To stop those, email support@docurise.io and we will block that transmission. To limit how Meta uses what it already holds, refuse interest-based ads in your Meta ad settings (facebook.com/adpreferences). |
| Google Analytics (_ga, _ga_*) | Website usage analytics and service improvement | Install Google's Analytics Opt-out Browser Add-on at tools.google.com/dlpage/gaoptout. |
| PostHog (ph_*) | Product usage analysis and feature improvement | Refuse through browser cookie blocking or a Do Not Track setting. |
We do not collect or use special-category data — beliefs, political opinions, health, sexual life — for advertising, and we do not collect behavioural data from anyone we know to be under 14.
Responsibility for personal information splits two ways in DocuRise, and which side applies determines who you direct a request to.
For personal information a creator collects through their own documents, folders, lead forms, contact management and messaging, that creator is the controller and we are their processor. In that scope the creator is responsible for:
As processor we supply the infrastructure and compliance tooling, process within the creator's instructions, and record consent and unsubscribe status. The terms of that processing are set out in our data processing agreement, which is incorporated into the Terms of Service.
We act as controller in our own right, and this policy applies directly, for: creating, authenticating and managing DocuRise accounts and subscription billing; operating the Service, responding to incidents, security and abuse prevention; producing usage statistics and improving features; and meeting legal obligations and handling disputes.
A DocuRise account is for creators aged 18 and over. We do not knowingly collect personal information from children under 14, or under 13 for users in the United States.
We do not verify the age of people who open a creator's document or answer their lead form. Responsibility for that data rests with the creator under Section 13, and a creator running a flow aimed at, or likely to reach, children must meet the applicable requirements themselves, including obtaining a legal representative's consent.
If we learn we have collected a child's personal information without the required consent, we destroy it without delay. Tell us at support@docurise.io if you believe this has happened.
Korean data subjects may bring a complaint or dispute to:
We are a United States company, but Korean users may raise privacy matters through our Korean affiliate, which forwards them to the data protection officer.
Traffic Machine Co., Ltd. | Representative: Gayoung Park
Business registration number: 684-88-02857 | Mail-order registration: 2023-Seoul Songpa-5624
125 Wangsimni-ro, Room 302, Seongdong-gu, Seoul, Republic of Korea
Phone: +82-70-8080-4559 | Email: support@docurise.io
We may update this policy as laws or the Service change. We post the effective date and the substance of any change on this page. For changes that materially affect your rights, we post them 30 days before they take effect and notify account holders by email or in-app notice.
Questions: DocuRise / Risecraft, LLC — support@docurise.io, or the Korean contact point in Section 17.
The Korean-language version of this policy is available here. The two versions reflect the law and the user protections that apply in each jurisdiction, so some provisions differ. For users in South Korea, Korean mandatory law prevails and whichever version is more favourable to the user applies.