Privacy Policy
What personal data is held, why, for how long, and how to have it erased.
This Privacy Policy (hereinafter, the “Policy”) sets out the purposes for which, the legal bases on which and the manner in which personal data are collected, processed, stored, transferred and protected on the IdeaNest reward-based crowdfunding platform (hereinafter, the “Platform”) operated by Alievs Space MMC (Tax ID (VÖEN): 1906482561, registered address: Baku city) (hereinafter, the “Operator”).
The Policy has been prepared on the basis of the Constitution of the Republic of Azerbaijan, the Law “On Personal Data”, the Law “On Electronic Commerce”, the Law “On Protection of Consumer Rights”, the Civil Code and other applicable legislative acts. The Policy forms an integral part of the “Terms of Use”, the “Cookie Policy”, the “Creator Agreement”, the “Backer Agreement” and the other “Legal Documents”.
By registering on the Platform, using the Platform, creating a Campaign or making a Pledge, you confirm that you have read and understood this Policy. Where consent is required, it is obtained separately, in an express and specific form, and may be withdrawn at any time.
1. Key Definitions
1.1. Terms used in this Policy have the meanings given to them in the “Terms of Use”. In addition, the following definitions apply:
1.1.1. Personal data means any information relating to an identified or identifiable natural person (data subject), including first name, surname, e-mail address, telephone number, postal address, VÖEN, online identifiers, IP address and other similar information.
1.1.2. Data subject means a natural person whose personal data are processed: a visitor to the Platform, a User, a Creator, a Backer, a Creator's representative or any other person who contacts the Platform.
1.1.3. Processing means any operation performed on personal data by automated or non-automated means: collection, recording, systematisation, storage, alteration, use, transfer, blocking, depersonalisation and destruction.
1.1.4. Owner and operator means the person who determines the purposes and means of the processing of personal data. For the purposes of this Policy, such person in respect of the personal data processed on the Platform is the Operator, subject to the exceptions set out in Section 4.
1.1.5. Processor means a third party that processes personal data on behalf of and on the instructions of the Operator (for example, a hosting provider, an e-mail delivery service or a payment provider).
1.1.6. Depersonalisation means an operation that makes it impossible to attribute personal data to a specific data subject without additional information.
1.1.7. Payment token means a unique identifier issued by the payment provider in place of bank card details which does not reveal the full card number.
2. Operator and Contact Details
2.1. The person responsible for the processing of personal data on the Platform is: Alievs Space MMC, Tax ID (VÖEN) 1906482561, registered address: Baku city.
2.2. For all queries, requests and complaints relating to personal data: e-mail — [email protected]; general support — [email protected]; telephone — +994 99 790 77 74; postal address — Baku city.
2.3. The Operator appoints a person responsible for overseeing the protection of personal data. The responsible person may be contacted via the privacy e-mail above.
3. Scope of the Policy
3.1. The Policy applies to:
• the ideyanest.com website and all of its language versions (Azerbaijani, English, Russian);
• the Platform's account, dashboard, catalogue, campaign pages, “Coming Soon” pages, Pledge checkout pages and the Pledge Manager;
• e-mails and in-site notifications sent by the Platform;
• requests to the support service and any other correspondence with the Operator;
• other services that the Operator may in future provide within the Platform and that refer to this Policy.
3.2. The Policy does not apply to third-party websites and services opened via links on the Platform (including Creators' social media pages, the payment provider's payment page and courier services' tracking websites). Such resources have their own privacy policies, which you are advised to read separately.
3.3. Detailed information on cookies and similar technologies is provided in the “Cookie Policy”.
4. Allocation of Roles: Operator, Creator and Backer
4.1. The Platform is an intermediary between the Creator and the Backer. Accordingly, there are two distinct roles in the processing of personal data:
4.1.1. The Operator processes data for its own purposes and is responsible for such processing in respect of the operation of the Platform, account management, the acceptance and recording of Pledges, refunds, payouts, the review of disputes, moderation, security and compliance with legal requirements.
4.1.2. The Creator processes, as an independent owner, the Backer data made available to it through the Platform for the purposes of preparing and delivering rewards (fulfilment), communicating with Backers and managing its own Campaign. The Creator must use such data solely for the purposes set out in the “Creator Agreement” and this Policy, ensure their confidentiality and security, and comply with the law.
4.2. Once the Creator has exported Backer data from the Platform (for example, by means of a CSV file for transfer to a courier), the Creator is responsible for the further processing of such data. The Operator records each instance of export in a log.
The Creator may not use Backer data for purposes other than the delivery of rewards and communication relating to the Campaign, including for the purpose of selling or transferring them to third parties or sending advertising for other projects without the Backer's consent.
5. Data We Collect, Purposes of Processing, Legal Bases and Retention Periods
5.1. The Operator collects only the minimum amount of data necessary for specific, explicit and lawful purposes. The table below sets out the categories of data, their source, the purposes of processing, the legal bases and the retention periods.
Category: Account data Data included: First name, surname (or username), e-mail, password hash, selected interface language, registration date, account status, confirmation of being over 18 Purpose: Creating and managing the account, authentication, sending notifications Legal basis: Conclusion and performance of the agreement (“Terms of Use”) Retention period: For as long as the account is active and for 30 days after deletion of the account is requested; after this period the account is depersonalised: the name and e-mail are replaced with values that do not identify you and the password hash is deleted (clause 23.9); the remaining data of this category (for example, the registration date and interface language) are kept only as part of the depersonalised account, and no data are kept to prevent re-registration. Financial records, Pledges, payouts and the other data listed in clause 23.10 are not account data: they are kept, linked to the depersonalised account, under their own categories and for their own periods
Category: Profile data Data included: Profile picture, biography, city, social media links, history of past Campaigns Purpose: Displaying the Creator's public profile, ensuring trust Legal basis: Performance of the agreement; legitimate interest of the Operator (keeping Backers informed) Retention period: For as long as the account is active and, after deletion of the account is requested, until the account is depersonalised (clause 23.9), when the profile picture together with its stored file, the biography, the city and the social media links are deleted; Campaign history — 5 years
Category: Creator's financial and identification data Data included: VÖEN, name of the entrepreneur or legal entity, payment token and masked number of the business card, cardholder name, identity documents where necessary Purpose: Withdrawal of funds, verification of the validity of the VÖEN and of card ownership, payout, tax and accounting, fraud prevention Legal basis: Performance of the agreement (“Creator Agreement”); legal obligation (tax and accounting legislation) Retention period: 5 years after the last payout or such longer period as is established by law; the identity documents themselves (their images) are deleted 7 days after the verification decision, or 60 days after submission if they are never reviewed — after that only the fact that the verification took place and its result are kept
Category: Campaign content Data included: Title, description, story, images, video, risks section, reward tiers, FAQ, updates Purpose: Publication of the Campaign, moderation, display in the catalogue Legal basis: Performance of the agreement Retention period: At least 5 years after the Campaign closes (for accessibility via direct link and in the Backer's dashboard)
Category: Backer data Data included: List of Pledges, selected reward tiers and add-ons, amounts, date, anonymity choice, country of delivery Purpose: Processing and recording the Pledge, refunds, providing information to the Creator for the fulfilment of obligations Legal basis: Performance of the agreement (“Backer Agreement”) Retention period: 5 years after completion of the Campaign
Category: Payment data Data included: Payment token, masked card number (e.g. last 4 digits), card scheme, transaction identifier, amount, currency, status, 3-D Secure result Purpose: Charging the Pledge, refunds, handling disputes and chargebacks, accounting Legal basis: Performance of the agreement; legal obligation Retention period: 5 years after the last transaction
Category: Delivery addresses Data included: Recipient's name, address, postcode, city, country, telephone (stored in encrypted form) Purpose: Delivery of the reward, calculation of shipping costs Legal basis: Performance of the agreement Retention period: 1 year after all rewards have been delivered; then deleted or depersonalised
Category: Survey answers Data included: Information requested by the Creator through the Pledge Manager (size, colour, options, dates, address) Purpose: Preparing the reward in accordance with the Backer's choice Legal basis: Performance of the agreement Retention period: 1 year after all rewards have been delivered
Category: Communications Data included: Notification history, bulk mailings, in-site inbox messages Purpose: Informing about extensions, withdrawal of funds, the dispute period, refunds and updates Legal basis: Performance of the agreement; legal obligation (mandatory notifications) Retention period: 3 years; when the account is depersonalised, the notifications of the account, including in-site inbox messages, and its notification settings are deleted (clause 23.9)
Category: Comments and public content Data included: Comments on Campaign pages, reactions to updates Purpose: Enabling discussion, moderation Legal basis: Performance of the agreement Retention period: For as long as the Campaign page exists or until deleted by the user
Category: Support requests and complaints Data included: Text of the request, attachments, correspondence history, complaints about projects Purpose: Responding to requests, improving service quality, detecting breaches Legal basis: Performance of the agreement; legitimate interest Retention period: 3 years after the request is closed
Category: Dispute materials Data included: The Backer's objection, evidence, the Creator's explanation, the administrator's decision Purpose: Resolution of disputes, processing of chargebacks Legal basis: Performance of the agreement; legitimate interest (defence of claims) Retention period: 5 years after the decision
Category: Technical logs Data included: Login times, requests, error logs, immutable log of privileged operations Purpose: Security, fraud prevention, troubleshooting, audit Legal basis: Legitimate interest; legal obligation Retention period: General logs — 12 months; privileged operations log — 5 years
Category: Device and network data Data included: IP address, browser type and version, operating system, screen size, language, time zone Purpose: Provision of the service, security, detection of abuse Legal basis: Legitimate interest Retention period: 12 months
Category: Push notification tokens (mobile application) Data included: The push token of the device issued by Expo for the installation of the application, the platform (iOS or Android), the device name reported by the device's operating system, the application version, the account to which the token is linked, and the times of the first and the most recent registration. A token is registered only on a device on which you are signed in and have allowed notifications Purpose: Sending to the mobile application the push notifications you have allowed (for example, about Pledges, payments, Campaigns, comments and rewards), according to the notification categories chosen in the application's notification settings; account security notifications (for example, about a sign-in from a new device) cannot be turned off Legal basis: Consent (permission for notifications on the device); it can be withdrawn at any time in the device settings, and individual categories of notifications can be turned off in the application's notification settings Retention period: Until you sign out of the application on that device, until the application is next opened after notifications have been turned off for it in the device settings, until the notification service reports that the token is no longer valid (for example, after the application has been uninstalled), or until deletion of the account is requested (see clause 23.8); a token that has not been refreshed for 180 days (the application refreshes it each time it is opened while you are signed in) is deleted automatically
Category: Crash and error reports (mobile application) Data included: Reports of crashes and errors of the mobile application: the error message and a technical description of where in the application it occurred, a record of the latest technical events in the application before the error, the device model, the operating system and its version, the application version and build number, the identifier of the latest request to the Platform's server and, if you are signed in, the account identifier (without name or e-mail); information on whether application sessions ended normally or with a crash; performance measurements (application start, screen loading and request times) for 10% of sessions. The IP address of the device is received by the service when a report is sent. Before a report is sent, personal data (names, contact details, addresses, passwords, tokens, payment details) and the device name are removed from it; no screenshots or screen recordings are made Purpose: Detection and correction of crashes and errors of the mobile application, monitoring of its stability and performance Legal basis: Legitimate interest of the Operator (ensuring the stable and secure operation of the mobile application) Retention period: Crash and error reports — for the period set by the error-monitoring service (Sentry), not longer than 90 days; performance measurements — for the period set by that service
Category: Application update data (mobile application) Data included: Each time it is started, the mobile application checks for updates and sends the mobile application services provider (Expo) the IP address of the device, a random installation identifier created by the application that is not linked to the account, the platform, the version of the application and of the installed update, and the update channel Purpose: Delivery of updates and fixes to the mobile application Legal basis: Legitimate interest of the Operator (delivering fixes and security updates to the mobile application) Retention period: The Operator does not store these data; they are processed by Expo for the period set by its own rules
Category: Approximate location data Data included: Coordinates for the “near me” filter, rounded to an accuracy of approximately 1 km Purpose: Displaying nearby Campaigns Legal basis: Consent (location permission in the browser) Retention period: Not stored — used only for the duration of the request
Category: Traffic source (attribution) data Data included: The amount and time of the Pledge and the source to which it is attributed — without names or contact details. The website does not currently record visits, referrer information or UTM parameters for attribution, so Pledges are attributed to the “direct” source Purpose: Providing the Creator with an aggregated report by traffic source Legal basis: Legitimate interest Retention period: Visit data are not recorded; aggregated statistics — indefinitely (depersonalised)
Category: Audience statistics Data included: The fact that a page was opened, a Campaign page was viewed or a Campaign card was clicked; country; platform (web, iOS, Android); the section the card was shown in. The IP address and browser details are hashed one way, only while the request is handled, with a random key created for that day, and are not stored. No cookie is used and nothing is stored on the device. The country is taken from the information passed on by Cloudflare or from the DB-IP database (db-ip.com, CC BY 4.0) Purpose: Aggregated statistics on how many people visit the Platform and its Campaigns and from which countries; showing the view count on a Campaign card; providing the Creator with an audience report for their own Campaign Legal basis: Legitimate interest of the Operator (running the Platform and informing Creators) Retention period: The daily key and the hashes that prevent double counting — until the end of the following day, then deleted; aggregated counts (day, hour, country, platform) — indefinitely, without identifying anyone
Category: Web analytics (Cloudflare) Data included: The address of the page opened (without the part after the “?” sign), the referring website, browser, operating system and device type, country, and page loading speed and quality metrics (Core Web Vitals), sent by the Cloudflare Web Analytics script that Cloudflare's network adds to the Platform's pages. No cookie is used, nothing is stored on the device, and visitors are not recognised or tracked by IP address or browser details Purpose: Aggregated statistics on views of and visits to the Platform's pages and on their loading speed; improving the operation of the Platform Legal basis: Legitimate interest of the Operator (ensuring the operation and technical quality of the Platform) Retention period: Cloudflare keeps individual measurements in full for 7 days and thereafter only in aggregated, sampled form; the Operator has access only to aggregated statistics that do not identify anyone
Category: Cookies and similar technologies Data included: The sign-in cookie (refresh token); the selected interface language, country and theme; a record of a dismissed maintenance notice. Analytics and marketing cookies are not used Purpose: The purposes set out in the “Cookie Policy” Legal basis: The sign-in cookie — performance of the agreement and legitimate interest; cookies and browser storage that remember your choices — your request (performance of the agreement). No cookies requiring consent are used Retention period: The periods set out in the “Cookie Policy”
Category: Marketing preferences Data included: Newsletter subscription, subscriptions to “Coming Soon” pages, following a Creator Purpose: Informing about new Campaigns and Platform news Legal basis: Consent Retention period: Until consent is withdrawn
5.2. Upon expiry of the retention period, data are deleted, destroyed or irreversibly depersonalised. Where court proceedings, a request from a public authority, a dispute or a chargeback are ongoing, the retention of the relevant data may be extended until such proceedings are concluded.
5.3. The Operator does not deliberately collect special categories of personal data (racial or ethnic origin, political opinions, religious beliefs, health, intimate life, etc.). Users are requested not to share such data in Campaign content, comments or support requests.
6. Sources of Data Collection
6.1. Data are obtained from the following sources:
6.1.1. directly from you — upon registration, completing your profile, creating a Campaign, processing a Pledge, completing surveys or contacting the support service;
6.1.2. automatically — from your device and browser when you use the Platform (technical logs, the cookies and browser storage described in the “Cookie Policy”, cookie-free audience statistics, cookie-free Cloudflare Web Analytics);
6.1.3. from the payment provider — the status of the transaction, payment token, masked card number, and information on refunds and chargebacks;
6.1.4. from the Creator — for example, when the Creator uploads a tracking number for the shipment of a reward;
6.1.5. from public registers and open sources — for the purpose of verifying the validity of a VÖEN;
6.1.6. from other Users — for example, information provided about you in the course of a complaint or dispute.
6.2. If you provide the Operator with another person's data (for example, an address for the delivery of a reward to another person), you confirm that that person is aware of this and has consented to it.
7. Data Flow between the Backer and the Creator
7.1. When making a Pledge, the Backer understands that certain of their data will be made available to the Creator of the relevant Campaign for the purpose of preparing and delivering the reward. The following are visible in the Creator's backer database:
• the Backer's name and e-mail address;
• the selected reward tier, add-ons, the amount and date of the Pledge, and the status of the Pledge;
• the country of delivery and the delivery address collected through the Pledge Manager;
• answers given to the Creator's surveys.
7.2. The Backer's bank card details, payment token, password, IP address and other technical data are never provided to the Creator.
7.3. Anonymous backing. A Backer may choose to make a Pledge anonymously. In that case their name is not shown in the Campaign's public backer lists, in comments or in other public places. However, so that the reward can be delivered, the Backer's name and contact details remain available to the Creator.
7.4. Traffic source report. The source attribution report provided to the Creator reflects only the source, the amount and the time. The website does not currently record visits for this report, so Pledges are attributed to the “direct” source. The attribution system does not technically record who specifically made the Pledge, and no names are shown in the report.
7.5. Geographic report. The Creator is shown an aggregated breakdown by country of delivery.
7.6. Creator's public data. The Creator's name (or brand name), profile picture, biography, city, history of past Campaigns and the date of the latest update (including a neutral status indicating overdue updates) are displayed publicly. The Creator's VÖEN and business card details are not public and are visible only to an authorised administrator.
8. Recipients of Data and Processors
8.1. The Operator does not sell or rent personal data. Data are transferred only in the following cases and to the following extent:
Recipient: Payment provider (Payriff, Republic of Azerbaijan) Data transferred: Payment amount, currency, order identifier and the language of the payment page; card details are entered directly on the provider's page Purpose: Charging Pledges, 3-D Secure, refunds, payouts to the Creator's business card, processing of chargebacks
Recipient: Banks and payment systems Data transferred: Transaction data Purpose: Executing payments and refunds, chargeback disputes
Recipient: Hosting and cloud infrastructure provider (Hetzner Online GmbH, Federal Republic of Germany) Data transferred: All data stored on the Platform (including data stored in encrypted form) Purpose: Hosting of the Platform (servers, database, storage of uploaded images and videos), backups
Recipient: E-mail delivery service (Brevo; Sendinblue SAS, French Republic) Data transferred: Name, e-mail, content of the message Purpose: Delivery of notifications and service e-mails
Recipient: Network, content delivery and security provider (Cloudflare, Inc., United States of America) Data transferred: All traffic between the browser and the ideyanest.com website passes through Cloudflare's network, where it is decrypted for processing: the IP address, browser details, the addresses of the pages requested and the content of requests and responses, including the data entered in forms (for example, sign-in details, Pledge and delivery details); these data are processed transiently, only for the purpose of delivering the request, and Cloudflare keeps security logs (IP address and request details) for a limited period. The mobile application connects to the Platform's server directly, not through this network Purpose: DNS service for the ideyanest.com domain, delivery of the website's pages (content delivery network, CDN), encryption of the connection (TLS), protection against attacks (DDoS) and malicious traffic
Recipient: Web analytics provider (Cloudflare) Data transferred: The address of the page opened, the referring website, browser, operating system and device type, country and page performance metrics; the IP address and browser details are received by Cloudflare when the data are sent but are not used to recognise or track visitors Purpose: Cookie-free aggregated web analytics (see the “Cookie Policy”)
Recipient: Error and crash reporting service (Sentry; Functional Software, Inc., United States of America; European Union data region) Data transferred: Reports of errors and crashes of the mobile application, from which personal data (names, contact details, addresses, passwords, tokens, payment details) are removed before sending; the account identifier (without name or e-mail), device model, operating system and application version; performance measurements for 10% of sessions; the IP address of the device is received when a report is sent Purpose: Detection and correction of malfunctions of the mobile application
Recipient: Mobile application services provider (Expo; 650 Industries, Inc., United States of America) and, through it, Apple Push Notification service (Apple Inc.) and Firebase Cloud Messaging (Google LLC) Data transferred: For push notifications — the device's push token and the content of the notification (title, text and the link it opens); for application updates — the IP address of the device, a random installation identifier that is not linked to the account, the platform and the version of the application Purpose: Delivery of push notifications to the mobile application (only where notifications are allowed on the device) and delivery of application updates
Recipient: E-mail and messaging services used for support (Gmail — Google LLC; WhatsApp — WhatsApp LLC; both United States of America) Data transferred: When you write to the Operator by e-mail or via WhatsApp — your name, e-mail address or telephone number and the content of the message, including attachments Purpose: Receiving and responding to requests
Recipient: Creator Data transferred: The data listed in clause 7.1 Purpose: Preparation and delivery of rewards
Recipient: Courier and logistics companies Data transferred: Name, address, telephone — via the Creator's export Purpose: Delivery of the reward (under the Creator's responsibility)
Recipient: Professional advisers Data transferred: To the extent necessary Purpose: Legal, audit, accounting and tax services
Recipient: Public authorities Data transferred: To the extent required by law Purpose: Court decisions, lawful requests from law enforcement and tax authorities
Recipient: Legal successor Data transferred: Data relating to the operation of the Platform Purpose: In the event of reorganisation, merger or transfer of the business
8.2. The Operator enters into written agreements with processors. Such agreements provide for the processor's obligation to process data only on the Operator's instructions, to maintain confidentiality, to take appropriate security measures and to return or destroy the data upon termination of the agreement.
8.3. An up-to-date list of processors is provided upon request via [email protected].
9. Cross-Border Transfer of Data
9.1. The Platform's servers, database, uploaded files and backups are located in the European Union, in data centres of Hetzner Online GmbH (Federal Republic of Germany); accordingly, the personal data processed on the Platform are transferred outside the Republic of Azerbaijan and stored in the European Union. E-mails are sent through the Brevo service of Sendinblue SAS (French Republic), and crash reports of the mobile application are stored in the European Union data region of the Sentry service of Functional Software, Inc. (United States of America). Cloudflare, Inc., located in the United States of America, provides the network and security layer through which all traffic of the ideyanest.com website passes, as well as the web analytics service; the data it processes may be processed in the United States and in other countries where Cloudflare's network operates. Push notifications and updates of the mobile application are delivered through the services of 650 Industries, Inc. (Expo), Apple Inc. and Google LLC, and support correspondence sent by e-mail or via WhatsApp is processed by Google LLC and WhatsApp LLC respectively; these companies are located in the United States of America, and the data concerned may be processed there.
9.2. Cross-border transfers are carried out only in accordance with the requirements of the Law “On Personal Data”, to countries ensuring adequate protection of data, or where adequate safeguards (contractual obligations, encryption, access restrictions) are in place.
9.3. Where the Creator ships rewards outside Azerbaijan, the Backer's delivery data are necessarily transferred to courier and customs services in the country of destination. Such transfer is carried out at the request of the Backer who has selected the country of delivery and for the purpose of delivering the reward.
9.4. In the case of a cross-border transfer, the Operator requires the processor to process the data in the country of destination only for the purposes specified in the agreement, not to transfer them to third parties without the Operator's consent, to inform the Operator of requests from public authorities to the extent permitted by law, and to return or destroy the data upon termination of the agreement.
9.5. You can obtain detailed information on cross-border transfers (countries and safeguards applied) by sending a request to [email protected].
10. Security Measures
10.1. The Operator takes technical and organisational measures to protect personal data against unauthorised access, alteration, disclosure, loss and destruction, including:
10.1.1. Protection of card data. Bank card details are entered only on the payment provider's secure page and never reach the Platform's servers. The Platform stores only the payment token and the masked card number. Payments are authenticated using 3-D Secure technology.
10.1.2. Encryption. All data between the browser and the Platform are transmitted over an encrypted channel (HTTPS/TLS). Delivery addresses are stored in encrypted form in the database. Passwords are stored only as one-way hashes.
10.1.3. Segregation of roles. Staff access is divided into five separate roles: moderator, administrator, finance, compliance and support. Each role sees only the data necessary for its function. The person who approves payout details is not the person who sends money to those details.
10.1.4. Dual approval. Each payout requires the approval of two separate authorised persons.
10.1.5. Immutable log. Any privileged operation (access to data, approval of details, refund, payout, blocking of a user, granting an exception to requirements) is recorded in an audit log that cannot be altered or deleted.
10.1.6. Recording of exports. Each instance of a Creator exporting Backer data is logged.
10.1.7. Data minimisation. Location data are rounded to approximately 1 km; the attribution system does not store names; addresses are deleted or depersonalised after rewards have been delivered.
10.1.8. Organisational measures. Employees undertake confidentiality obligations; access is granted on the principle of “least privilege”, is reviewed regularly and is revoked immediately when an employee changes position or leaves.
10.1.9. Backups and recovery. Regular backups of data are made and recovery procedures are tested.
10.2. No method of transmitting or storing data is absolutely secure. The Operator takes reasonable measures to minimise risks, but the User is also responsible for the security of their account: choosing a strong password, not sharing it with others and immediately notifying [email protected] of any suspected unauthorised access to the account.
The Operator will never ask you by e-mail, telephone or messaging for your password, full card number, CVV/CVC code or SMS confirmation code. If you receive such a request, do not respond to it and let us know.
11. Automated Decisions
11.1. Automation is applied on the Platform only where the calendar or the percentage produces an unambiguous result:
• a Campaign being deemed successful (at least 80% of the goal raised);
• activation of the “Extend” button (at least 50% of the goal raised, within the relevant time window);
• an automatic refund to all Backers on the 8th day after the end of the first term for a Campaign that has not been extended and has raised less than 80% of its goal;
• an automatic refund where 80% has not been raised by the end of the extension;
• the automatic withdrawal of funds 30 days after the end of the term for a Campaign that has raised 80% of its goal;
• the display of the “Closing Soon” and “Extended” badges.
11.2. These automated operations are not based on profiling and do not involve the evaluation of personal characteristics — they are the execution of conditions in the “Legal Documents” that apply in the same way to all Campaigns.
11.3. All decisions requiring evaluation are taken by a human: a Backer's dispute and the verification of the VÖEN — by an administrator; the suspension or rejection of a Campaign — by a moderator. The Operator does not take decisions producing legal effects for Users or significantly affecting them solely on the basis of automated processing.
11.4. The sorting of Campaigns in the catalogue (relevance, popularity, newest, etc.) is based on Campaign indicators and does not involve individual profiling of Users.
12. Rights of the Data Subject
12.1. In accordance with the Law “On Personal Data”, you have the following rights:
12.1.1. Right to information — to learn which data about you are processed, the purposes of processing, the legal bases, the source, the retention periods and the recipients;
12.1.2. Right of access — to obtain a copy of your personal data;
12.1.3. Right to rectification — to require the correction and completion of inaccurate or incomplete data. You can change most account and profile data yourself in your dashboard;
12.1.4. Right to erasure — to require the deletion of data where there is no basis for processing;
12.1.5. Right to restriction (blocking) of processing — where the accuracy of the data is contested or the lawfulness of processing is in doubt;
12.1.6. Right to object — to object to processing carried out on the basis of legitimate interest;
12.1.7. Right to withdraw consent — at any time in respect of processing based on consent. Withdrawal of consent does not affect the lawfulness of processing carried out before it;
12.1.8. Right to data portability — to receive the data you have provided in a structured, machine-readable format;
12.1.9. Right to lodge a complaint — to complain about the Operator's actions to the competent public authority or to a court.
12.2. Limitations on the right to erasure. Certain data may be retained even after a request for erasure where their retention:
• is required by law (for example, data on financial transactions and tax records);
• is necessary for the performance of obligations in respect of an ongoing Campaign, Pledge, refund, payout, dispute or chargeback;
• is necessary for the establishment, exercise or defence of legal claims;
• is necessary because the Creator's obligation to deliver rewards has not yet been completed (in which case the Creator retains access to the Backer's delivery data).
12.3. The account of a Creator who has a live Campaign or whose reward obligations have not been completed cannot be fully deleted; in such cases the account is kept in a blocked state until the obligations have been completed.
13. Procedure for Exercising Rights
13.1. To exercise your rights, send a request to [email protected] from the e-mail address registered to your account, or submit it in writing to Baku city.
13.2. The request must state your name, the account e-mail address, the right you wish to exercise and as specific a description as possible. The Operator may request additional information to verify your identity; this is to prevent your data from being disclosed to another person.
13.3. The Operator responds to the request within the period established by law, but in any event no later than 30 calendar days from the date of receipt of the request. Where the request is complex or the number of requests is high, this period may be extended with justification; you will be informed of this within the initial period.
13.4. Responding to requests is free of charge. In accordance with the law, the Operator may refuse manifestly unfounded or excessively repetitive requests or may charge reasonable administrative costs.
13.5. Where a request is refused, the Operator informs you in writing of the reason for the refusal and of the options for lodging a complaint.
14. Age Restriction
14.1. The Platform is intended for persons who have reached 18 years of age. Upon registration, the User confirms that they have reached 18 years of age.
14.2. The Operator does not knowingly collect the personal data of persons under 18. Where it is discovered that such data have been collected, the relevant account is blocked and the data are deleted, except for data required to be retained by law. A parent or legal representative who believes that a child's data have been provided to the Platform should contact [email protected].
14.3. Where a card is used without the cardholder's knowledge (for example, by a minor family member), the cardholder may dispute the payment in the manner provided for in the “Dispute Resolution Policy”.
14.4. The Operator does not require documents to verify age, but where there is reasonable suspicion that an account belongs to a person under 18 (for example, in the course of a complaint or dispute), it may request information confirming age. Documents provided for this purpose are deleted within 30 days after the verification is completed.
14.5. Even where a Creator offers items intended for children as rewards (for example, a children's book or a toy), a Pledge may be made only by a person who has reached 18 years of age; the child's data must not be stated as the recipient of the reward — delivery is arranged in the name of the parent or legal representative.
15. Notifications and Marketing Consents
15.1. Service (mandatory) notifications. Notifications that are important for the security of your account and Pledges and for your rights are sent irrespective of marketing consent and cannot be opted out of. These include: confirmation of registration and of the Pledge, extension of the Campaign, the Creator's request for the withdrawal of funds and the last date on which the payment may be disputed, refunds, survey requests and reminders, decisions on disputes, material changes to the “Legal Documents”, and security warnings.
15.2. Creator updates and mailings. The Creator of a Campaign you have backed may send you updates and bulk messages through the Platform. Such mailings are subject to frequency limits and must relate only to the relevant Campaign.
15.3. Marketing e-mails. E-mails about Platform news, new Campaigns and thematic collections are sent only with your separate consent. You may withdraw consent at any time in your account settings or via the “unsubscribe” link at the end of each e-mail.
15.4. “Coming Soon” pages and following a Creator. By subscribing to a Campaign's “Coming Soon” page or following a Creator, you consent to receiving notifications about the launch of the relevant Campaign or about new Campaigns of that Creator. The subscription may be cancelled at any time.
15.5. Notifications are sent in the language you have selected in your profile.
15.6. Notification settings. In your account settings you can choose the frequency and channel (e-mail or in-site inbox only) of Creator updates, replies to comments and recommendation e-mails. The mandatory notifications referred to in clause 15.1 are sent both by e-mail and to the inbox irrespective of these settings.
15.7. The Creator's own channels. Where the Creator wishes to add a Backer's e-mail address to its own newsletter outside the Platform, it must obtain separate and demonstrable consent from the Backer for this purpose. Making a Pledge does not constitute such consent.
15.8. Proof of consent. The Operator records the date and channel of the granting and withdrawal of marketing consent and the version of the consent text, and retains such records for 3 years after consent is withdrawn.
16. Measures in the Event of a Personal Data Breach
16.1. Where a breach of the security of personal data (leak, unauthorised access, loss) is detected, the Operator immediately:
• takes measures to contain the incident and limit its consequences;
• assesses the nature, scope and risks of the incident;
• where required by law, notifies the competent public authority within the prescribed period;
• where the incident poses a high risk to the rights of data subjects, informs the affected Users without undue delay by e-mail or in-site notification, explaining the nature of the incident and the measures they can take;
• documents the incident and takes measures to prevent its recurrence.
17. Third-Party Services and Links
17.1. Links, including video links, or other content posted by Creators on Campaign pages may lead to third-party websites. External videos are not embedded in the Platform's pages and open on the relevant service's own website only when the link is clicked. Such websites may collect your data, and the Operator bears no responsibility for their privacy practices.
17.2. When making a Pledge, you are redirected to the payment provider's page. The data you enter on that page are processed in accordance with the payment provider's privacy policy and the security standards of the payment card industry.
18. The Creator's Obligations regarding Backer Data
18.1. By obtaining Backer data, the Creator undertakes:
• to use the data solely for the preparation and delivery of rewards and for communication relating to the Campaign;
• to transfer the data to third parties only to the extent necessary for delivery (courier, logistics, production partner) and to require them also to maintain confidentiality;
• to store exported files securely and to destroy them once the obligations have been completed;
• not to use the Backer's data to advertise other projects without the Backer's express consent;
• to inform the Operator immediately in the event of a breach of data under its control;
• to respond to Backers' requests concerning their own data in accordance with the law or to forward them to the Operator.
18.2. A breach of these obligations constitutes a breach of the “Creator Agreement” and may result in the blocking of the account and other consequences provided for by law.
19. Principles of Personal Data Processing
19.1. When processing personal data, the Operator observes the following principles:
19.1.1. Lawfulness and fairness — data are processed only on grounds established by law and with respect for the rights of the data subject;
19.1.2. Purpose limitation — data are used only for the purposes specified at the time of collection and are not processed in a manner incompatible with those purposes;
19.1.3. Data minimisation — the volume of data collected is limited to what is necessary to achieve the purpose;
19.1.4. Accuracy — the Operator takes reasonable measures to ensure that data are accurate and up to date and gives the User the ability to update their data;
19.1.5. Storage limitation — data are not kept for longer than is necessary for the purposes of processing;
19.1.6. Integrity and confidentiality — data are protected by appropriate technical and organisational measures;
19.1.7. Accountability — the Operator documents its processing activities in order to be able to demonstrate compliance with these principles.
20. Data Processing during the Campaign Life Cycle
20.1. For the sake of transparency, the data processed at the main stages of a Campaign are explained below.
20.1.1. Draft. The Campaign content entered by the Creator (title, description, story, images, video, risks, tiers) is stored as a private draft visible only to the Creator. At this stage the Creator is informed that a VÖEN and a business card will be required for the withdrawal of funds.
20.1.2. “Coming Soon” page. The e-mail addresses of Users who subscribe to the page and the subscription date are stored in order to send a notification about the launch of the Campaign. The list of subscribers is shown to the Creator only as a number.
20.1.3. Moderation. The moderator reviews the Campaign content, the Creator's profile and the history of its past Campaigns. The moderator's decisions and reasons are stored in the Creator's checklist and in the audit log.
20.1.4. Fundraising. For each Pledge, the Backer's choice, the amount, the payment token, the status of the transaction and the source to which the Pledge is attributed (see clause 7.4) are recorded. At the time of the Pledge, the money is charged immediately and held in the account of the Operator or the payment provider.
20.1.5. Extension. When the Creator extends the Campaign, all Backers are sent a notification of the new date; their e-mail addresses and notification settings are used for this purpose.
20.1.6. Refund. Where the Campaign has not raised 80% of its goal, is suspended or is cancelled, the refund is made by means of the payment token and the transaction identifier; the Backer is sent a notification.
20.1.7. Withdrawal of funds. The Creator enters the VÖEN and the business card; the administrator verifies the validity of the VÖEN and that the card belongs to the Creator. All Backers are sent a notification of the last date on which the payment may be disputed.
20.1.8. Fulfilment. Survey answers and delivery addresses are collected through the Pledge Manager; the Creator “freezes” the addresses, exports them and uploads tracking numbers; the Backer sees the tracking number in their dashboard.
20.1.9. Completion and archive. Even after the Campaign has been removed from the catalogue and search, it remains accessible via a direct link and in Backers' dashboards; addresses and survey answers are deleted or depersonalised within the periods specified in Section 5.
21. Disputes, Chargebacks and Fraud Prevention
21.1. Where a Backer disputes a payment, the Operator processes, for the purpose of reviewing the dispute, the Backer's request, the evidence submitted, the data on the Pledge and the payment, the Creator's explanations and the correspondence relating to the Campaign. These data may be shown to the other party to the dispute to the extent necessary.
21.2. Where a chargeback is initiated through a bank, the Operator may provide the payment provider and the bank with evidence of the transaction, the Campaign and the fulfilment of obligations (for example, tracking numbers and the Creator's updates).
21.3. To prevent fraud, unauthorised use of cards, the creation of multiple accounts and other abuse, the Operator may analyse technical data (IP address, device data, transaction patterns) on the basis of legitimate interest. The results of such analysis do not lead to automatic blocking — the decision is always taken by an authorised employee.
22. Requests from Public Authorities
22.1. The Operator discloses personal data to public authorities only on the grounds and in the manner established by law, upon a written and lawful request.
22.2. Each request is examined as to its lawfulness and scope; the Operator provides only the minimum data required. Unless prohibited by law, the Operator may inform the relevant User of the request.
23. Account Deletion
23.1. You can delete your account in your account settings or by sending a request to [email protected].
23.2. From the moment deletion of the account is requested, the profile is removed from public view (clause 23.8), and comments may be displayed as “deleted user” or removed. The data retained after deletion and their retention periods are specified in clause 23.10; data that are required to be retained by law are kept in a blocked state until the relevant periods expire and are not used for other purposes.
23.3. A Backer's account may be deleted even if rewards for the Campaigns they have backed have not yet been delivered; however, in that case the Creator retains access to the data necessary for delivery and the Backer loses the ability to see notifications and the tracking number in the dashboard.
23.4. In accordance with clause 12.3, a Creator's account cannot be deleted where there is a live Campaign, an unpaid chargeback debt or uncompleted reward obligations.
23.5. Open Pledges. Deleting the account does not cancel Pledges made and does not give rise to a refund. Where a Campaign has not raised 80% of its goal, the refund is made automatically to the same card also in respect of a Pledge made from a deleted account.
23.6. Payout obligations. Where a Creator awaiting a payout wishes to delete their account, the payout must first be completed or the Creator must waive the payout in writing; in that case the fate of the funds is determined in accordance with the “Creator Agreement”.
23.7. Deletion of the account takes effect 30 days after it is requested. Within this period the deletion can be cancelled by signing in to the account and cancelling it in the account settings, in which case the account is restored, subject to clause 23.8. After this period the account is depersonalised and can no longer be restored; when a new account is created, the previous history is not transferred to it.
23.8. When deletion of the account is requested, all sessions of the account on all devices are ended and all push notification registrations (push tokens) of the account are deleted immediately; until the deletion takes effect or is cancelled, no device can be registered for push notifications for the account. From the same moment the public profile of the account is hidden: it is not displayed publicly and does not appear in lists or search results. If the deletion is cancelled, the previous visibility of the profile is restored, and the mobile application registers the device for push notifications again when it is next opened while you are signed in, provided that notifications are allowed for it in the device settings.
23.9. When the account is depersonalised, the name and e-mail address are replaced with values that do not identify you, the password hash is deleted, and the profile data (the biography, the city, the social media links and the profile picture together with its stored file) are deleted. The following are also deleted, among other data: the notifications of the account, including in-site inbox messages, and its notification settings; the two-factor authentication secret, recovery codes and pending two-factor sign-in requests; links of the account to external sign-in services (Google, Apple); pending requests to change the e-mail address; and any remaining push notification registrations.
23.10. The following data are not deleted when the account is deleted or depersonalised; they are kept, linked to the depersonalised account, for the periods stated below, after which they are deleted or depersonalised in accordance with clause 5.2: support requests and complaints — 3 years after the request is closed; identity verification data of Creators, data on the Creator's legal status (VÖEN, name of the entrepreneur or legal entity) and payout details (payment token and masked number of the business card, cardholder name) — 5 years after the last payout or such longer period as is established by law; data on the signing of agreements on the Platform (including electronic signature data) — 5 years after the end of the relevant agreement; partner profiles (the share agreed with a partner of the Platform and the access granted to them) — 3 years after the end of the partnership; Pledges — 5 years after completion of the Campaign; payment data and other financial records — 5 years after the last transaction. These data are used only for the purposes for which they are retained (Section 5). Images of identity documents are not kept for these periods: they are deleted shortly after the verification, as stated in clause 5.1.
24. Exercising Rights: Procedures and Examples
24.1. The table below explains how each right is exercised in practice, what information must be provided and what the response covers.
Right: Information and access How to apply: Request to [email protected] from the account e-mail Example: A Backer wishes to know which Creators have seen their address Operator's response: A list of the data processed, the purposes, the recipients (including the Creators that have received the Backer's data), the retention periods and a copy of the data
Right: Rectification How to apply: Yourself in the dashboard or by request Example: A Creator has entered the VÖEN incorrectly Operator's response: The data are corrected; where financial details change, the administrator carries out a new verification
Right: Erasure How to apply: Account settings or request Example: A Backer has received all their rewards and wishes to close their account Operator's response: The account is deleted in accordance with Section 23; financial data required to be retained by law are kept blocked until the period expires; an explanation is provided
Right: Restriction How to apply: Request stating the reason Example: A User claims that their address is incorrect and asks that it not be used until verified Operator's response: The data are blocked for the duration of the verification and are only stored
Right: Objection How to apply: Request specifying the particular processing Example: A User objects to the use of technical logs for analytical purposes Operator's response: The Operator stops the processing unless there are overriding legitimate grounds (for example, a fraud investigation); the decision is reasoned
Right: Withdrawal of consent How to apply: Account settings, the “unsubscribe” link in an e-mail Example: A User opts out of marketing e-mails Operator's response: The change takes effect immediately or within 3 business days at the latest
Right: Portability How to apply: Request Example: A Creator wishes to obtain its Campaign content and profile data for use elsewhere Operator's response: The data are provided in a structured format (for example, JSON or CSV)
24.2. Where a request is made through a representative, a document confirming the representative's authority (power of attorney) must be provided.
24.3. Where a request affects the rights of other persons (for example, a Backer requesting the data of other Backers), the data of such persons are removed from the response or depersonalised.
25. Justification of Retention Periods
25.1. The retention periods specified in Section 5 have been determined on the basis of the following criteria:
25.1.1. Financial and tax data (5 years). Accounting and tax legislation requires documents evidencing transactions to be retained for a certain period; such data must also be available for audits by the tax authorities.
25.1.2. Pledges and dispute materials (5 years). Claims relating to the delivery of rewards, chargebacks and litigation may arise even after a Campaign has ended; the limitation periods established by the Civil Code are taken into account.
25.1.3. Account data (30 days after a deletion request). This period allows the deletion to be cancelled (clause 23.7); after it the account is depersonalised. Account data are not kept to prevent re-registration; the data necessary for the defence of possible claims (financial records, Pledges, payouts) are kept under their own categories and for their own periods (clause 23.10).
25.1.4. Delivery addresses and survey answers (1 year after delivery). This period is sufficient to resolve claims concerning lost or damaged parcels; as addresses are sensitive data, they are not kept for longer.
25.1.5. Technical logs (12 months). This is an appropriate period for investigating security incidents; the privileged operations log, however, is kept for 5 years for the purposes of financial control.
25.1.6. Attribution data. The website does not currently record visit data for attribution. If the recording of visits is introduced, its retention period will be stated in this Policy and in the “Cookie Policy” beforehand.
25.2. The Operator reviews retention periods at least once a year and deletes data that are no longer necessary ahead of time.
26. Categories of Processors
Processor category: Payment provider (Payriff) Function: Card acceptance, 3-D Secure, refunds, payouts Scope of access: Payment and transaction data Location: Republic of Azerbaijan
Processor category: Cloud infrastructure and hosting (Hetzner Online GmbH) Function: Servers, database, file storage, backups Scope of access: All data stored on the Platform (including encrypted data) Location: European Union, data centres of Hetzner Online GmbH (Federal Republic of Germany)
Processor category: Media file storage (Hetzner Object Storage) Function: Storage of uploaded images and videos and their delivery for display Scope of access: Campaign media, profile pictures Location: Federal Republic of Germany (Falkenstein; Hetzner Online GmbH)
Processor category: E-mail service (Brevo) Function: Sending notifications and e-mails Scope of access: Name, e-mail, content of the message Location: French Republic (Sendinblue SAS)
Processor category: Error and crash reporting (Sentry) Function: Detection of errors and crashes of the mobile application Scope of access: Error and crash reports with personal data removed, the account identifier, device, operating system and application details, performance measurements Location: European Union data region, Germany (Functional Software, Inc., United States of America)
Processor category: Network, content delivery and security (Cloudflare) Function: DNS, delivery of the website's pages (CDN), encryption of the connection (TLS), protection against attacks Scope of access: All website traffic, transiently and in decrypted form: IP address, browser details, requests and their content, including form data; security logs Location: United States of America and other countries where Cloudflare's network operates (Cloudflare, Inc.)
Processor category: Web analytics (Cloudflare) Function: Cookie-free aggregated measurement of page views, visits and page loading performance Scope of access: Page address, referring website, browser, operating system and device type, country, performance metrics; the IP address and browser details of the request (not used to recognise visitors) Location: United States of America (Cloudflare, Inc.)
Processor category: Push notifications and application updates (Expo) Function: Delivery of push notifications to the mobile application through Apple Push Notification service and Firebase Cloud Messaging; delivery of application updates Scope of access: Push token and notification content; for updates — IP address, random installation identifier, platform and application version Location: United States of America (650 Industries, Inc.; Apple Inc.; Google LLC)
Processor category: Support channels Function: Receiving and responding to requests Scope of access: Content of the request, contact details Location: Requests submitted through the Platform — European Union (Hetzner Online GmbH); e-mail — United States of America (Google LLC, Gmail); WhatsApp — United States of America (WhatsApp LLC)
27. Third-Party Data and Support Communications
27.1. Where the Creator posts images, names or other data of other persons in Campaign content (story, images, video, updates), it must obtain the consent of such persons. Where the Operator receives a complaint about such content, it investigates it under the moderation procedure and removes it where necessary.
27.2. Where a Backer states the name and address of another person for the delivery of a reward to that person (for example, as a gift), the Backer must ensure that that person is aware of this.
27.3. Correspondence with the support service is retained for the purposes of quality control, dispute resolution and evidence of the fulfilment of obligations. If telephone calls are recorded, a warning to this effect is given at the start of the call and recordings are not kept for more than 12 months, except where a dispute is ongoing.
28. Profile Visibility
28.1. A Backer may choose whether or not to display publicly in their profile which Campaigns they have backed. By default, the list of backed Campaigns is not displayed publicly.
28.2. The Creator's public profile (name, picture, biography, past Campaigns, date of the latest update) is necessary to ensure trust on the Platform and cannot be hidden for as long as the Creator's Campaigns exist on the Platform, except where deletion of the account has been requested (clause 23.8).
28.3. Comments are always published under the author's profile name. An anonymous Pledge does not ensure the anonymity of comments.
29. Security Incident Response Procedure
29.1. The measures set out in Section 16 are carried out under an internal procedure in the following order:
29.1.1. Detection and logging — information about the incident (a monitoring alert, or a report from an employee, User or processor) is logged and a responsible person is assigned to it;
29.1.2. Containment — affected access is blocked, passwords and keys are changed and, where necessary, the relevant functions (for example, export) are temporarily suspended;
29.1.3. Assessment — it is determined which data, how many Users and what risk are involved; the security of the keys to encrypted data is specifically checked;
29.1.4. Notification — the competent authority and Users are informed in accordance with clause 16.1; in incidents involving payment data, the payment provider is notified immediately;
29.1.5. Recovery and follow-up — systems are restored, causes are analysed and measures to prevent recurrence are documented.
29.2. The notification sent to Users states a description of the incident, the categories of data affected, the possible consequences, the measures taken by the Operator and recommendations to the User (for example, changing the password and being cautious about suspicious e-mails).
30. Changes to the Policy
30.1. The Operator may update this Policy in connection with changes in legislation, the functionality of the Platform or data processing practices.
30.2. Users are informed of material changes at least 15 days before the effective date by e-mail or by a banner on the Platform. Where a change requires new consent, such consent is obtained separately.
30.3. All previous versions of the Policy are kept in an archive and provided upon request. The date of publication and the effective date are indicated in each version.
31. Final Provisions
31.1. This Policy is governed by the legislation of the Republic of Azerbaijan.
31.2. The Policy has been drawn up in the Azerbaijani language. Translations into other languages are for information purposes; in the event of any discrepancy, the Azerbaijani text shall prevail.
31.3. Disputes relating to personal data are first resolved by contacting the Operator. This does not limit your right to apply to the competent public authority or to a court.
Operator: Alievs Space MMC
Tax ID (VÖEN): 1906482561 · Registered address: Baku city
Privacy matters: [email protected] · Support: [email protected] · Telephone: +994 99 790 77 74
Website: ideyanest.com