Terms, privacy and software licenses
Hosted-service policies are drafts pending operator details. Software licensing is effective independently.
Copyright and software rights
OpenChronology — exact rational timeline software Copyright (c) 2026 Athan Clark, an individual. OpenChronology first-party software, including the web interface deployed at timescale.info, desktop application, standalone HTML edition, server, official plugins, build scripts, and accompanying first-party documentation, is licensed under the GNU General Public License version 3 only (SPDX: GPL-3.0-only). You may redistribute and modify it under that license. See LICENSE for the full terms. It is provided WITHOUT ANY WARRANTY, including merchantability or fitness for a particular purpose, to the extent permitted by law. Third-party components retain their own copyrights and licenses. See THIRD_PARTY.md, bundled dependency notices, and vendor licenses. The independent rational-map, sqlite-rational, and rational-conformance projects and historical projects in the enclosing development workspace retain their existing licenses. Users retain ownership of their timelines, notes, images, and original plugin or formatter scripts. Exporting or hosting those materials does not automatically license them under the GPL. Domain registration and rights in the OpenChronology and timescale.info names are separate from the software license; no domain registration, endorsement, or trademark rights are granted by this notice. No nonprofit organization is represented as the copyright holder or operator.
Service terms (draft)
# timescale.info — terms of service Draft version: 2026-10-15. Not yet effective. Operator: Athan Clark, an individual. Contact and jurisdiction: pending operator confirmation; see LAUNCH.md. These terms cover the hosted service at timescale.info and desktop connections to that service. Independent installations have their own operators and policies. ## Accounts and use of the service When these terms become effective, creating an account or using authenticated hosting services constitutes agreement to these terms. Public visitors may read timelines without an account. Keep credentials and connected identity-provider accounts secure, provide truthful information, and report unauthorized access. An account is personal unless you are authorized to act for an organization. Accounts are for people aged 13 or older; the service does not offer accounts to children under 13 or parental-consent accounts. Sign-up asks for your year of birth. Anyone may read public timelines without an account. This eligibility rule does not restrict rights under the software license or use of a separate offline installation. ## Young people Accounts of people who may be under 18 (by the year of birth they gave) get the most protective settings, which they cannot turn off: - warnings before sensitive content (below) always show, and its images stay blurred until chosen; - the timelines they star are not shown on their profile; - browsing leaves out labelled timelines. Timelines start private for everyone. The service has no private messages, no contact between people outside public pull-request discussions, no location features, no advertising and no profiling for advertising. A parent or guardian who believes their child under 13 has an account, or who has a concern about a teenager's account, can contact the operator; the account can be closed and its data deleted. If you are young and something here upsets or worries you, use **Report** or tell an adult you trust. ## Your data and collaborators You retain ownership of your timelines, moment metadata, images, comments, and original plugin and time-formatting scripts. You must have the rights needed to upload, link, copy, and share those materials. Images are shown by linking to where their owners host them; the service stores the links, not copies. Link only images you may share, and respect any limits their hosts set. Do not upload passwords, sensitive secrets, or other people's private information without authorization. The service is not designed for regulated confidential records or safety-critical decisions. You grant Athan Clark a nonexclusive, worldwide, royalty-free permission to store, process, reproduce, back up, transmit, and display your submitted content solely to operate, secure, and provide the service and the sharing you request. You grant authorized recipients permission to view, execute attached restricted scripts, and export content, and to fork and prepare change recommendations where forking is enabled, through the functions and access you enable. This is not an ownership transfer, an advertising license, or permission to sell your content. This permission ends when content is deleted, subject to necessary backup removal, legal preservation, and recipients' previously obtained copies. Timelines start private. Public timelines are readable, searchable, and exportable by anyone. Public visibility does not automatically make your content GPL-licensed, public domain, or freely reusable for every purpose. Specify a content license if you want broader reuse rights. Making a timeline private later cannot retract copies already downloaded. Sharing a private export is your own sharing decision. Signed-in users can fork public timelines into independently owned copies. Private forking requires the owner's authorization; those platform copies remain private. Forks retain their own collaborators and survive upstream deletion. Saving records immutable checkpoints; submitted reviews pin a saved snapshot rather than following later edits automatically. A fork does not transfer ownership of the original or grant unlimited reuse rights beyond these service features and a stated content license. The owner controls visibility, membership, and timeline deletion. A viewer can read; a contributor can propose changes; a writer can update the upstream version, merge recommendations, and close or reject them. Signed-in readers of public timelines can propose changes. Recommendations retain proposed and base snapshots and discussion until the timeline is deleted. Submitting a recommendation grants the owner permission to incorporate and share the proposed changes under the timeline's stated content license, if any; do not submit material with incompatible rights. Contributors retain their copyright. Permission to collaborate is not permission to impersonate the owner or change ownership. ## Plugins, scripts, and the library Official OpenChronology plugins are part of the GPLv3 software. Original custom scripts remain their author's property, subject to any applicable derivative-work requirements and licenses on incorporated code. Installing a plugin stores its definition in the timeline; exporting a timeline includes that definition. Removing a library listing cannot retract installed or exported copies. Publishing to the plugin library grants service users permission to download, install, execute, and include that version in timelines and their exports. Include your own license notice for additional modification or redistribution rights. This functional permission does not waive other copyright rights. Do not publish code you lack permission to distribute. Library availability or an official-looking name is not an endorsement; official plugins are identified separately. Restricted execution reduces available capabilities but cannot guarantee defect-free output. ## Acceptable use and moderation The service is for knowledge: history, science, education, journalism, art and records. Educational, historical, medical, artistic and news depictions of nudity, violence and disturbing events are allowed, but must be labelled as sensitive content (nudity, graphic violence, disturbing content) on the timeline, moment or duration that contains them. Readers are then warned before it opens and its images are blurred until they choose to see them. Not allowed at all: pornography or other sexually explicit material made to arouse; gore or cruelty shown for its own sake; and any sexual content involving minors, which is removed, preserved as the law requires and reported to the authorities. Do not use hosted services for illegal content, infringement, harassment, threats, fraud, doxxing, malware, attempts to escape script restrictions, access-control bypass, credential theft, or deliberate disruption. Respect technical rate and size limits. Report suspected security defects privately using the published contact; do not access other users' data or disrupt the service while investigating. ## How content is moderated Anyone, with or without an account, can report a timeline, moment, duration, comment, published plugin or suite, or account they can see, choosing what is wrong (child sexual abuse or exploitation, other illegal content, sexually explicit content, graphic violence, promoting suicide or self-harm, harassment or private information, spam, copyright infringement, or something else). The owner is not told who reported. Reports of child abuse and other illegal content are reviewed first. People, not automated systems, review reports and decide. The operator and the site's administrators may: - dismiss a report; - add a sensitive-content label, which the owner cannot remove; - restrict content, so only its owner (and administrators) can see it; - suspend an account; for violations of these terms, security incidents, or legal obligations. Apparent child sexual abuse material is restricted at once, preserved as the law requires and reported to the authorities (in the US, to NCMEC). Immediate action may be necessary; unlawful or harmful material need not remain available. Where practicable, the operator will provide an opportunity to export lawful data. This discretion does not transfer ownership of user data. Copyright complaints and repeat infringement are handled under COPYRIGHT.md. The service uses no automated content detection. Two automatic measures shape what appears, not whether it is allowed: browsing ranks public timelines with an account standing (from account age, email confirmation, two-factor authentication, stars and forks received, and moderation decisions), leaving out new accounts' timelines until they are established; and signing up, sending email, reporting, publishing plugins, repeated failed sign-ins and new accounts' contributions to others' timelines may ask for a human-verification challenge. Search ranks by relevance to what you typed. ## Complaints - **About content:** use **Report** on it. - **About a decision on your content or account:** you are told what was decided and why, by notice in your account and by email, and can ask once from Account for it to be reviewed by someone. A suspended account asks by contacting the operator. Signed-in reporters with a confirmed email are told the outcome of their report. - **About anything else:** contact the operator, for example about how a report was handled, about the service not meeting these terms or its legal duties, or about being wrongly treated as under 18. Complaints are answered as soon as practicable and are not used against the person who makes them. Where you live may also give you the right to complain to a regulator or a court, or (in the EU) to an out-of-court dispute settlement body. ## Availability, departure, and liability Keep independent exports. Local edits do not publish automatically: saving to the server changes the timeline or proposal you explicitly select. The service may change or be interrupted and does not promise perpetual hosting, particular storage capacity, recovery of every version, or a service-level guarantee. You can delete, through the interface, the timelines you own, your comments, and your account (Account → Delete your account), which deletes what it owns and wrote, as PRIVACY.md describes. Other data requests go to the operator; see PRIVACY.md. To the extent permitted by applicable law, the service is provided as available, without promises of uninterrupted availability or fitness for a particular purpose. The operator is not liable for indirect or consequential losses to that extent. These terms do not exclude liability that cannot lawfully be excluded, including mandatory consumer rights, nor limit remedies for intentional wrongdoing where prohibited. The software's separate warranty terms are in the GPLv3 license. ## Software rights, identity, and changes OpenChronology software is copyright 2026 Athan Clark and licensed GPL-3.0-only. These hosted-service terms do not restrict copying, modification, redistribution, self-hosting, or commercial use permitted by that license. Names and domain rights are distinct; forks may accurately acknowledge their origin but must not suggest they are the official timescale.info service without authorization. No nonprofit currently operates the service. A future operator or copyright assignment will be disclosed; it is not assumed by these terms. Material service policy changes will receive prospective notice before taking effect, except when immediate changes are necessary for law or security. Archived policy versions should remain available. No arbitration clause or exclusive forum is imposed by this draft; governing-law details await operator confirmation, and mandatory rights under applicable law remain available.
Privacy notice (draft)
# timescale.info — privacy notice Draft version: 2026-10-15. Not yet effective. Responsible operator: Athan Clark, an individual. Public privacy contact, hosting providers, hosting region, and backup/log retention schedules are pending confirmation; see LAUNCH.md. ## Information and purposes The hosted service stores account usernames and identifiers, salted password hashes when password login is used, verified email addresses, encrypted authenticator secrets, hashed single-use recovery codes, confirmation/reset proofs, encrypted transactional email jobs, linked identity-provider names and subject identifiers, session records, and authorization-flow records. Password hashes are not plaintext passwords. Google, GitHub, or Facebook sign-in contacts the provider you choose; the provider can observe that authentication. The application uses provider credentials server-side and does not give provider tokens to timeline plugins. Provider privacy notices also apply to their own services. Resend processes recipient addresses and account verification, recovery, and security notification email content for delivery. The server checks new passwords against Have I Been Pwned using only a five-character hash prefix and padded responses; it never sends a plaintext password or complete password hash to that service. These services can observe the sending server's network address. Confirmation proofs expire in 24 hours, reset proofs in 30 minutes, and pending MFA challenges in five minutes. Temporary records are cleaned by the delivery worker. Authenticator secrets and recovery-code hashes remain until replaced, disabled, or account removal. The database stores the timelines you explicitly save: exact rational times, titles, notes, tags, metadata, formatting scripts, plugin definitions, and links to images (not copies of them). It also stores visibility, collaborator permissions, saved revision documents, fork relationships and ancestry, proposed and base snapshots, and discussion comments with account attribution. These support editing, search, sharing, collaboration, and export. Private timelines are excluded from the public browser and public full-text search. Site administrators can access and manage private timelines; they are not encrypted from the operator. Account profiles may contain an avatar image or HTTPS image URL. Remote avatar hosts receive browser requests. Scoped API credentials are stored as hashes with names, prefixes, permissions, expiry, revocation, and last-used timestamps. The service also records per-user logical storage usage, quota exemptions, suspension status, administrator privileges, and an audit trail of administration actions. Secrets, passwords, and MFA codes are excluded from that audit trail. Sign-up asks for your year of birth, to confirm you are old enough for an account and to keep warnings before sensitive content on for accounts of people who may be under 18; only the year is stored, with your choice of whether to see sensitive content without warnings. A sign-up refused for its age is answered neutrally, and a hash of that browser's sign-in token is kept for one day so that another answer from it is refused too; nothing else about the refused sign-up is kept. The service computes an account standing (from account age, confirmation, two-factor authentication, stars and forks received, and moderation decisions) to rank public timelines; only administrators see it. Reports record what was reported, the category and any details you give, and your account if you were signed in; the owner of what you report is not told who reported it. Moderation decisions keep their reason, who decided, any review request and its outcome, as a record. Reports and decisions are kept while needed to moderate and as required by law. IP addresses are processed for connection handling and abuse prevention; temporary authentication rate-limit keys are hashed. Hosting providers and reverse proxies may generate request and security logs. The deployment must document their actual fields, recipients, and retention before this notice becomes effective. Support, privacy, and abuse reports may contain the information you provide and are used to respond and investigate. If the operator turns on Cloudflare Turnstile for human-verification challenges (instead of the built-in proof of work), your browser loads Cloudflare's challenge when one is asked for, and Cloudflare receives network and device information to tell people from automated traffic, under its own privacy policy. The application includes no advertising or analytics integration; a deployment adding either must update this notice and meet applicable consent requirements before doing so. ## Local storage, cookies, and offline editions Browser session cookies authenticate requests; anti-forgery and short-lived authorization-flow values secure login. Server sessions have a 14-day absolute expiry and become invalid after one day of inactivity. Users can revoke sessions. The browser keeps editing drafts and authentication-return state in local storage facilities. Clearing site storage removes local drafts and can sign you out. The application does not include advertising cookies or cross-site tracking code. If the operator enables Google Analytics, the site first asks whether you allow analytics cookies. Only if you accept does your browser load Google's script, which sets Google Analytics cookies and sends Google the pages you visit, with network and device information. Google signals and ad personalization are turned off, and timeline content is never sent. Your choice is kept in your browser; "Analytics settings" in the footer changes it. The standalone HTML edition processes timelines on your device and blocks network connections. It includes embedded assets and legal notices. It cannot use the online catalogue or missing external images. The desktop edition stores local .och SQLite files and can connect to the server you select; connecting and saving to a server share data with that operator. A local file is not automatically uploaded. Exported .och and .ochx files are not encrypted by the application and include timeline scripts and embedded assets. Access and account credentials are not exported as timeline settings. Your browser, operating system, backups, and chosen storage locations have their own data practices. ## Who can receive data Public timeline content and its discussions are available to anyone and can be downloaded and indexed outside the service. Private content is available to the people the owner authorizes. Operators and necessary hosting/database providers can access stored data for service operation; this is not end-to-end encryption. The operator does not receive ownership of that content. Provider services process authentication requests when selected. Information may be disclosed when required by law or necessary to respond to security abuse or protect legal rights, subject to applicable law and appropriate limits. Moment image URLs can request images from third-party HTTPS hosts in connected editions. Those hosts see network information, including an IP address and requested URL; image requests omit browser credentials and referrers. Opening an original image source visits that site under its own policies. The server stores image links, not copies; exports to your own files may embed a browser-created image copy if the host allows it. Plugin scripts run through a restricted interpreter without direct network, DOM, or import access; host-rendered image fields can still cause these image requests. Published plugin definitions are public independently of private timelines using them. ## Retention and choices Saved timelines remain until the owner deletes them or operator-assisted removal is required. Deleting a timeline removes its live events, recommendations, and comments through database cascades, together with unreferenced history belonging to that timeline. Independently owned forks and submitted snapshots on other timelines remain; ancestry needed by those forks and reviews is retained. A public review exposes its submitted snapshot, not the source fork's other private history. Revoking upstream access stops future reads and synchronization but does not erase copies already made. Do not assume closing a recommendation deletes its snapshots or comments. You can delete your own comments at any time, from the pull request they are on. You can delete your account from Account → Delete your account, confirming with your username, your password and, if two-factor authentication is on, a code. Deleting it deletes at once the timelines you own (as deleting each would), the pull requests and comments you wrote on other timelines, your published plugins and suites, stars, memberships, API keys, sign-in methods, sessions and security records. Kept: changes already merged into other people's timelines, which are part of their history (it names an account that no longer exists), others' forks of your timelines, and moderation records, which no longer name you. The last administrator of an installation cannot delete their account. Other requests, such as about content of yours elsewhere, go to the privacy contact. Expired login flows and sessions are cleaned by authentication operations, rather than guaranteed immediate physical erasure at expiry. Backup deletion and log retention depend on the deployment and must be specified before public launch. Necessary legal holds may delay deletion with limited access. Recipient copies, search engines, and files you export are outside the operator's control. Export your timelines before deletion; keep local backups if needed. Depending on applicable law, you may request access, correction, deletion, restriction, portability, or object to processing and complain to a competent privacy regulator. The operator will verify requests without requiring unnecessary information and respond within applicable deadlines. Service delivery, security, and legal obligations are the purposes; where GDPR applies, the intended bases are contract necessity, legitimate interests in secure operation subject to balancing, and legal obligations, with consent for optional processing where required. Hosting locations, international-transfer mechanisms, and any required representatives must be confirmed before offering the service in jurisdictions requiring them. Accounts are for people aged 13 or older; the service does not knowingly offer accounts to children under 13. A sign-up giving a year of birth under 13 is refused, and an account created through a social sign-in that does so is closed before it can be used. Report suspected accounts of children under 13 to the operator so they can be investigated and addressed under applicable law. Accounts of people who may be under 18 get high-privacy settings by default that they cannot change: warnings before sensitive content always show, the timelines they star are not shown on their profile, and browsing leaves out labelled timelines. For everyone, timelines start private, profiles show only a username and an optional avatar, and the service collects no location, has no private messaging, and does no profiling for advertising. The year of birth is used only for these settings and the age requirement. This is not a claim that an age question alone satisfies children's privacy or online-safety laws. Material privacy changes must describe the new practices before they take effect; existing data must not be repurposed incompatibly without the necessary legal basis.
Copyright, abuse and security reports
# Copyright, abuse, and security reporting Draft version: 2026-10-15. Operator: Athan Clark, an individual. Public reporting email and, if used, designated-agent details are pending. This draft does not assert that a DMCA agent has been registered or that a safe harbor automatically applies. Anyone can report a timeline, moment, duration, comment, published plugin or suite, or account with **Report**, choosing "Copyright infringement" and describing the work and why its use is unauthorized; no account is needed. A formal notice, such as a US DMCA notice, goes to the operator contact once it is published, as described below. Images on timelines are links to where their owners host them, not copies stored by the service (docs/images.md). A complaint about a linked image can ask for the link to be removed from the timeline; removing the image itself is a matter for its host. For a copyright complaint, identify the copyrighted work, the specific timeline, plugin, comment, image, or URL at issue, your contact information, and why the use is unauthorized. For a US DMCA notice, also include an electronic or physical signature, a good-faith statement that the use is not authorized by the owner, agent, or law, and a statement of accuracy and authority under penalty of perjury. Do not include private account credentials. If you are uncertain whether the use is permitted, including by license or fair use, assess that before sending a claim. The operator should review complete reports promptly, restrict identified material when appropriate, and notify the affected user unless prohibited or unsafe. Report details may be shared with that user to allow a response; sensitive contact information should be limited to what the process requires. In-app reports are handled in the review queue (docs/moderation.md): restricted material becomes visible only to its owner, who is told why and can ask for a review. Repeat infringers' hosted accounts are suspended in appropriate circumstances: before deciding, the operator reviews the account's earlier restrictions for copyright, which the moderation records keep (`oc_moderation_cases`, `oc_reports`). Preserve a limited record of decisions and respect lawful preservation requirements. If US DMCA procedures apply, an affected user may provide a counter-notice with a signature, identification of the removed material and its former location, a statement under penalty of perjury of a good-faith belief that removal resulted from mistake or misidentification, their name/address/telephone number, consent to the relevant US federal court's jurisdiction, and acceptance of service from the complainant or agent. The operator must follow applicable notification and restoration procedures; restoration generally follows the statutory 10–14 business day period after a valid counter-notice unless notice of a qualifying court action is received. This procedure must be finalized with the actual designated agent. For other abuse, provide specific URLs and a factual description of the concern. For vulnerabilities, report privately with reproducible steps and minimal evidence. Do not publish secrets, exploit unrelated accounts, or interrupt the service. There is no promised bug bounty or blanket authorization for intrusive testing. Software licensing complaints should identify the distributed version and the missing license, source, or attribution. GPL rights remain available independently of any account moderation decision. Reference: https://www.copyright.gov/512/index.html and https://copyright.gov/dmca-directory/ describe US procedures and agent designation.
Operator details pending
# Operator publication checklist These policies are reviewable drafts, not assertions that timescale.info is already operating or that legal registrations have been completed. They intentionally avoid invented contact addresses, corporate status, hosting vendors, and jurisdiction. Copyright and GPL software licensing take effect independently of this draft status. Before making the hosted policies effective: - Supply Athan Clark's monitored support/privacy/abuse/security contact and required operator/business mailing information. A service address can avoid publishing a residential address where permitted. Confirm governing jurisdiction and applicable consumer/privacy rules; get legal review appropriate to the intended user regions. - Replace draft labels with an effective date and archive prior policy versions. Establish a notice/acceptance process for account creation, including social login; the current interface presents policies but does not record contractual acceptance. - Configure Resend with a verified sending domain, scoped API key, SPF/DKIM and appropriate DMARC. Back up the authentication encryption key separately, run the delivery worker, and test confirmation, recovery, and MFA end to end. - Confirm hosting/database/backup/email/log providers, locations, access controls, log fields and concrete retention/removal schedules. Document processors, international transfers, and representatives where required. Ensure contracts and actual configuration match the public privacy notice. - Establish identity verification, export, correction, complaint, appeal, breach-response, and legal-hold procedures. Deleting timelines, one's own comments and one's own account is self-service (PRIVACY.md); a copy of all of an account's data at once is not (each timeline exports separately), so access and portability requests need operator work. Do not promise self-service functions that do not exist. - Decide whether to use a US DMCA designated agent. If so, register and publish matching required contact details, track renewal deadlines, and establish the notice/counter-notice and repeat-infringer process before relying on safe harbor. Registration alone does not satisfy every condition. - Confirm the 13+ account policy, handling of suspected accounts of children under 13, and regional age requirements. Sign-up asks for a year of birth (self-declared): it is not age verification or parental consent, and accounts that may be under 18 always see sensitive-content warnings. Review this against the regions served (for example higher digital-consent ages under the GDPR in some EU countries). - US COPPA (the amended rule, in force since 22 April 2026): the service is for a general audience and refuses accounts under 13 through a neutral age screen (no hint of the age needed; a refused browser is refused again for a day). If the operator learns an account belongs to a child under 13, close it and delete its data. Keep a written information security program and a data retention policy anyway; the rule requires both of services it covers, and they are good practice for any. - UK Age Appropriate Design Code (Children's Code): write a data protection impact assessment covering under-18 users, and keep the high-privacy defaults for accounts that may be under 18 (TERMS.md, Young people). Review it with RISK-ASSESSMENT.md. - US state laws on minors and social media: about twenty states have them, many enjoined or in litigation, and their definitions of a social media platform vary. Check, for the states served, whether the service meets their definitions (most exclude services whose main purpose is not social interaction, or that are educational): for example Texas's SCOPE Act (HB 18), New York's SAFE for Kids Act (its rules on feeds for minors take effect 25 January 2027), and Utah, Louisiana, Texas and Alabama's app store accountability laws if the desktop app is distributed through an app store. - Australia's social media minimum age (under 16, since 10 December 2025): the service is likely outside it (its purpose is not social interaction, and educational services are excluded), but record the reasoning before offering accounts there. - Content policy (TERMS.md): no pornography or gratuitous gore; educational depictions allowed when labelled. Keep it that way to stay outside age-verification laws for pornography (US state laws, the UK Online Safety Act's pornography duties) and 18 U.S.C. 2257 record-keeping; allowing explicit material would require them. - Register as an electronic service provider with NCMEC's CyberTipline before launch, so apparent child sexual abuse material can be reported as 18 U.S.C. 2258A requires, and follow the procedure in docs/moderation.md (restrict, preserve for one year, report; never copy or forward the material). Name who reviews the report queue and how often; reports of child abuse and other illegal content are listed first. - UK Online Safety Act: complete and keep current the illegal-content risk assessment and the children's access and risk assessments (template: RISK-ASSESSMENT.md), and keep reporting and complaints working (Report, the review queue, review requests). The terms describe how users and children are protected, how moderation decides, and the complaints procedure (TERMS.md: Young people; How content is moderated; Complaints). - EU Digital Services Act: publish a single point of contact for authorities and users, keep notice-and-action (Report) and statements of reasons (the owner's notice and email) working, and publish the moderation policy (TERMS.md acceptable use). - Publish matching Corresponding Source alongside browser/desktop/container releases and preserve dependency copyright/license notices. See docs/licensing.md. - Check domain ownership and name conflicts; no registered trademark is asserted. A future nonprofit requires real formation and any intended copyright assignments, operator disclosure, and data-transfer review. This repository does not assign rights automatically to an entity that does not yet exist. Primary references used for this draft: - GNU GPLv3 and application guidance: https://www.gnu.org/licenses/gpl-3.0.html and https://www.gnu.org/licenses/gpl-howto.html - FTC privacy guidance: https://www.ftc.gov/business-guidance/privacy-security/consumer-privacy - FTC children's privacy guidance (including current COPPA changes): https://www.ftc.gov/business-guidance/resources/complying-coppa-frequently-asked-questions - US Copyright Office notice-and-takedown resources: https://www.copyright.gov/512/index.html and https://copyright.gov/dmca-directory/ These sources explain specific obligations; they do not establish that any one deployment satisfies every law. Have the finished policies reviewed after the operator, deployment, and intended markets are confirmed.
GNU General Public License version 3
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
<http://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
<http://www.gnu.org/philosophy/why-not-lgpl.html>.
Third-party attribution
# Third-party components - **rational-map / rational-ordered-map 0.1.0**, MIT. The vendored npm archive includes its license; source and commit are recorded in `vendor/versions.json`. It uses **fraction.js 5.3.4**, MIT. Installed package licenses are under `node_modules/`. - **sqlite-rational 0.1.0**, MIT. Source and license are in `vendor/sqlite-rational/`; source commit is recorded in `vendor/versions.json`. - **pgmp 1.0.6**, LGPL 3 (see upstream COPYING and source headers). The deployment image builds the exact public source commit `1849585416f2bc3d070bf8cef6a659907687ec7f`; upstream license: https://github.com/dvarrazzo/pgmp/blob/1849585416f2bc3d070bf8cef6a659907687ec7f/COPYING. - **GNU MP (GMP)**, LGPL 3 or later / GPL 2 or later. Desktop and PostgreSQL modules dynamically link system GMP; no GMP source or static GMP copy is bundled here. See `vendor/sqlite-rational/THIRD_PARTY.md` and your system package's notices/source provisions. - **SQLite**, public domain; linked from the system package in desktop and server-converter builds. - **reqwest 0.12.28**, MIT/Apache-2.0; native HTTPS transport, with **rustls** and **webpki-roots** as recorded in `src-tauri/Cargo.lock`. Their licenses remain in the crate packages. - **Tauri and its Rust dependencies**, MIT/Apache-2.0 and other licenses recorded in crate packages and `src-tauri/Cargo.lock`. **serde/serde_json**, MIT/Apache-2.0. - **Next.js 16.3.8**, MIT (Vercel); **React / React DOM 19.2.8**, MIT (Meta and contributors). Their original licenses are retained in installed packages and the standalone server distribution. The platform browser bundles retain dependency license notices. These packages are used only by the hosted platform, not the standalone HTML or Tauri editor. - **node-postgres**, MIT. **esbuild**, MIT. **TypeScript**, Apache-2.0. **Playwright**, Apache-2.0. JavaScript dependency versions are in `package-lock.json`. The Debian package includes this file, the application's GPLv3 license, the SQLite extension's license/notices, and the browser dependency license notices. System GMP, SQLite, GTK, and WebKit packages retain their own licenses.