Amendment notice
Posted: 2026-11-18 · Effective: 2026-11-25 at midnight in Korea
Reason: Clarify always-available Lifetime Pro, service-duration and non-transferability limits, no refund on service closure, the seven-day/no-official-pack refund conditions for monthly and lifetime purchases, and lifetime payment records.
If you do not object before the effective date, you are deemed to accept the amendment. If you do not agree, you may delete your account; any remaining paid period is handled under the Refund Policy. Continuing to use the service after the effective date also counts as acceptance.
Lifetime purchase conditions and the new monthly refund conditions apply to new purchases through separate checkout consent, recorded before payment. Purchases may be made under those accepted conditions before the general amendment takes effect.
Devalley Privacy Policy
Effective: November 25, 2026
The operator of Devalley (the "Operator") publishes this policy under Article 30 of the Personal Information Protection Act of the Republic of Korea to protect your personal data and to handle any concern about it quickly.
Devalley is built to collect as little as possible. The app works without an account, village data stays on your computer (a signed-in member's coins, XP and purchases are kept in the account's wallet), and the Operator never receives payment-method details.
Article 1 (What we collect and how)
The Operator processes the following personal data and nothing else.
1. Account (when you sign up)
- GitHub or Google sign-in: email address, name and the provider's user id. The tokens the provider issues (for Google sign-in, the ID token too) are used only to complete sign-in and are not stored, and no profile picture is kept. At sign-up the GitHub username is used only to pick your handle. No other data from your Google or GitHub account is requested. Devalley's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- What you choose: handle, display name, language, whether your profile is public, the chief's look, and whether you agreed to news email and when.
- What we generate: a random account id, sign-up date, last sign-in time, when you confirmed you are 14 or older, the versions of the terms and this policy you agreed to and when, role, and any restriction records (kind, end date, reason).
2. Sign-in sessions (while you are signed in)
- Session token, IP address, browser or app type (User-Agent), creation and expiry times.
- From the app, additionally: a random install id, the device name (by default the first 40 characters of the computer's name; you can change it on My page), operating system, app version.
- Sign-in records: the account, when it signed in, the IP address, and whether on the site or in the app. Used to look into account takeover and kept as the access records the law asks for.
- The device code used to sign the app in (deleted once approved or expired).
3. Pro subscription and benefits, and packs bought with money (when you use Pro or buy a pack with money)
- From Paddle: Paddle customer id, subscription id, status, plan, currency, billing period, next billing date, and the raw subscription events Paddle sends (amount, country and other fields Paddle includes).
- Lifetime Pro purchases: transaction, customer and account identifiers, payment time and refund-request/revocation times support entitlements, receipts and refund review. Existing official-pack delivery records supply the account, time, pack, version and delivery path. Active records remain while the account and entitlement exist; customer/account links are cleared five years after refund, or immediately when the account is deleted. Transaction identity and revocation facts remain without personal links to prevent replay from restoring Pro.
- Checkout error diagnostics: the signed-in account ID, error code and detail, and price ID are kept in the audit log for 3 years to troubleshoot failures. We do not collect customer/card details or the full checkout event.
- Packs bought with money: Paddle transaction id, the pack, amount and currency, payment, refund and chargeback state, and when you agreed at checkout that downloading or opening the pack ends the right of withdrawal.
- What we generate: the source of each Pro grant (subscription, trial, promotion, administrator) and its period; promo code redemptions.
- Official pack downloads: account, pack and version, where it went (the install id of the app that downloaded it, or a mark saying it was downloaded in a browser or fetched by the site's tailor shop to draw the pack's residents), file size, time. Used for refund reviews and the daily download cap.
- Pro feature use: account, feature (an official pack key issued, resident packs turned on, your own residents saved beyond the member limit, packs made and versions uploaded, the app without ads (a Pro app's plan check), sync), subject (pack and version and the like), install id, date; only the first use a day of each feature and subject. Used for refund reviews.
- Whether an email address has had the free trial: a keyed hash of the address (the address itself is not stored; the hash survives account deletion).
- Card numbers, bank details, billing address and tax ids are collected and held by Paddle directly; the Operator never receives them.
4. Community and studio (when you upload)
URL drafts (when requested): the public URL you enter and public page information are sent to Anthropic’s Claude API to draft a service introduction. Account identifiers, email, existing editor text and local agent data are not sent. We do not store fetched pages or generated drafts in the database; only the title and body you review and publish become an ordinary post. Per-account request counters follow the automatic collection rules. Candidate representative images are cached for up to one hour for preview; images automatically included in the draft follow the ordinary attachment retention and deletion rules and can be removed before publishing. You can write posts without using this feature.
Posts (with the time they were edited), comments, likes, attached images, packs (title, description, files, cover, previews, licence, coin price), looks.
For each pack version, when you confirmed the warranty that you made the material or have permission, and the wording you confirmed.
The record of packs you hold: pack, version, file hash, when you received or bought it and its licence then. Used to keep that version's file so you can download it again.
Reports: target, reason, details, the reporting member, the outcome and staff's note. For copyright requests, the requester's contact details, proof of the right, where the infringement is and how it went (stop, resumption, notice of a lawsuit).
Support board posts: title, body, category, the app version, daemon API and operating system when sent from the app's "Report a problem…", and, in the "Refund" category, the payment details attached automatically (plan, subscription or transaction id, dates).
In-site notifications (comments on your posts, pack review results, notices of action taken on your content after a report or by staff (the action, reason and staff's note), notices that a pack you turned on or hold was taken down, notices that an Official Pack is being retired, a trial ending in 3 days, a trial or PRO ended, changes to the terms and policies, payment problems, restrictions on writing, support answers) and when you read them. The trial, PRO, terms and payment notices also reach the signed-in app, which shows them.
PRO end records: when PRO ended and why (subscription, trial, grant, promotion, refund, restriction), and what it locked then: the resident packs turned on, the number of your own residents, and the official packs and versions downloaded.
Requests you send from the site to the app (install a pack, apply a chief look): their type and time.
Village settings: the packs your residents come from, and the residents you designed (name, outfit). The site's tailor shop and the app share them.
Wallet (signed-in members): XP total, coin balance, coin history (coins earned each day, purchases and their purchase ids, sales of your packs, staff adjustments and their reasons, what the first sign-in moved in), the clothes, decorations and packs you own, and the daily XP and chief-coin totals the app sent (per install id).
5. What the app sends to the server
- The update check (signed in or not, at start and once a day): the app version and operating system type; no account or install id.
- Every request of a signed-in app (signing in, the daily plan check, village sync, reading the requests sent from the site, official packs and their keys, the wallet, Pro sync): the session token, the app's version and operating system ("Devalley/<app version> (<operating system>)") and the number of the protocol version the app speaks.
- Device registration (signed-in apps): install id, device name, operating system, app version.
- Village sync (signed-in apps, every 5 minutes while running and when the tailor shop opens): session token. The app fetches the village settings and the requests sent from the site, and uploads village settings changed in the app.
- Wallet (signed-in apps): daily XP and chief-coin totals (earned while signed in) and the item when you buy clothes or a decoration; once, at the first sign-in, that computer's coin balance, XP total and the clothes and decorations bought on it.
- The ad list (free plan, signed in or not, once a day): the app downloads the list of sponsor ads and their images. The request carries only the app version and operating system type; no account or install id.
- Ad impression totals (free plan, once a day): the number of times each campaign was shown, and the place (the village). Nothing identifies a person or a device.
- Ad clicks: clicking an ad opens your default browser on devalley.app/go/<campaign>, which forwards to the sponsor; the Operator counts clicks per campaign only.
- Official pack downloads and pack key requests (Pro, or a member who bought the pack): session token, pack name and version. Official pack files travel and stay encrypted; the app opens them in memory only, with a key it receives while entitled (for a pack used through Pro, valid until your current Pro ends).
- Community pack downloads (signed-in apps): session token, pack name and version. A pack received is kept in the account's record of packs you hold.
- Sync (Pro, only if you turn it on): the journal (each day's record, coins left out), avatars and the village settings (its name, decorations and the like) go up and come down with each entry's change time, to keep several PCs in step. Coins, XP and purchases live in the account's wallet and are not part of it, and residents an agent brought stay on that PC. Up to 5 MB per account.
6. Collected automatically
- Cookies: the sign-in session cookie (dv. prefix), the state cookie used only while signing in (dv.state) and the language cookie (dv_lang); see Article 9.
- Google ads on the site (free-plan members and visitors not signed in): on a page that shows one, Google itself collects, with its own cookies and similar technologies, a browser or device identifier, the IP address, the address of the page, browser and device details, and the ad impressions and clicks. The Operator does not receive these and sees only the totals Google reports (impressions, clicks, earnings). Article 9, items 5 to 7 have the details.
- Site analytics (Google Analytics, on the site’s public pages only): with the random identifier in the analytics cookies Google sets on the site (_ga and cookies starting ga), it counts visits from the same browser together and gathers the addresses of the page seen and the previous page (with no query but a campaign’s), the page title, the time spent, actions within the page such as scrolling, clicks on outside links and file downloads, the browser, operating system and device type, screen size, language, and an approximate location (city level) estimated from the IP address. Google Analytics does not store IP addresses. The Operator sees only statistical reports that identify no one, and never links them to an account. Article 9, items 8 to 10 have the details.
- Bot protection (only when turned on): if the Operator turns on Cloudflare Turnstile, it sends browser characteristics and your IP address from the post and comment forms to Cloudflare to tell people from bots, and the Operator receives only the result. It is off at present; sign-in and posting are guarded by rate limits alone.
- The hosting provider's (Cloudflare) security and operations logs: request time, IP address, path, response code, kept briefly under Cloudflare's policy.
- Rate-limit counters keyed by the IP address or a keyed hash of it, or by account id (deleted within 3 days at most).
- Sponsor ad impression and click totals per campaign, day and place. Automated requests such as search robots are not counted, and nothing in them identifies a person.
- App downloads: how often the site's download buttons (/download/latest/<platform>) were used, as totals per day and platform only.
7. What never reaches the Operator, and where the app connects by itself
- The following stays on your computer: the contents and state of your terminal and agent sessions, what you write and the answers in the conversation window, repository names and paths, your inbox and to-dos, tokens for Slack, GitHub, Vercel and other services, agent credentials, and the full village journal (except the journal records in item 5 when you turn on Pro sync). A signed-in member's coins, XP and purchases are kept with the account through the wallet in item 5.
- To show usage, while the village window or the usage card is open, the app asks Anthropic (Claude Code, api.anthropic.com), OpenAI (Codex, chatgpt.com) and Google (Gemini CLI, oauth2.googleapis.com and cloudcode-pa.googleapis.com) directly, at most every 15 minutes per agent, with the sign-in you already have in that agent (on Windows, when you use Claude Code only inside WSL, with the sign-in inside that distribution). The app only reads the agents' sign-in files on this computer or (on Windows) inside WSL and never changes them. From a sign-in inside WSL it holds one access token in memory for that request only and writes nothing inside WSL. When Gemini's hourly token has expired, the app fetches a new one and keeps it in its memory until it expires; Gemini CLI updates its own file.
- When you connect Slack, GitHub or Vercel, the app also connects to that service (slack.com, api.github.com, api.vercel.com) directly with your token.
- None of these connections goes through the Operator's server, and the Operator receives none of their content. Otherwise the app connects to devalley.app alone: to check for and download new versions (the Operator's server sees your IP address at that moment) and, on the free plan, for the ad list. Installing an update is your choice (the Windows installer downloads a new version ahead and installs it only when you choose it in the tray menu).
Article 2 (Why we process it)
The Operator processes personal data only for these purposes and, if a purpose changes, takes the steps Article 18 of the Personal Information Protection Act requires, such as obtaining separate consent.
- Accounts: identification, sign-in, handle uniqueness, blocking sign-ups under 14, recording consent, handling restrictions and disputes, delivering notices.
- Providing the Service: running the community, galleries and studio, showing public profiles, selling packs and letting you download the packs you hold again, reviewing packs, handling reports and support posts, relaying requests between the site and the app, notifications.
- Pro and billing: reflecting subscription and pack payment state, checking trial and promotion eligibility (one per person), keeping the list of signed-in devices, keeping official pack download records, handling refunds and disputes.
- Safety and abuse prevention: blocking bots and spam, rate limiting, detecting account takeover, enforcing the terms, meeting legal duties.
- Improving the Service: aggregate statistics on feature use and sign-up and conversion paths, in a form that identifies no one. Visits to the site’s public pages and where they come from are analysed with Google Analytics (Article 9, item 8).
- Essential notices: what the Service cannot do without, such as billing, the end of a trial or PRO, changes to the terms and restrictions, given by site notification and in the app instead of email. Notices the law requires, such as of a security incident, are given by whatever reaches you, email included. Marketing email is sent only with your separate consent.
- Funding the free plan: placing sponsor ads and counting impression and click totals per campaign (sponsors receive totals only). The site also carries Google AdSense ads (Article 9, item 5).
Article 3 (How long we keep it)
- The Operator keeps personal data within the periods the law or your consent allows.
- Retention by item:
| Item | Period |
|---|---|
| Account data (email, name, handle, profile), sign-in links, sessions, village settings (your residents' names and outfits), notifications, install requests, support board posts | Deleted or de-identified as soon as you ask to leave (no restoring) |
| Subscription, grant and promo-code records needed to reconcile payments, consent and restriction records, likes | Kept tied only to a random account id, then deleted within 30 days of leaving |
| The wallet (coins, XP, history) and the clothes, decorations and packs you own | Deleted as soon as you ask to leave (no restoring) |
| The sync copy (Pro) | Kept, locked, when Pro ends; deleted at once when you remove it or leave |
| Community content | Posts and comments stay with the author link removed (paragraph 4); looks are made private and community packs taken down at once, and the version files no member holds and the covers are deleted (versions other members hold are kept so they can download them again); the remaining records are deleted within 30 days |
| Deleted posts and comments | Title and body erased at once when the author deletes them; kept 30 days, then erased, when staff delete them (meanwhile seen by staff only, to check an objection) |
| Images uploaded but put in no post or comment | 1 day from upload |
| The warranty confirmation of a pack version (time and wording) | As long as that version's file is on the server |
| Support board posts (with the app details and, for refunds, the payment details) | Kept like other posts; deleted at once when you leave |
| Sign-in sessions (including IP address and browser or app details) | Deleted on sign-out or expiry; a session expires 30 days after its last use |
| Sign-in records (account, time, IP address, site or app) | 3 months (access records), after leaving too until then |
| Device codes for the app's sign-in | Deleted when used, or within an hour after they expire unused (30 minutes) |
| Rate-limit counters | 3 days at most from when counting started |
| Site notifications | 90 days after they are made, read or not |
| Requests sent from the site to the app | 7 days after the app takes them, 30 days if it never does |
| Reports (target, reason, details, reporter) and copyright request records | 3 years after they are handled; open ones until handled |
| Free-trial record (email hash) | Kept after account deletion to enforce one trial per person |
| Keyed hash of the email of an account that left, and until when it is blocked | 1 day (the same email cannot sign up again for a day) |
| Keyed hash of the email of an account closed for a breach of the terms | 3 years (the same email cannot sign up again meanwhile) |
| Raw subscription events from the payment processor | 5 years from receipt |
| Agreements to the limit on withdrawal before a checkout (what was being bought, the wording, the time) | 5 years from the agreement |
| Operations records (checkout error diagnostics, audit log of restrictions, deletions and administrative actions, and of administrators viewing or searching members' details) | 3 years; after account deletion only the random account id remains |
| Support and refund mail (mail to support@devalley.app and its attachments) | 3 years from receipt (consumer complaint and dispute records) |
| Requests to access, correct, delete or stop processing personal data, and how they were handled | 3 years |
| Official pack download records (pack, version, install id or site mark, size, time), Pro feature use records and PRO end records | 3 years (consumer dispute records); unlinked from the account once it is deleted |
| Sponsor ad impression and click totals (per campaign, day and place) | 2 years (statistics, not personal data; the basis for sponsor billing) |
| Site analytics records tied to the cookie identifier (Google Analytics) | Deleted by Google after the period the Operator sets in Google Analytics (14 months at most); aggregate reports that identify no one remain |
| App download totals (per day and platform) | Statistics, not personal data, kept while the Service runs |
- Under Korean law the following are kept after you leave: the raw payment and subscription events Paddle sent and the agreements to the limit on withdrawal made before a checkout, 5 years; official pack download records and Pro feature use records, 3 years; support and refund mail, 3 years (the payment and the consumer complaint and dispute records of the Act on Consumer Protection in Electronic Commerce). The original records of contracts, withdrawals and payments are held by Paddle as merchant of record. The Operator keeps sign-in records (account, time, IP address, site or app) for 3 months and then deletes them (the access records of the Protection of Communications Secrets Act). The server's logs never hold email addresses, sign-in links or secrets.
- Posts and comments you made public remain as those of a "deleted user" with the author link removed. Public packs and looks may remain in copies other members already downloaded.
- An account with no sign-in for a year may be deleted after notice posted on the Site and sent as a site notification 30 days ahead (not while a paid subscription is active).
Article 4 (Sharing with third parties)
- The Operator processes personal data only within the purposes in Article 2 and shares it with third parties only: (a) with your separate consent; (b) where a law so provides or legal duties make it unavoidable; (c) where urgently needed to protect someone's life, body or property; (d) on a lawful request from investigators or a court.
- A profile you set to public (handle, display name, chief look, public looks and packs, posts and comments) is visible to other signed-in members, and the boards' post lists (title, author, time, comment count) and notice posts are visible to visitors who are not signed in. Support board posts are seen only by their author and staff. That is disclosure you chose, not third-party sharing.
- If the business is transferred or moved to a business or company the Operator forms, personal data is transferred after prior notice under Article 27 of the Personal Information Protection Act.
Article 5 (Processors and transfers abroad)
- The Operator entrusts processing to the providers below, all located outside Korea, so personal data is transferred to and stored abroad. This is disclosed here as entrustment and storage necessary to perform the contract under Article 28-8(1)3 of the Personal Information Protection Act.
| Recipient (contact) | Country | Data | Purpose | When and how | Retention |
|---|---|---|---|---|---|
| Cloudflare, Inc. (privacy@cloudflare.com) | United States (global edge) | Everything in Article 1 | Hosting of the server, database and file storage, security, bot protection (Turnstile), email forwarding | Continuously over the network as the Service is used | Until the engagement ends or the periods in Article 3 |
| Paddle.com Market Limited (privacy@paddle.com) | United Kingdom | Email address, country, payment-method details (collected by Paddle itself), subscription state, pack payments | Payments, taxes, receipts and refunds for Pro and packs as merchant of record | At checkout | Paddle's policy and statutory periods |
| GitHub, Inc. (privacy@github.com) | United States | Sign-in request (OAuth) | GitHub sign-in | When you choose GitHub sign-in | GitHub's policy |
| Google LLC (https://support.google.com/policies?p=privpol_privts) | United States | Sign-in request (OAuth) | Google sign-in | When you choose Google sign-in | Google's policy |
| Anthropic, PBC (https://privacy.claude.com) | United States | Public URL entered, public page information and generated draft | Drafting a service introduction from the chosen URL | Sent by API when you request a draft | Anthropic’s API retention policy and applicable account settings |
| Google LLC (https://support.google.com/policies?p=privpol_privts) | United States | The site analytics items in Article 1, item 6 (cookie identifier, page address, browser and device details, approximate location) | Site analytics (Google Analytics) and Google Tag Manager, which loads its tag | Over the network when a public page of the site is opened | The period the Operator sets (14 months at most) |
| The Operator's mail service: Google LLC (Gmail) (https://support.google.com/policies?p=privpol_privts) | United States | The address, content and attachments (logs and the like) of support and refund mail | Answering support requests | When you send the mail | 3 years |
- You may object to these transfers at support@devalley.app. You can decline transmission to Anthropic by writing posts directly without using URL drafts. Objecting to transfers required for account services means you cannot create or use an account; the app's free features remain available without one.
- The Operator supervises these processors through their data processing agreements and standard contractual clauses. This policy is updated when a processor changes. The Operator uses no mail-sending provider at present; one is added to this table, with notice, when the Service starts sending mail.
Article 6 (Destruction)
- Personal data whose retention period has passed or whose purpose is fulfilled is destroyed without delay.
- When you ask to leave, your email, name, profile image, sign-in links, sessions, village settings, notifications, install requests, support board posts and wallet are deleted or made unidentifiable at once, your looks are made private, your community packs are taken down (descriptions and covers cleared, shown as by a "deleted user"), and posts and comments are detached from you. The subscription, grant and promo-code records, consent and restriction records and likes left tied only to a random account id are deleted from the database by a daily job within 30 days. A deleted account cannot be restored.
- Electronic files are deleted irrecoverably. An attached image in file storage (R2) is deleted once no post or comment that shows it remains, an image uploaded but put in no post or comment is deleted after a day, the images of a post or comment deleted on a report are deleted with it, and the images of hidden or deleted posts are not served. When you leave, the images no remaining post or comment shows, your community packs' covers and the pack version files no member holds are deleted at once. Pack version files other members hold are kept so they can download them again, except illegal information the law requires removed, which is deleted even if someone holds it. The title and body of a post or comment its author deletes are erased at once; what staff delete is kept 30 days (seen by staff only, to check an objection), then erased. A handled report is deleted 3 years after it was handled. The hosting provider's backups expire on its own schedule.
- Data that must be kept by law is stored separately and used for that purpose only.
Article 7 (Your rights and how to exercise them)
- You may at any time ask to access, correct, delete or stop processing your personal data, or withdraw consent.
- On the site itself: view and edit in Profile and Settings; delete the account on the Data page; change visibility and end sign-in sessions in Settings.
- Requests to access (a copy of all your data included), correct, delete or stop processing are taken on the support board (signed-in members) or at support@devalley.app. A post left while signed in counts as your own request. Mail is accepted only from the email address you signed up with; from any other address, the Operator first sends a confirmation to the address you signed up with and acts once it is answered. The Operator acts within 10 days of receipt and tells you the outcome, and keeps the request and how it was handled for 3 years. A representative must present a power of attorney together with your confirmation. The copy of your data is a JSON file; secrets such as session tokens are left out for security and named in the file.
- Access and suspension requests may be limited under Articles 35(4) and 37(2) of the Personal Information Protection Act, and data the law requires us to collect cannot be deleted on request.
- The Operator does not collect personal data of children under 14 and deletes any such account and data as soon as it learns of one. A legal guardian may request deletion at support@devalley.app.
- Keep your data current. Liability for using someone else's data rests with the person who did so.
Article 8 (Security measures)
Under Article 29 of the Personal Information Protection Act the Operator:
- Administratively: limits access to personal data to the Operator alone, keeps an audit log of administrative actions, and supervises processors. Moderators who help with the community see only a member's id, name, handle, role and whether they are suspended or have left, and cannot look a member up by email. When an administrator opens a member's details or looks members up by email, the audit log records who looked, when and at whom (for a search, the number of results, never the query); it is kept 3 years and read through once a month.
- Technically: encrypts every connection (HTTPS/TLS) and stored data (through the hosting provider), uses passwordless sign-in (OAuth, one-time links), expires session tokens and lets you end sessions, hashes the trial record, applies bot protection and rate limits, validates the type and size of uploads, stores official pack files encrypted (keys are issued only to an entitled account's app), and signs the plan statement sent to the app.
- Minimises data: takes no payment-method details, keeps village data on your computer, runs no analytics in the app, and analyses the site’s public pages with Google Analytics, sending page addresses without their query and never linking them to an account (Article 9, item 8); its only third-party ad network is Google AdSense on the site (Article 9, item 5), never in the app. The sponsor ads shown on the free plan are placed by the Operator by hand, track no one, and are counted only as per-campaign totals.
- Responds to incidents: on learning that personal data has leaked, been lost or been stolen, the Operator stops it at once (replacing secrets, ending every session) and within 72 hours at the latest tells you what leaked, when and how, how to limit the harm, what the Operator is doing and how to seek remedy, and whom to contact. Notice is given by a post on the notice board, a site notification and a notice in the app, and mail to the sign-up address of each member affected. Where Article 34 of the Act requires it, such as a leak of 1,000 people's data or more or one through unlawful access from outside, the Operator also reports it within 72 hours to the Personal Information Protection Commission or KISA.
Article 9 (Cookies and automatic collection)
- The site uses only these cookies: the session cookie that keeps you signed in (dv. prefix, Secure and HttpOnly, 30 days from last use), the state cookie used only while you sign in (dv.state, 5 minutes) and the cookie that remembers your language (dv_lang, one year). When you open the checkout, the script of Paddle, the payment processor, may use its own cookies and storage to process the payment, under Paddle's privacy policy. Your choice to hide the sponsor ads for 12 hours stays in your browser's and the app's local storage and is never sent to the server. The Operator sets no advertising or tracking cookies, and its only analytics cookies are Google Analytics’ on the site’s public pages (item 8); the cookies Google sets where the site shows a Google ad are in item 5.
- When turned on, Cloudflare Turnstile may set its own cookie for bot protection, under Cloudflare's privacy policy.
- You may refuse cookies in your browser; refusing the session cookie means you cannot stay signed in.
- The Operator collects no behavioural data for personalised advertising; the site analytics (item 8) serve visit statistics only and are not used for ads. The sponsor ads it places itself are the same for everyone. Google ads on the site may be personalised by Google from behavioural data; how that is collected and refused is in items 5 to 7. Should another analytics tool or third-party ad network ever be introduced, this policy will be updated beforehand.
- Google ads on the site (Google AdSense): Google LLC (United States) collects the data itself, under Google's privacy policy (https://policies.google.com/privacy). The ads appear only on the column's pieces and the community boards' posts, for free-plan members and visitors not signed in. They never appear on the post lists, the home page, the download and Pro pages, the docs, signing in, the legal texts, the contact page, the support board, members' screens such as notifications and the studio, the screens of Pro members and staff, or in the app (the village). Where an ad shows, Google's script automatically collects, with cookies and similar technologies, a browser or device identifier, the IP address, the page address, browser and device details and the ad impressions and clicks.
- Google uses this to serve ads, to personalise them to your interests, to limit repeats, to prevent invalid clicks and to measure ads, and keeps it as its own policy says (https://policies.google.com/technologies/ads). How Google uses data from partner sites: https://policies.google.com/technologies/partner-sites.
- How to refuse: the × on the ad slot keeps that browser from loading Google ads and their script for 12 hours; Google's ad settings (https://adssettings.google.com) turn personalised ads off; your browser can block third-party cookies; the Pro plan has no ads. Visitors from the European Economic Area, the United Kingdom and Switzerland see personalised Google ads only if they consent, as Google's policies require.
- Site analytics (Google Analytics 4 and Google Tag Manager): Google LLC (United States) processes the data for the Operator, under Google's privacy policy (https://policies.google.com/privacy) and how Google uses data from partner sites (https://policies.google.com/technologies/partner-sites). They load only on the site's public pages (the home page, the download and Pro pages, the column and boards, signing in, the legal texts and the like), never on my page, the studio, approving an app sign-in, notifications, the support board, the staff console or in the app (the village), and on no page at all for visitors from the European Economic Area, the United Kingdom or Switzerland, or whose country is unknown. Google Tag Manager only loads the analytics tag: it sets no cookie and sends no page address to Google itself, and the Operator will update this policy before putting any other tag in it.
- The analytics cookies ga (tells browsers apart) and those starting ga (keep a visit's session) stay on the site (devalley.app) for 2 years from your last visit. The addresses of the page and the previous page sent to Google Analytics lose their query, but for campaign markers (utm and the like), and anything after #, so no search terms or sign-in values go with them. The Operator turns on neither Google signals nor any advertising link in Google Analytics, sends it no member identifier or email address, and sees only statistical reports that identify no one (visits, where they come from, the most-read pages).
- How to refuse: blocking or clearing devalley.app's cookies in your browser leaves no analytics cookie, and Google's opt-out add-on (https://tools.google.com/dlpage/gaoptout) keeps your data from reaching Google Analytics. Refusing takes nothing away from the site or the app.
Article 10 (Additional use or disclosure without consent)
Where Articles 15(3) and 17(4) of the Personal Information Protection Act allow additional use or disclosure without consent, the Operator considers whether it relates to the original purpose, whether it is foreseeable from the circumstances and practice, whether it unfairly harms your interests, and whether safeguards such as pseudonymisation or encryption are in place.
Article 11 (Privacy officer)
- The Operator designates the following privacy officer to oversee processing and handle complaints and remedies:
- Privacy officer: Dong-hyeok Kim (the Operator of Devalley)
- Contact: support@devalley.app
- Any question, complaint or request for remedy about personal data may be addressed to the privacy officer, who answers without delay.
- Requests to access, correct, delete or stop processing, and complaints, are received and handled by the privacy officer directly (Article 7(3)).
Article 12 (Remedies)
You may seek remedy or advice about a privacy infringement from the following Korean bodies, which are independent of the Operator:
- Personal Information Dispute Mediation Committee: 1833-6972, www.kopico.go.kr
- Personal Information Infringement Report Center (KISA): 118, privacy.kisa.or.kr
- Supreme Prosecutors' Office, Cyber Investigation Division: 1301, www.spo.go.kr
- National Police Agency, Cyber Bureau: 182, ecrm.police.go.kr
A person whose rights are infringed by a public institution's decision or inaction on a request under Articles 35 (access), 36 (correction and deletion) or 37 (suspension) of the Act may file an administrative appeal under the Administrative Appeals Act.
Article 13 (Users outside Korea)
- The Service is operated from Korea. If you use it from elsewhere, your data is transferred to and processed in Korea and in the countries listed in Article 5.
- Residents of the European Economic Area and the United Kingdom: the Operator relies on performance of a contract (providing accounts and Pro), legitimate interests (security, abuse prevention, improvement), legal obligations, and consent (sharing features, marketing email) as legal bases. You have the rights of access, rectification, erasure, restriction, portability and objection, and may lodge a complaint with a supervisory authority. Transfers rely on the European Commission's standard contractual clauses and each processor's adequacy framework.
- Residents of California and other U.S. states with privacy laws: the Operator does not sell personal data. Through the Google ads on the site, Google may collect data itself for personalised advertising, which you can refuse as Article 9, item 7 says. Requests to know, delete or correct are made as in Article 7, and you will not be discriminated against for exercising them.
- The Korean text of this article prevails where interpretations differ.
Article 14 (Changes to this policy)
- This policy applies from November 25, 2026 and replaces the earlier draft.
- Changes following law or the Service are announced on the site at least 7 days before they take effect. Material changes to the data collected or its purposes, or changes unfavourable to your rights, are announced 30 days ahead and, where needed, consent is sought again.
- Earlier versions are available from the Operator on request.
Contact: support@devalley.app