Skip to content

Latest commit

 

History

History
192 lines (182 loc) · 12.8 KB

cic36.md

File metadata and controls

192 lines (182 loc) · 12.8 KB

CIC 36

Declarations on Formation of a Community Interest Company

+-----------------------------------+-----------------------------------+ | Company Name in Full | OpenCulinary C.I.C. | +-----------------------------------+-----------------------------------+ | ### SECTION A: COMMUNITY INTEREST | | | STATEMENT -- beneficiaries {#sec | | | tion-a-community-interest-stateme | | | nt-beneficiaries} | | | | | | We/I, the undersigned, declare | | | that the company will carry on | | | its activities for the benefit of | | | the community, or a section of | | | the community. | | | | | | > The company's activities will | | | > provide benefit to ... | | | | | | Individuals and families seeking | | | to discover and prepare healthy, | | | affordable food & nutrition | | | matching any dietary constraints | | | they may have. | | +-----------------------------------+-----------------------------------+


COMPANY NAME OpenCulinary C.I.C.


+-----------------------------------+-----------------------------------+ | ### {#section} | | | | | | ### SECTION B: Community Interest | | | Statement -- Activities & Relate | | | d Benefit {#section-b-community- | | | interest-statement-activities-rel | | | ated-benefit} | | | | | | Please indicate how it is | | | proposed that the company's | | | activities will benefit the | | | community, or a section of the | | | community. Please provide as much | | | detail as possible to enable the | | | CIC Regulator to make an informed | | | decision about whether your | | | proposed company is eligible to | | | become a community interest | | | company. It would be useful if | | | you were to explain how you think | | | your company will be different | | | from a commercial company | | | providing similar services or | | | products for individual or | | | personal gain. | | +-----------------------------------+-----------------------------------+ | Activities | ### {#section-2} | | | | | ### {#section-1} | How will the activity benefit | | | the community? | | | | | | ### {#section-3} | +-----------------------------------+-----------------------------------+ | Recipe Search Engine      | The community will benefit from | | | free, online public access to a | | | smart recipe search engine which | | | helps individuals and families | | | make the most of the ingredients | | | they have available to them. | | | | | | As a website and installable as | | | an application, the search engine | | | will provide simple and effective | | | tools for diverse community | | | members with varying dietary | | | requirements, time constraints, | | | economic challenges and cooking | | | experience. | | | | | | The search engine will not be | | | funded by either advertising, any | | | financial sponsors, or by selling | | | user data -- and as such the | | | content and features it includes | | | will be led by (and cater to) the | | | community's requirements. | +-----------------------------------+-----------------------------------+ | Recipe Meal Planner      | The community will benefit from | | | access to a free online meal | | | planner, which will assist with | | | scheduling of meals both for | | | individuals and group meals with | | | family and friends. | | | | | | This will provide relief and | | | assistance to community members | | | in the important and potentially | | | time-consuming tasks of kitchen | | | stock management and ingredient | | | shopping. | | | | | | At present this kind of planning | | | can and is often done on paper, | | | and there are for-profit | | | businesses which are starting to | | | provide similar online meal | | | planning tools. | | | | | | OpenCulinary differentiates | | | itself by taking a strong stance | | | on privacy. All user data is | | | stored on user's own devices and | | | is never shared -- letalone sold | | | -- to the service or any third | | | party. This follows a set of | | | principles for developing | | | 'local-first software'. | | | | | | Over time we believe that | | | building tools which strongly | | | respect user privacy will provide | | | both a great service to the | | | community and also build their | | | deserved trust and feedback, | | | leading to further improvements. | | | | | | The service will allow users to | | | 'send' the shopping list for | | | their meal plan to online | | | supermarkets in order to arrange | | | deliveries if they choose to, | | | but this will always be opt-in | | | and the service will always | | | provide meal planning without the | | | need to create any user accounts | | | or deal with any third-party food | | | suppliers. | +-----------------------------------+-----------------------------------+

+-----------------------------------------------------------------------+ | If the company makes any surplus | | it will be used for... | | | | Further investments within the | | company to improve the service | | provided, including but not | | limited to: increasing the number | | of recipes and ingredients | | included in the service, | | improving accessibility and | | translating the service for user | | in other languages, improving the | | level of detail and accuracy of | | ingredient information, providing | | relevant cooking education and | | guidance, and providing | | documentation to users. | +-----------------------------------------------------------------------+


COMPANY NAME OpenCulinary C.I.C.


+-----------------------------------------------------------------------+ | SECTION C: | | | | ### We/I, the undersigned, declare that the company in respect of whi | | ch this application is made will not be: {#wei-the-undersigned-declar | | e-that-the-company-in-respect-of-which-this-application-is-made-will- | | not-be} | | | | > (a) a political party; | | > | | > (b) a political campaigning organisation; or | | > | | > (c) a subsidiary of a political party or of a political campaignin | | g | | > organisation. | | | | SECTION D: | +-----------------------------------------------------------------------+


 Signed           Date