Effective date: 5 July 2026 Version: draft-1 Operator: Craftolin ("Craftolin", "we", "us", "our") Principal place of business: Gopal Nagar, Malkajgiri, Hyderabad, Telangana 500047, India
⚠ DRAFT — NOT REVIEWED BY COUNSEL, NOT IN FORCE
This document has not been settled by a lawyer. The version is deliberately
draft-1rather than1.0so that no consent record written before legal review can be mistaken for one written after it.An Indian lawyer familiar with intermediary, consumer-protection and contract law must settle the wording before this is shown to real Makers. Open questions are at §5 below.
1. Purpose of this Document
1.1 This is a short declaration a Partner (referred to here, and in the applications, as a "Maker") must actively accept before they may accept a Requirement from a Customer.
1.2 It does not replace the Partner Agreement, which covers the same ground at greater length and continues to apply in full. Its purpose is different: the Partner Agreement is accepted once, at registration, among several documents; this is a short, plain-language confirmation given at the moment the Maker takes on an obligation to a specific Customer.
1.3 Craftolin does not require a Maker to hold GST registration, Udyam registration, company or LLP registration, a shop licence, or any other registration in order to create a profile or to accept a Requirement. Craftolin exists to give small independent makers an online presence they could not otherwise afford, and requiring such registrations would exclude the people it is for. Nothing in this declaration asks for any registration number.
2. The Declaration
The following text is presented to the Maker in the applications. It is served from the API so that every client displays identical wording, and the version above is recorded against the Maker's acceptance.
Before you can receive customer requirements, please confirm:
The details I have given — my name, business name, address, contact details and links — are true.
My product photos, descriptions and prices are accurate as far as I know.
I understand it is my responsibility to follow the laws that apply to what I make and sell, including any registrations, licences and taxes. Craftolin has not checked this and does not do it for me.
I understand Craftolin is a place to show my work and receive customer enquiries. Craftolin does not buy from me, does not sell my products, and does not take payment for them.
I understand the deal is between me and the customer — the price, the payment, making it, delivery, cancellation and refunds. Craftolin is not part of that.
☐ I confirm the above.
3. How Acceptance Is Taken and Recorded
3.1 Minimum reading time. The confirm control is disabled for 30 seconds after the declaration is displayed, with the remaining time shown to the Maker. This is a floor, not a ceiling: a Maker who wishes to take longer simply takes longer. The intention is that acceptance is informed rather than reflexive.
3.2 Active acceptance. The checkbox is unticked by default and must be ticked by the Maker. It is never pre-selected, and consent is never inferred from continuing to use the applications.
3.3 Record. Acceptance is written to consent_records with the purpose
maker_declaration, the document code 18_MAKER_DECLARATION, the version in
force at the time, the point of collection, the timestamp, and the IP address
and user agent of the request.
3.4 Versioning. Any amendment to the wording increases the version. A Maker whose recorded acceptance names a superseded version is asked to read and accept the current text again, and cannot accept a Requirement until they do. Consent to earlier wording is not treated as consent to later wording.
3.5 Enforcement. The requirement-acceptance endpoint refuses to proceed without a current acceptance on record. The check is performed on the server and is not dependent on client behaviour.
3.6 Withdrawal. A Maker may withdraw this consent through the ordinary consent-withdrawal route. Withdrawal is recorded and prevents further acceptance of Requirements; it does not affect obligations already owed to a Customer in respect of a Requirement already accepted.
4. What This Declaration Deliberately Does Not Contain
4.1 No indemnity. No clause requiring the Maker to compensate Craftolin against losses has been drafted. An over-broad indemnity given by an individual home-based Maker carries a real risk of being held unenforceable, which would leave Craftolin with no protection at all rather than modest protection. Whether a narrow indemnity is appropriate is a question for counsel (§5.3).
4.2 No warranty of licence-holding. Point 3 is framed as an acknowledgement of responsibility rather than a statement that the Maker in fact holds every licence applicable to them. A Maker who is unaware that a licence applies to their activity does not, by accepting this, make a false statement of fact. Whether the harder form is preferable is a question for counsel (§5.1).
4.3 No representation by Craftolin. Nothing in this declaration is, or may be presented as, a representation by Craftolin that the Maker is verified, vetted, licensed, registered, or otherwise approved. Craftolin performs no such checks and says so — see Terms and Conditions §1.4 and Partner Agreement §4.4 and §5. Acceptance of this declaration must never be surfaced to Customers as a trust or verification badge.
5. Questions for Counsel
5.1 Point 3 — acknowledgement or warranty? As drafted, the Maker accepts that compliance is their responsibility. The alternative is a warranty that they hold every applicable registration and licence. The warranty is stronger for Craftolin but harsher on Makers and may be unrealistic for the intended user base. Which is appropriate?
5.2 Points 1 and 2 — the qualifier is deliberately asymmetric. Point 2 is qualified by "as far as I know"; point 1 is not. The reasoning is that a Maker knows their own name, address and telephone number for certain, whereas whether a photograph fairly represents a product involves judgement. The consequence is that an inaccurate address is a false statement while an optimistic photograph is not. Is that division correct, and is "as far as I know" the right formulation, or should it be "to the best of my knowledge and belief"?
5.3 Indemnity. Should one be included at all, and if so how narrowly drawn, given that the counterparty is typically an individual and the weaker party to the bargain?
5.4 Relationship with the Partner Agreement. This declaration restates in short form matters that the Partner Agreement covers at length. Divergence between the two would operate against Craftolin. Should this declaration restate, cross-refer, or be incorporated by reference?
5.5 Language. Whether Hindi and/or regional-language versions are required for consent to be informed, given the intended user base.
5.6 Reading time. Whether 30 seconds is defensible as a minimum, or whether a different period (or none) is preferable.
5.7 Retention. How long consent records should be retained after an account is closed, read together with the Data Retention Policy.
Nothing in this document is legal advice. It was drafted by the development team to give counsel a starting point to correct, and must not be relied upon until reviewed.