Purchase terms, licenses, and privacy
What you buy, your rights, how refunds work, and how your information is handled.
Licenses overview
Which license covers each edition, and who owns the text you write with Whalory: you do, in every edition.
Read the text
This file says which license covers each Whalory edition and where the full text of each license is. Read it before you install Whalory in an organization, share it, build your own version, or sell text you wrote with it. The editions are Whalory Core (free), Whalory Pro, and Whalory Studio. Persian version: LICENSE.md.
At a glance
| Edition | Files | License | Full text |
|---|---|---|---|
| Whalory Core | Core files | Text: Creative Commons Attribution 4.0 (CC BY 4.0); scripts: the MIT License | LICENSE-CORE.en.md |
| Whalory Pro | Core files | Same as Core | LICENSE-CORE.en.md |
| Whalory Pro | Added files and sections, the packs for each assistant, channel data | End-user license agreement; one person | EULA.en.md, EULA.fa.md |
| Whalory Studio | The same files as Pro | End-user license agreement; as many seats as the order states | EULA.en.md, EULA.fa.md |
Core files keep their open license inside Pro and Studio too. Buying a paid edition takes nothing away from the rights that CC BY 4.0 and MIT give you.
Which files belong to which edition
- Core files:
SKILL.mdand the front page, guide, changelog, and license files in both languages;- the method files in
references/: context detection, question gate, judgment, brief, gathering, the playbooks, review, editor, voice profile, and profile builder; - eleven craft files in each language pack,
references/fa/andreferences/en/: craft, prose, common errors, conventions (Persian) or style guide (English), AI tells, occasions, claims, ethics, channels, forms, and style repair; - the profile templates, Whalory's own voice, and the café and SaaS starter profiles, in both languages;
- in
scripts/, the linters, the shared counters, the Model Context Protocol (MCP) server, and the self-tests with their samples.
- The Core plugin and bundle. The Core plugin carries the Core license: its manifests, both of its agents (writer and editor), the
write,review,voice, andlintcommands, and the opt-in autolint hook. So does the Core.mcpbbundle. - Files in every edition.
VERSIONandagents/openai.yamlship with all three editions under the Core license. The icons inassets/icon-*, when present, also ship with every edition. They are trademarks of the Whalya studio, though, and fall under no license, as the name and logo section explains. - Pro sections inside Core files. Any text between
<!-- pro -->and<!-- /pro -->is not part of Core and falls under the Pro license. - Pro files. Every other reference and profile,
data/, the other scripts, the remaining agents, the remaining commands, and the packs for each assistant. - In a purchased package. The
editionfield at the top ofSKILL.mdnames the edition, andLICENSE-BUYER.txtholds the buyer's license identifier.
Text you write with Whalory
This is the same in all three editions:
- It's yours. The Whalya studio claims no rights in the text you write with Whalory's help.
- Commercial use is allowed. That covers your own work and your clients' work. You don't need to mention Whalory in the text.
- Whoever publishes the text answers for it: correct facts, claims, permits, and compliance with the law. Whalory marks missing facts with brackets, and filling them in is your job.
The editions don't differ in your right to use what you write. They differ in the number of users, the packs, updates, and support.
Name and logo
The product names "Whalory" and «والوری», the studio name "Whalya" and «والیا», and their logos are not covered by any of these licenses. You may use them to credit Whalory, as described in how to credit Whalory. A version you changed takes its own name and must not be presented as endorsed by the Whalya studio.
Other people's services
Whalory is a set of files. It sells no access to any assistant or model. Every assistant you install Whalory on has its own terms, and those terms are separate from these licenses.
Questions about licensing
Contact: the contact page on the Whalory website. The legal text is only what LICENSE-CORE.en.md and EULA.en.md say; this page is a summary.
The full license texts linked above set out the applicable terms.
Core license: CC BY 4.0 for text, MIT for scripts
The full open license texts and how to credit Whalory when sharing its files.
Read the text
This file holds the full text of the two licenses for Whalory Core. Creative Commons Attribution 4.0 International (CC BY 4.0) covers the text, and the MIT License covers the scripts. Read it before you use Whalory in your own work, change it, or share it. What each edition includes, and who owns the text you write, is in LICENSE.en.md. Persian version: LICENSE-CORE.md.
Contents
- Which file, which license
- How to credit Whalory
- Text you write with Whalory
- Full text of CC BY 4.0
- Full text of the MIT License
Which file, which license
| Part | License | Software Package Data Exchange (SPDX) id |
|---|---|---|
Every file in a scripts/ folder of the skill or the Core plugin, including the test samples in scripts/samples/ | MIT | MIT |
Every other Core file: SKILL.md, the guides, references/, profiles/, and the Core plugin's agents and commands | Creative Commons Attribution 4.0 International | CC-BY-4.0 |
- Rights holder: the Whalya studio («استودیو والیا»), which makes Whalory, 2026 (1405 in the Iranian calendar).
- The license can't be taken back. CC BY 4.0 grants a worldwide, royalty-free, and irrevocable license (Section 2(a)(1)). A version published under it stays under it, even if a later version gets another license.
- Names and logos are not licensed. CC BY 4.0 does not license trademark rights (Section 2(b)(2)). The product names "Whalory" and «والوری», the studio name "Whalya" and «والیا», and their logos may be used only to credit Whalory.
- Pro parts are separate. Text between
<!-- pro -->and<!-- /pro -->, and files that ship only in Whalory Pro and Whalory Studio, are not covered by this file. Their license is described inLICENSE.en.md.
How to credit Whalory
CC BY 4.0 sets four duties for anyone who shares the material (Section 3(a)(1)). Credit the creator, refer to the license, and link to the source where that is reasonably practicable. Say whether you changed it. Copy one of these lines and fill in the brackets:
Based on Whalory by the Whalya studio, https://github.com/gilebehnam/whalory, licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). [Unmodified / Modified: one line on what changed]- A changed version takes its own name. The license gives you no permission to suggest that the Whalya studio endorses or sponsors your work (Section 2(a)(6)).
- In the scripts, keep the copyright line and the MIT license text next to the code.
Text you write with Whalory
- It's yours. The Whalya studio claims no rights in the text you write with Whalory's help. Commercial use is allowed, and you don't need to credit Whalory in that text.
- The limit: this freedom doesn't cover sharing Whalory's own files. If you publish part of a reference word for word, credit it as described above.
- The responsibility: whoever publishes the final text answers for the facts, the claims, and compliance with the law.
The full license texts below set out the applicable terms.
Full text of CC BY 4.0
The text below is copied unchanged from the official source (retrieved 2026-09-27 from creativecommons.org).
Attribution 4.0 International
=======================================================================
Creative Commons Corporation ("Creative Commons") is not a law firm and
does not provide legal services or legal advice. Distribution of
Creative Commons public licenses does not create a lawyer-client or
other relationship. Creative Commons makes its licenses and related
information available on an "as-is" basis. Creative Commons gives no
warranties regarding its licenses, any material licensed under their
terms and conditions, or any related information. Creative Commons
disclaims all liability for damages resulting from their use to the
fullest extent possible.
Using Creative Commons Public Licenses
Creative Commons public licenses provide a standard set of terms and
conditions that creators and other rights holders may use to share
original works of authorship and other material subject to copyright
and certain other rights specified in the public license below. The
following considerations are for informational purposes only, are not
exhaustive, and do not form part of our licenses.
Considerations for licensors: Our public licenses are
intended for use by those authorized to give the public
permission to use material in ways otherwise restricted by
copyright and certain other rights. Our licenses are
irrevocable. Licensors should read and understand the terms
and conditions of the license they choose before applying it.
Licensors should also secure all rights necessary before
applying our licenses so that the public can reuse the
material as expected. Licensors should clearly mark any
material not subject to the license. This includes other CC-
licensed material, or material used under an exception or
limitation to copyright. More considerations for licensors:
wiki.creativecommons.org/Considerations_for_licensors
Considerations for the public: By using one of our public
licenses, a licensor grants the public permission to use the
licensed material under specified terms and conditions. If
the licensor's permission is not necessary for any reason--for
example, because of any applicable exception or limitation to
copyright--then that use is not regulated by the license. Our
licenses grant only permissions under copyright and certain
other rights that a licensor has authority to grant. Use of
the licensed material may still be restricted for other
reasons, including because others have copyright or other
rights in the material. A licensor may make special requests,
such as asking that all changes be marked or described.
Although not required by our licenses, you are encouraged to
respect those requests where reasonable. More considerations
for the public:
wiki.creativecommons.org/Considerations_for_licensees
=======================================================================
Creative Commons Attribution 4.0 International Public License
By exercising the Licensed Rights (defined below), You accept and agree
to be bound by the terms and conditions of this Creative Commons
Attribution 4.0 International Public License ("Public License"). To the
extent this Public License may be interpreted as a contract, You are
granted the Licensed Rights in consideration of Your acceptance of
these terms and conditions, and the Licensor grants You such rights in
consideration of benefits the Licensor receives from making the
Licensed Material available under these terms and conditions.
Section 1 -- Definitions.
a. Adapted Material means material subject to Copyright and Similar
Rights that is derived from or based upon the Licensed Material
and in which the Licensed Material is translated, altered,
arranged, transformed, or otherwise modified in a manner requiring
permission under the Copyright and Similar Rights held by the
Licensor. For purposes of this Public License, where the Licensed
Material is a musical work, performance, or sound recording,
Adapted Material is always produced where the Licensed Material is
synched in timed relation with a moving image.
b. Adapter's License means the license You apply to Your Copyright
and Similar Rights in Your contributions to Adapted Material in
accordance with the terms and conditions of this Public License.
c. Copyright and Similar Rights means copyright and/or similar rights
closely related to copyright including, without limitation,
performance, broadcast, sound recording, and Sui Generis Database
Rights, without regard to how the rights are labeled or
categorized. For purposes of this Public License, the rights
specified in Section 2(b)(1)-(2) are not Copyright and Similar
Rights.
d. Effective Technological Measures means those measures that, in the
absence of proper authority, may not be circumvented under laws
fulfilling obligations under Article 11 of the WIPO Copyright
Treaty adopted on December 20, 1996, and/or similar international
agreements.
e. Exceptions and Limitations means fair use, fair dealing, and/or
any other exception or limitation to Copyright and Similar Rights
that applies to Your use of the Licensed Material.
f. Licensed Material means the artistic or literary work, database,
or other material to which the Licensor applied this Public
License.
g. Licensed Rights means the rights granted to You subject to the
terms and conditions of this Public License, which are limited to
all Copyright and Similar Rights that apply to Your use of the
Licensed Material and that the Licensor has authority to license.
h. Licensor means the individual(s) or entity(ies) granting rights
under this Public License.
i. Share means to provide material to the public by any means or
process that requires permission under the Licensed Rights, such
as reproduction, public display, public performance, distribution,
dissemination, communication, or importation, and to make material
available to the public including in ways that members of the
public may access the material from a place and at a time
individually chosen by them.
j. Sui Generis Database Rights means rights other than copyright
resulting from Directive 96/9/EC of the European Parliament and of
the Council of 11 March 1996 on the legal protection of databases,
as amended and/or succeeded, as well as other essentially
equivalent rights anywhere in the world.
k. You means the individual or entity exercising the Licensed Rights
under this Public License. Your has a corresponding meaning.
Section 2 -- Scope.
a. License grant.
1. Subject to the terms and conditions of this Public License,
the Licensor hereby grants You a worldwide, royalty-free,
non-sublicensable, non-exclusive, irrevocable license to
exercise the Licensed Rights in the Licensed Material to:
a. reproduce and Share the Licensed Material, in whole or
in part; and
b. produce, reproduce, and Share Adapted Material.
2. Exceptions and Limitations. For the avoidance of doubt, where
Exceptions and Limitations apply to Your use, this Public
License does not apply, and You do not need to comply with
its terms and conditions.
3. Term. The term of this Public License is specified in Section
6(a).
4. Media and formats; technical modifications allowed. The
Licensor authorizes You to exercise the Licensed Rights in
all media and formats whether now known or hereafter created,
and to make technical modifications necessary to do so. The
Licensor waives and/or agrees not to assert any right or
authority to forbid You from making technical modifications
necessary to exercise the Licensed Rights, including
technical modifications necessary to circumvent Effective
Technological Measures. For purposes of this Public License,
simply making modifications authorized by this Section 2(a)
(4) never produces Adapted Material.
5. Downstream recipients.
a. Offer from the Licensor -- Licensed Material. Every
recipient of the Licensed Material automatically
receives an offer from the Licensor to exercise the
Licensed Rights under the terms and conditions of this
Public License.
b. No downstream restrictions. You may not offer or impose
any additional or different terms or conditions on, or
apply any Effective Technological Measures to, the
Licensed Material if doing so restricts exercise of the
Licensed Rights by any recipient of the Licensed
Material.
6. No endorsement. Nothing in this Public License constitutes or
may be construed as permission to assert or imply that You
are, or that Your use of the Licensed Material is, connected
with, or sponsored, endorsed, or granted official status by,
the Licensor or others designated to receive attribution as
provided in Section 3(a)(1)(A)(i).
b. Other rights.
1. Moral rights, such as the right of integrity, are not
licensed under this Public License, nor are publicity,
privacy, and/or other similar personality rights; however, to
the extent possible, the Licensor waives and/or agrees not to
assert any such rights held by the Licensor to the limited
extent necessary to allow You to exercise the Licensed
Rights, but not otherwise.
2. Patent and trademark rights are not licensed under this
Public License.
3. To the extent possible, the Licensor waives any right to
collect royalties from You for the exercise of the Licensed
Rights, whether directly or through a collecting society
under any voluntary or waivable statutory or compulsory
licensing scheme. In all other cases the Licensor expressly
reserves any right to collect such royalties.
Section 3 -- License Conditions.
Your exercise of the Licensed Rights is expressly made subject to the
following conditions.
a. Attribution.
1. If You Share the Licensed Material (including in modified
form), You must:
a. retain the following if it is supplied by the Licensor
with the Licensed Material:
i. identification of the creator(s) of the Licensed
Material and any others designated to receive
attribution, in any reasonable manner requested by
the Licensor (including by pseudonym if
designated);
ii. a copyright notice;
iii. a notice that refers to this Public License;
iv. a notice that refers to the disclaimer of
warranties;
v. a URI or hyperlink to the Licensed Material to the
extent reasonably practicable;
b. indicate if You modified the Licensed Material and
retain an indication of any previous modifications; and
c. indicate the Licensed Material is licensed under this
Public License, and include the text of, or the URI or
hyperlink to, this Public License.
2. You may satisfy the conditions in Section 3(a)(1) in any
reasonable manner based on the medium, means, and context in
which You Share the Licensed Material. For example, it may be
reasonable to satisfy the conditions by providing a URI or
hyperlink to a resource that includes the required
information.
3. If requested by the Licensor, You must remove any of the
information required by Section 3(a)(1)(A) to the extent
reasonably practicable.
4. If You Share Adapted Material You produce, the Adapter's
License You apply must not prevent recipients of the Adapted
Material from complying with this Public License.
Section 4 -- Sui Generis Database Rights.
Where the Licensed Rights include Sui Generis Database Rights that
apply to Your use of the Licensed Material:
a. for the avoidance of doubt, Section 2(a)(1) grants You the right
to extract, reuse, reproduce, and Share all or a substantial
portion of the contents of the database;
b. if You include all or a substantial portion of the database
contents in a database in which You have Sui Generis Database
Rights, then the database in which You have Sui Generis Database
Rights (but not its individual contents) is Adapted Material; and
c. You must comply with the conditions in Section 3(a) if You Share
all or a substantial portion of the contents of the database.
For the avoidance of doubt, this Section 4 supplements and does not
replace Your obligations under this Public License where the Licensed
Rights include other Copyright and Similar Rights.
Section 5 -- Disclaimer of Warranties and Limitation of Liability.
a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
c. The disclaimer of warranties and limitation of liability provided
above shall be interpreted in a manner that, to the extent
possible, most closely approximates an absolute disclaimer and
waiver of all liability.
Section 6 -- Term and Termination.
a. This Public License applies for the term of the Copyright and
Similar Rights licensed here. However, if You fail to comply with
this Public License, then Your rights under this Public License
terminate automatically.
b. Where Your right to use the Licensed Material has terminated under
Section 6(a), it reinstates:
1. automatically as of the date the violation is cured, provided
it is cured within 30 days of Your discovery of the
violation; or
2. upon express reinstatement by the Licensor.
For the avoidance of doubt, this Section 6(b) does not affect any
right the Licensor may have to seek remedies for Your violations
of this Public License.
c. For the avoidance of doubt, the Licensor may also offer the
Licensed Material under separate terms or conditions or stop
distributing the Licensed Material at any time; however, doing so
will not terminate this Public License.
d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
License.
Section 7 -- Other Terms and Conditions.
a. The Licensor shall not be bound by any additional or different
terms or conditions communicated by You unless expressly agreed.
b. Any arrangements, understandings, or agreements regarding the
Licensed Material not stated herein are separate from and
independent of the terms and conditions of this Public License.
Section 8 -- Interpretation.
a. For the avoidance of doubt, this Public License does not, and
shall not be interpreted to, reduce, limit, restrict, or impose
conditions on any use of the Licensed Material that could lawfully
be made without permission under this Public License.
b. To the extent possible, if any provision of this Public License is
deemed unenforceable, it shall be automatically reformed to the
minimum extent necessary to make it enforceable. If the provision
cannot be reformed, it shall be severed from this Public License
without affecting the enforceability of the remaining terms and
conditions.
c. No term or condition of this Public License will be waived and no
failure to comply consented to unless expressly agreed to by the
Licensor.
d. Nothing in this Public License constitutes or may be interpreted
as a limitation upon, or waiver of, any privileges and immunities
that apply to the Licensor or You, including from the legal
processes of any jurisdiction or authority.
=======================================================================
Creative Commons is not a party to its public
licenses. Notwithstanding, Creative Commons may elect to apply one of
its public licenses to material it publishes and in those instances
will be considered the “Licensor.” The text of the Creative Commons
public licenses is dedicated to the public domain under the CC0 Public
Domain Dedication. Except for the limited purpose of indicating that
material is shared under a Creative Commons public license or as
otherwise permitted by the Creative Commons policies published at
creativecommons.org/policies, Creative Commons does not authorize the
use of the trademark "Creative Commons" or any other trademark or logo
of Creative Commons without its prior written consent including,
without limitation, in connection with any unauthorized modifications
to any of its public licenses or any other arrangements,
understandings, or agreements concerning use of licensed material. For
the avoidance of doubt, this paragraph does not form part of the
public licenses.
Creative Commons may be contacted at creativecommons.org.Full text of the MIT License
The MIT License text comes from the SPDX license list, with only the copyright line filled in (retrieved 2026-09-27 from SPDX).
MIT License
Copyright (c) 2026 Whalya
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.End-user license for Pro and Studio
Seats, continued use, ownership of outputs, updates, support, and refunds for paid editions.
Read the text
Terms version: 2026-10-04, effective October 4, 2026.
This license is between the buyer and the Whalya studio, the maker and seller of Whalory. Purchases are made on the Whalory website. Contact us privately through support. The version accepted at checkout is recorded with the order.
1. What you buy
- Pro: Whalory files for one person, with 12 months of updates and support for installation and product errors.
- Studio: the same collection for up to 5 people in one organization, with 12 months of updates and support.
- Pro renewal: another 12 months of updates and support on the same key. If the current period has not ended, the new period starts when it ends; otherwise, it starts on the renewal date.
- Checkout shows the total before payment. Whalory adds no further charge at the gateway. There is no automatic renewal or recurring charge.
2. Installation and continued use
You may install the files on your own devices, adapt them for your own use, and keep backups. Pro covers one person. Studio covers up to 5 people in one organization; access to shared installations must stay within those seats.
Versions received during the purchase period remain usable after the 12 months end, for the same number of people. New versions and continued support require renewal. Expiry does not disable files already received.
3. Your outputs
The text you write with Whalory is yours, including commercial work for yourself and your clients. You do not need to credit Whalory in that output. Check facts, claims, permissions, and applicable requirements before publishing.
4. Sharing paid files
You may not sell, rent, publish, or share paid files or license keys outside the seats covered by the purchase. This includes a public assistant or service that exposes the paid files to others. Keep the buyer identifier and copyright notices in the package.
Writing for clients, showing your outputs, and teaching writing methods are allowed. Core files retain their open licenses even within a paid package; see the Core license.
5. Delivery and keys
The payment result page shows the key and download links after the gateway confirms payment. Keep your key somewhere safe. The account page provides fresh download links using the key and the email or mobile number used at checkout. Do not send the key in public reports or support messages.
6. Support
Use the private support form for installation, tool errors, purchases, and file access. Include your order number and a description of the issue. Writing copy for you, creating custom brand profiles, and legal advice are separate services. No fixed response time or round-the-clock service is promised.
7. Refunds
You may request a full refund within 7 calendar days of a Pro, Studio, or renewal purchase. Downloading files does not disqualify you. Send the request through support. Once the buyer and order have been confirmed, the refund is processed within 7 working days and returned only to the original payer.
A refunded edition purchase loses its license; stop using and delete the paid files received under that purchase. A refunded renewal removes only the added update period, while the rights from earlier purchases remain. Text you already wrote remains yours. See the refund policy.
8. Assistants and responsibility
Whalory does not sell access to an AI model, account, or subscription. The assistant you choose has separate fees and terms. Local tools work without an API key. Model outputs can vary or contain errors; review the facts before publication. Whalory promises no sales result, search rank, or error-free output.
9. Disputes and changes
Contact support first to resolve a dispute. Mandatory consumer rights and access to the competent forum under applicable law are preserved; these terms do not limit them.
The terms accepted at checkout remain applicable to that order. Later changes do not retroactively change earlier purchases. Persian terms govern purchases made through the Persian checkout. Data practices are described in privacy.
Read support replies on the support page using your private tracking code. Keep that code; replies are not automatically emailed.
Privacy
What the shop keeps to deliver your files, find your license, and answer support: the name and contact you give at checkout.
Read the text
Terms version: 2026-10-04, effective October 4, 2026.
Local tools and Studio
Whalory’s local tools work on your device and inside your chosen assistant. They do not send us your drafts or profiles. Your assistant’s own data practices are governed by its provider.
The website keeps your reduced-motion preference and data you choose to save locally in your browser. Browser data is not linked to your purchase account. Any separately enabled online capability must identify its connection and your choice before sending text; local work does not depend on it.
Purchases
For delivery, we keep your name, email or mobile number, selected edition, purchase time and amount, order number, payment reference, and payment status. If the gateway returns a masked card number, that limited value is kept for payment follow-up. Whalory never receives your full card number, bank password, or security code.
License keys are not stored as readable text in the database. We keep a hash, the last four characters, and an encrypted copy for delivery and recovery. The payment result page shows the key after payment is verified. Its essential whalory_reveal cookie lets that same browser see it again for half an hour; the cookie never contains the key.
For domestic checkout, Zibal receives the amount, order number, callback address, and mobile number if supplied. Enter bank card details only on the bank payment page. Application records use a hash of the connection address for abuse prevention. Hosting infrastructure may keep technical request logs for security and troubleshooting.
Support and waitlists
The support form records your name, contact, optional order number, and message. These details are private and used to answer and follow up your request. Do not include license keys, passwords, bank card details, or confidential client text.
Joining a waitlist stores your email and chosen topic for that request. Its removal link deletes the signup. Your contact is not used to advertise another topic.
Retention and requests
License and purchase records remain for as long as needed to provide access to purchased versions, handle financial matters, or meet legal obligations. Support messages are kept for no more than 12 months after the request is closed. Data is not sold or shared for advertising.
Use support to request access, correction, or deletion. We verify account or order ownership before acting. If a record must remain for a legal obligation or dispute, we explain why. Deleting data needed for license recovery can prevent future access to your purchase; we discuss that consequence before deleting it.
Hub and analytics
Hub statistics and weekly packet submissions are disabled. Local tools do not require them. Ordinary page visits use no advertising trackers.
Read support replies on the support page using your private tracking code. Keep that code; replies are not automatically emailed.
Terms of use
Terms for using this website and for buying.
Read the text
Terms version: 2026-10-04, effective October 4, 2026.
Seller and contact
Whalory is made and sold by the Whalya studio through this website. Use the private support form for purchase help, installation issues, or refund requests. Do not post license keys or personal purchase details in public reports.
What you buy
- Pro: Whalory files for one person, with 12 months of updates and support for installation and product errors.
- Studio: the same collection for up to 5 people in one organization, with 12 months of updates and support.
- Pro renewal: another 12 months of updates and support on the same key, starting when the current period ends, or on the renewal date if it has already ended.
- Core: free, with text under CC BY 4.0 and scripts under MIT.
International checkout
English pages show prices in US dollars. International checkout is unavailable: no payment, preorder, or deposit is collected here. You may join its waitlist. Buyers with an Iranian bank card can use the Persian checkout, which has its own currency and Persian purchase terms.
The amount shown at checkout is the total charged by Whalory. There is no automatic renewal or recurring charge. Orders are confirmed only after the server verifies payment with the payment gateway.
Delivery and continued use
Once payment is confirmed, the result page shows the order number, payment reference, license key, and download links. Keep the key; the account page provides fresh download links. Contact support with the order number if delivery is incomplete.
Versions received during the purchase period remain usable after it ends, for the same number of people. New versions and continued support require renewal. Your outputs are yours, including commercial use. See the license agreement for the paid files themselves.
Refunds, privacy, and responsibility
You may request a full refund within 7 calendar days of purchase; see refunds. Our privacy policy explains how purchase details and support messages are handled.
Whalory does not include an AI account or subscription. Your chosen assistant has separate costs. Check facts and claims before publishing the text you create.
The terms accepted at checkout are recorded with that order. Later changes do not apply retroactively. Mandatory consumer rights and access to the competent forum under applicable law remain intact. Contact support first with any dispute or question.
Refunds
Request a full refund within seven calendar days; downloading files does not remove this right.
Read the text
Terms version: 2026-10-04, effective October 4, 2026.
When to request a refund
You may request a full refund within 7 calendar days of buying Pro, Studio, or a renewal. Downloading or installing the files does not remove this right. You do not have to give a reason for changing your mind.
How to request one
Use the private support form. Give the order number and the email or mobile number used at checkout so we can verify the purchase and payer. Do not send your license key, bank password, or full card number.
After the request and purchase details are confirmed, the refund is processed within 7 working days and returned only to the original payer. Use support to follow its status.
What happens to the license
- Refunding Pro or Studio revokes that purchase’s license. Stop using and delete the paid files received under that purchase.
- Refunding a renewal removes only the added period; rights from earlier purchases remain.
- Text you wrote remains yours. Free Core remains available under its open licenses.
An unconfirmed payment
If your bank account was debited but the payment was not confirmed, keep the bank receipt and order number. Ask the bank or payment provider to check the transaction, and contact support. The return time depends on the bank and transaction review. No license is issued without verified payment.
This policy does not restrict mandatory rights under applicable law. International checkout remains unavailable and collects no payments.
Read support replies on the support page using your private tracking code. Keep that code; replies are not automatically emailed.
Inactive service
Hub privacy notice
What the Hub downloads, sends, keeps, and deletes, and how to turn each part off. Statistics and weekly packets stay off unless you turn them on.
Hub statistics and weekly packet submissions are disabled. This notice describes those optional services; it does not enable them or authorize sending your data.
Read the text
Summary
- Rule updates (on by default). Once a day Whalory downloads signed rule files, the way any program checks for updates. It adds no identifier, but like any download the servers see your IP address and can tell that Whalory was used that day. You can turn this off.
- Weekly statistics (off unless you turn them on). They are offered only to paid editions, which will be sold first in Iran, and only a person typing in their own terminal can turn them on. Then Whalory sends one small report a week: which checks fired, whether you changed wording that a hidden check flagged, rounded word counts, how much you edited drafts, how many revisions you asked for, and version numbers. Your text is never sent.
- Measuring fairly. While statistics are on, Whalory hides about 1 in 10 of its checks from you each week and counts whether you changed that wording yourself.
- Licence proof. Once a week a paid edition proves to our shop that it holds a licence, without sending the key. The shop signs your weekly ticket without seeing it, so our records cannot link the ticket to your report.
- Phrase sharing is a second, separate choice. It sends only numbers of entries from a public list of common phrases.
- Weekly packets you post yourself (global lane). Any edition, anywhere, can instead keep the same kind of counts on your computer and show them to you each week as a packet. Whalory sends nothing: you decide whether to post a packet on GitHub under your own account. Nothing from this option reaches our server in Iran.
- Storage. Reports are stored in Iran and deleted within 22 days after the week ends. We keep only totals that cover at least 10 people (20 for phrases), with a little random noise added.
- Your choice. Saying No changes nothing in how Whalory works. You can stop at any time with
hub_client.py off, which also asks our server to delete your reports.
1. Who we are
Whalory is made by the Whalya studio. The controller is [owner's full legal name or company name], [postal address], Iran. Data-protection contact, which is also the contact person (encarregado) under Brazil's LGPD: [privacy email to be confirmed]. [EU representative: to be decided. UK representative: to be decided.]
This notice covers Whalory Hub, the rule-update and statistics feature inside the Whalory skill, its MCP server and its plugins. It applies to the free Core edition and to the paid Pro and Studio editions; statistics are offered only to the paid editions. Purchases, licences and the website are covered by the Whalory website privacy notice.
2. What stays on your device
Whalory checks your copy on your own computer. Your drafts, final texts, file names, folders, prompts and voice profiles stay there. The linters and the MCP server never connect to the internet.
If you turn on weekly statistics, Whalory keeps a small log of counts on your computer (for example "rule dash flagged 2 findings in a short text"). It never writes your text into that log; with phrase sharing on, it records only the numbers of listed phrases. You can read the log at any time with hub_client.py log --events. The log for a week is deleted as soon as that week's report is built, and any log older than 14 days is deleted.
While statistics are on, the MCP server keeps the last few texts it checked in memory, for at most 6 hours, so that the final check can compare the draft you saw with the text you approved. They are never written to disk and disappear when the server stops.
3. Rule updates (on by default)
What happens. At most once a day, when your assistant starts a session, Whalory downloads public files that contain signed rule updates. It checks the digital signature of every file before using it.
Where from. GitHub Pages and GitHub Releases, run by GitHub, Inc. in the United States, and our mirror at hub.whalory.com, on a server we rent in Iran from Hostiran [legal name to be confirmed].
What those servers receive. The request for a public file, your IP address (as with any download), the time, and a generic program name (whalory-hub/1). From this they can tell that Whalory was used that day. Whalory adds no identifier, version or usage data, and it never sends back a tag that a server gave it earlier, so a server cannot recognise your installation. Our server writes no access log for hub.whalory.com, and our own code does not store IP addresses. Hostiran and its data centre may keep network traffic records that include your IP address for [period confirmed by the host], as Iranian law may require. GitHub handles its server data under its own privacy statement.
Why. So that the product you installed keeps getting better.
Turn it off. hub_client.py off updates, or set WHALORY_HUB_UPDATES=0, or turn off "Download signed rule updates" in your plugin settings where available. Whalory then uses the rules that came with your installed version. On Codex, Whalory stays offline unless you have allowed network access for Codex's sandbox.
4. Weekly statistics (off unless you turn them on)
4.1 How it is turned on
Only you can turn it on, by answering Yes on the consent screen in your own terminal and typing a short code. A setting in a plugin, a project file or your employer's managed settings can ask for statistics, but nothing is collected until you confirm in the terminal. Your AI assistant cannot turn it on. The first report is sent at least 3 days after you say Yes.
4.2 What a report contains
- The week (for example
2026-W40), the notice version you agreed to, and which options you chose. - The Whalory version (major and minor), a Python version range (for example "3.10 to 3.11"), and the rule-update versions in use.
- For each Whalory rule or listed phrase that fired that week, per language and broad kind of content (short, long or interface text): how many times it fired, and how often flagged wording was still in the text you approved. Counts are capped (at most 10 outcomes per rule per week).
- For the checks that were hidden from you that week (section 4.4): how often they flagged something in a sentence you rewrote, and how often that wording was gone after your edit. For comparison, the same count for a few randomly chosen word pairs in those sentences.
- Totals of words checked and approved, rounded down to a multiple of 50.
- For writing procedures (playbooks): how many drafts you approved on the first try, how much you edited, how many revisions you asked for, and how many errors were left.
- Health counters of the update system (for example "self-test passed").
- A scrambled form (hash) of a deletion code that only your computer knows.
4.3 What a report never contains
- Your text, or any sentence or phrase from it.
- Your prompts, file names, paths or project names.
- Your name, email or licence key.
- Which AI program you use.
- Your country, language settings or time of day.
- Any lasting identifier of your device or installation.
4.4 Hidden checks (measurement holdout)
To learn whether a check helps, Whalory needs cases where neither you nor your AI assistant saw its warning. So, while statistics are on, each week Whalory hides about 1 in 10 of its ordinary checks (1 in 20 of its error checks) on your computer. Which checks are hidden changes every week. Checks that protect correctness, such as channel limits and Persian character rules, are never hidden. Installations that do not share statistics never hide anything.
4.5 How reports are counted without knowing who you are
Each report carries a weekly ticket that proves it comes from a paid licence.
- Once a week, at a random time, your computer proves to our shop at
whalory.comthat it holds a paid licence. It sends a one-time code made from your licence key, never the key itself. The shop checks that the licence is active and at least 30 days old, and that no ticket has been issued that week to the same purchase (licences bought with the same bank card, email or phone number count as one). - The shop signs your ticket without seeing it ("blind signature"). It therefore cannot recognise the ticket later, and our records cannot link your report to your licence.
- The shop keeps, for 22 days after each week, a record of which purchase received a ticket that week, and then deletes it.
- Your computer sends the report at least 24 hours after it got the ticket, in a separate connection, so the two are harder to match.
What remains: someone with access to network records of both connections (for example our hosting provider or its data centre, or an authority using those records) might still match them by IP address.
4.6 When
Once a week, at a random time within 48 hours after the week ends (Monday 00:00 UTC). If you are offline, your computer tries again later, for up to 21 days.
5. Phrase sharing (a second, separate choice; off by default)
This option exists only if weekly statistics are on, and only after we announce it in a signed update.
Whalory ships a fixed, public list of common phrases of 1 to 4 words. The list is built from public texts and AI drafts, and it contains no names, no rare words and no words about sensitive topics (religion, ethnicity, health, sex life, sexual orientation, political opinion, trade union membership, crime). When you delete one of these listed phrases from a draft on at least two different days, Whalory can count it. Each week it may send up to 20 list numbers, each with the number of your sessions in which you deleted or kept it (capped at 5) and the broad kind of content. Nothing outside the list is ever sent.
If you pick "show me first", each week's list waits until you approve or remove rows with hub_client.py preview, which shows each phrase.
A phrase is used only if at least 20 different licensed people deleted it, in at least two kinds of content, over at least three weeks, and a random test step is passed as well. Only such a phrase may become a public rule. All other phrase counts are deleted with the raw reports.
6. Weekly packets you post yourself (global lane; off by default)
This option lets anyone, anywhere, help make Whalory's checks more accurate without sending anything to our server in Iran. It is offered to every edition, including the free Core edition, once we announce it in a signed update.
Turning it on. Only you can, in your own terminal (hub_client.py on packets), by answering Yes and typing a short code, as for weekly statistics. An installation uses either this option or weekly statistics, never both.
On your computer. Whalory keeps the same small log of counts as in section 2. It also hides about 1 in 10 of its checks each week, as in section 4.4. At the end of each week it turns the log into a packet and deletes the log.
The packet. hub_client.py packet (or /whalory:feedback in Claude Code) shows you the packet in full, with a link to that week's pinned issue in our public GitHub repository whalory-hub. It holds the same kinds of counts as a weekly report (section 4.2), without the weekly ticket, the deletion code or phrase data. It never holds your text, phrases, file names or licence details.
Posting is up to you, and public. If you want, you paste the packet as a comment under your own GitHub account, or run gh issue comment yourself. Whalory never posts it and never runs that command. Anyone can read your comment, and GitHub's terms and privacy statement apply to it.
What we do with it. A scheduled job in that repository reads the week's comments and checks every packet strictly. It counts only one packet per GitHub account per week, only from accounts at least 90 days old, and hides the comments it counted. It adds the packets up in memory without copying any comment, user name or account number anywhere. Only totals that cover at least 10 accounts are kept, with a little random noise added. They feed the same public rule changes as weekly statistics. Totals from packets can make a check milder or quieter. On their own they never make an existing check stricter, although they can help decide whether a newly listed stock phrase starts to show a warning.
Deleting. You can delete your comment at any time. If you delete it before the week's final count, 21 days after the week ends, it is left out. After that only the totals remain, and they cannot be traced back to you. Turning the option off (hub_client.py off packets) deletes the log and the packets on your computer, but not comments you posted; delete those on GitHub.
7. Why we use this data
- Making Whalory's rules more accurate. That means raising or lowering how strongly a rule warns and adjusting thresholds such as sentence length. It also means retiring phrases that cause false alarms and adding new stock phrases.
- Spotting a broken update early and rolling it back automatically.
- Preventing abuse of our servers.
We do not sell data, show ads, build profiles of people, or make decisions about you. We do not combine the contents of your reports with purchase records.
8. Legal bases
| Region | Weekly statistics and phrase sharing | Rule updates | Abuse prevention |
|---|---|---|---|
| Iran | Consent for the purposes described here (E-Commerce Law Art. 59) | [counsel to confirm] | [counsel to confirm] |
| EU/EEA | Your consent (GDPR Art. 6(1)(a); ePrivacy Directive Art. 5(3)) | [Legitimate interest in delivering and securing the installed product; counsel to confirm] | Legitimate interest in network security (GDPR Recital 49) |
| United Kingdom | Your consent (UK GDPR Art. 6(1)(a); the Privacy and Electronic Communications Regulations) | [as above; counsel to confirm] | Legitimate interest |
| Brazil | Consent (LGPD Art. 7 I) | [counsel to confirm] | Legitimate interest (Art. 7 IX) |
| India | Consent (DPDP Act s.6) | [counsel to confirm] | [counsel to confirm] |
| Elsewhere | Consent | Delivery of the product | Security |
Weekly packets (section 6) rest on your consent in your terminal and on your own decision to post [counsel to confirm the basis for reading posted packets, in each region].
9. Where the data is stored, and what that means
Reports are received and stored on our server in Iran, a virtual server we rent from Hostiran [legal name and data-centre city to be confirmed]. Packets you post yourself (section 6) never reach it. For reports, storage in Iran means:
- The European Commission has not found that Iran ensures an adequate level of data protection.
- Under Iran's Computer Crimes Law, Articles 32 to 34, internet access and hosting providers must keep certain records for set periods. They must also preserve or hand over data when a court orders it. That can include logs kept by our hosting provider and its data centre. We reduce this risk by storing as little as possible: our code stores no IP addresses and no text, reports cannot be linked to a licence in our records, and raw reports are kept only for a short time.
- Iran does not yet have a general personal data protection law in force. The E-Commerce Law requires consent for specified purposes and forbids processing data that reveals ethnicity, religion, health or sex life without explicit consent. We do not collect such data, and our lists exclude phrases on those topics.
- Anonymous totals are published on GitHub (United States) and on our website, only after the raw reports are deleted.
- Do not turn on statistics if you are in the United States, or are a U.S. citizen or permanent resident. [If no data-processing contract with the host is signed: This option is not offered to residents of the EU, the EEA or the UK.]
10. Who receives the data
| Recipient | Role | What |
|---|---|---|
| Hostiran [legal name to be confirmed] (Iran) | Rents us the server that runs our shop and the Hub (processor) | Stores the reports on our behalf; may keep network traffic records with IP addresses for [period], as Iranian law may require |
Our shop at whalory.com (the same controller) | Checks your licence for statistics | Sees which licence asked for a weekly ticket, never the ticket itself or your report |
| GitHub, Inc. (US) | Hosts update files, anonymous totals and the public packets issue | Sees your IP address when you download updates. Receives from us only totals released after the raw reports are deleted. Publishes any packet you post, under your account and its own terms |
| The public | Anonymous totals and rule changes in our public changelog, never counts from fewer than 10 people; every new hidden phrase is listed on the day it ships. Also the packets that people post themselves |
Nobody else. We would disclose data to an authority only where the law requires it (see section 9).
11. How long we keep it
| Data | Kept |
|---|---|
| Local event log (your computer) | Until the week's report is built; at most 14 days |
| Weekly ticket and unsent report (your computer) | Until sent, or 21 days after the week |
| Copy of sent reports and deletion codes (your computer) | 5 weeks |
| Texts in the MCP server's memory while statistics are on | At most 6 hours; never on disk |
| Weekly packets (your computer) | 5 weeks |
| A packet you post (GitHub) | Until you delete your comment; left out of our count if you delete it before the week's final count, 21 days after the week |
| Record of which purchase received a weekly ticket, and that week's signing keys (shop) | 22 days after the week |
| Raw reports, ticket numbers and deletion-code hashes (Hub server) | At most 22 days after the week: the final count runs 21 days after the week, and deletion follows within 24 hours |
| Rate-limit data derived from IP addresses (Hub server) | In memory only, at most 24 hours; never written to disk |
| Our application logs | 7 days, without IP addresses or report content |
| Our hosting provider's own logs | [period confirmed in writing by the host], as set by the provider and Iranian law |
| Totals covering at least 10 people (20 for phrases), released after the raw reports are deleted | Indefinitely; they are anonymous |
| Totals from posted packets, covering at least 10 accounts | Indefinitely; they are anonymous |
| Backups | Contain only anonymous totals; rotated within 30 days |
12. Your choices and rights
- Sharing statistics is optional. Whalory works the same if you say No.
- Turn it off:
hub_client.py off(weekly statistics and phrases),hub_client.py off phrases,hub_client.py off packets, orhub_client.py off updates. In Claude Code you can also set the plugin setting tooff. Turning off works immediately, even offline. - Delete:
hub_client.py offandhub_client.py forgetdelete everything on your computer and ask our server to delete each report still held, using the deletion code only your computer has. - Before uninstalling, run
hub_client.py forget. Uninstalling alone does not delete the Hub folder on your computer or send deletion requests. - See what was sent:
hub_client.py log --sentshows every report exactly as sent. - Your rights. Depending on where you live, you may have rights to access, correction, deletion, restriction, objection and data portability. You may withdraw consent at any time; earlier processing stays lawful. Our server does not know who you are, so we usually cannot find your reports from your name or email (GDPR Article 11). Your computer holds the receipts and deletion codes that identify them, and the commands above use them. Write to [privacy email to be confirmed] for anything else.
- Complaints. You can complain to your data protection authority. In the EU that is the authority of your country; in the UK, the Information Commissioner's Office; in Brazil, the National Data Protection Authority (ANPD); in India, the Data Protection Board.
We ask for your consent again after 24 months, and when you install a new major version of Whalory. We also ask again if we change any of these: what a report contains, why we use it, who receives it, where it is stored, how long we keep it, how many checks are hidden, or what our hosting provider logs. If a signed update names a different server or country, Whalory stops sending reports until you agree again.
13. Children
Whalory Hub statistics and weekly packets are only for people aged 18 or older. The Yes answer on each consent screen reads "Yes, and I am 18 or older". Please do not turn either on if you are younger.
14. Security
- Every update is signed, and your computer checks the signature before use and again before each use of stored rules; signing keys never sit on our Iranian server.
- All connections use HTTPS. Your licence key is never sent for Hub purposes.
- The shop and the Hub run on one server as separate services, each with its own system user, database and secrets. The Hub stores no licence data.
- Raw reports are deleted on a fixed schedule. Deleted rows are overwritten in our database files, and the database's temporary log file is emptied after each deletion. Disk snapshots of the Hub data are [disabled / kept for N days].
- Only the owner can use the administrative functions; opening collection and deleting data need the owner's digital signature, and every administrative action is logged.
15. Our commitment not to re-identify
We do not try to find out who sent a report, and we do not allow anyone who helps us to do so. Totals are published only when they cover at least 10 people (20 for phrases), after the raw reports are deleted, with a little random noise added, and rounded to the nearest 5.
16. Changes to this notice
We will publish every new version at this address with its date. If a change affects what we collect, why, where or for how long, Whalory stops sending reports until you agree again.
17. Contact
[Owner's full legal name], [postal address], [privacy email to be confirmed]. Security issues: [security email to be confirmed].
Questions about these texts
Use the private support form. Include your order number, but never your license key or card details. Private support