GDPR changes

You can limit the number of fundraisers that can be created via Settings > Maximum fundraising pages. You can set this per level (website level, sub site level, campaign level). If you then want to create an fundraisers and move over the button, you will see how many spots are still available.The moment there are no more spots, you cannot click the button and it will be greyed out:Note: This setting does not go together with activities. This is because you can also set a limit on activities. In case you want to set activities and there is already a maximum number of fundraising pages set, you get the message "The limit on the maximum number of fundraising pages is cleared.". After that, you won't see the menu item max number of fundraising pages until the activities are turned off at that level. If you work with activities and you want to set a maximum number of fundraising pages across all your activities (otherwise you could set it per activity), it's best to keep track of this manually and block fundraisers triggering at some point.

It is possible to track visitor behaviour on the iRaiser website, through Google Analytics. You can also have tracking pixels added by a support person upon request.Via Integrations > Google Analytics you can add a G-ID. From then on, measurements will come in to the linked GA4 property. You can find out the G-ID as follows:Click on Data streams: Then click on the url:On the top right you will see the ID:Visual ID:Add the G-ID. DatalayerWe fill an object with data that is pushed in the window.dataLayer so it can be used by Googles Tag Manager. Here you can see some examples of the object that is available, so it is clearer what kind of data you can expect here. For the full information, see the file: "Google Analytics 4 - Donation Purchase Event Documentation" (the are multiple tabs in that file)Here you can see examples of the datalayer after a Donations on an action page and in the Sign up flow:Example of the datalayer after donation on an action page:{"transaction_id": "T_0168de416b8d87cb47af12270e6a2a6cd6243c1f","affiliation": "iRaiser","value": "60. 0","currency": "CHF","payment_type": "ideal","items":"{"item_id": "D_0168de416b8d87cb47af12270e6a270a6cd6243c1f","item_name": "Donation on action by Henk Vries","item_brand": "iRaiser","item_category": "Fundraisers","item_category_2": "henk-vries-2","item_category_3": "Private","price": "60. 0","quantity": 1},{"item_id": "TC_0168de416b8d87cb47af12270e6a2a6cd6243c1f","item_name": "Transaction costs","price": "2.0","quantity": 1}]}&&">"item_category_3": "private","price": "60. And after the Sign up flow:{"transaction_id": "T_6a52a2e56689d38fc0dd3416869060e3367f57e3","affiliation": "iRaiser","value": "65. 0","currency": "EUR","payment_type": "ideal","coupon": "Discount code (as used)""items":[{"item_id": "D_57ef9a1aed94fe3129f995492a4b97f0b7bcfdb8","item_name": "Start donation","item_brand": "iRaiser","item_category": "Action","item_category_2": "john-doe","price": "15. 0","quantity": "1"},{"item_id": "RF_57ef9a1aed94fe3129f995492a4b97f0b7bcfdb8","item_name": "Registration fee","item_variant": "This is Registration fee","price": "50. 0","quantity": "1"},{item_id: "WI_Webshop item name",item_name: "Webshop item title",item_variant: "Item variant (as present)",price: "15.0",quantity: "1"}]}  

Settings ⟶ CouponsSometimes you have that special sponsor, ten employees of a particular organisation or someone who also committed last year, who deserves a discount on their registration. Coupons have been created for this purpose. With this feature, it is possible to create one or more discount code(s) that allow one to pay less registration fee.00:00 - Welcome00:25 - Where to find the Coupon feature00:42 - Let's create a coupon03:51 - How to use a couponAdd CouponsUse coupons use couponsAdd CouponsClick Add Coupons addFill in a descriptionOn the left at 'Discount' you can set the type of code and the discount Select One-time code or Reusable codeA One-time code is a code that is used only ééonce. Choose this one if you want to use several codes s. For example, when handing out codes in person at an event.A Reusable code is a generic code, which can be used several times. This code is generated and can then be used a set number of times (or infinitely).Select the type of discountWith Percentage (%) a certain discount percentage is given on the Registration fee.At Fixed amount (€), a fixed discount is given on the registration fee. However, this can never be lower than 0.On the right-hand side you can now set how you wish the code to be generatedChoose Generate automatically or Define the text yourselfIn the case of Generate automatically the text of the coupon code is randomly determinedIn the case ofDetermine text you can specify your own text of the discount code (at the bottom). This can be useful, for example, if you use the discount code for promotional purposes. You can only use the capital letters A-Z, 0-9 and dashes, and no spaces, when entering your own Coupons.Fill in the number of codes (max 500 per batch in the case of a One-off code)You can then choose to attach an End date and Time to the code. If you don't want to specify an end date, you can leave this field blank.Click SaveThen you return to the Overview and you can view discount code(s) under the blue eye ()  Download an export of the Coupons using Make Excel file  Coupons in useAs soon as an action starter has used a Once usable discount code it is crossed out (under the blue eye). The exact time when the coupon code was used and by which action starter is indicated. You can also use the button View to see which campaign starter it concerns. The code cannot be used after this.In case a Reusable code is used, the eyelet shows when and by whom this code was used. AnExcel file of this is also available for download.In the Donations Overview (under menu item Donations), it is indicated whether a coupon code has been used by the following icon: In the Donations export, the column Discount shows how much discount the action starter received on the Registration fee. The column Coupon shows the code used.On the My Entry page that each action starter has, it also states whether a Coupons was used and what effect it had on the entry. 

Match funding is a tool that can be used in both crowdfunding and peer-to-peer fundraising. It allows Companies and Funds to support Fundraisers and campaigns on the iRaiser platform.Content articleGeneralUseType Match fundingStart donationMultiply DonationOutputExcelGeneralTwo forms of Match funding are supported within the iRaiser framework:1. Starter donation2. Multiply DonationsWith the first variant, each new action, Campaign or Fundraiser receives an initial donation of a fixed amount from the company or fund. This could be interesting at a fundraising event (each participant is sponsored with xx euros by company X) or on a crowdfunding platform (each campaign receives an initial donation of €xx from company X).For the second variant, each donation is doubled (or far x-fold) by the company or fund doing the match funding. In both variants, the maximum amount available for the match funding can be set.The donation counter graphically displays the ‘match funding’contribution. Thereby, it can be referred to a page within the platform with more information. Match funding contributions are not subject to variable licence fees charged by iRaiser.Use On request, we can turn on Matchfunding functionality. You can find it then in the dashboard under Menu item 'Settings -> Match funding'. You can enable this at site, Sub site or project level by going to this level, managing it and going to Settings > Match funding and clicking on 'Yes, I want to use Match funding'.Following this, you can fill in the various fields:By organisation (mandatory field)Here you fill in the name of the organisation doing the match funding sponsoringColour You can choose a colour here and this colour will be reflected in the donation counter. Donations message Fill in a message here. This will be displayed with the donation. Suppose you enter "Match funding - Sustainability Fund" here it will look like this at the front end: More info URLTo provide more information about how your crowdfunding and Match funding works, you can create a Menu item (at site or segment level). You can put the url of this behind it. Once an url has been entered, an i will appear next to it where the user can click to read more information.  Type Match funding1. Start donationWith this type of Match funding, the organisation donates the first part of target amount when an action is created, i.e. not when making a donation. After the action is created, a (manual) donation is made directly on this action. You set its amount under Amount. You can optionally set a Maximum amount. Once that amount is reached, no more match funding will be done.An example of this type of match funding can be seen here2. Multiply DonationsThis type of Match funding focuses on Donations, and here the organisation multiplies every donation. After a donation is made, it is multiplied immediately. At Number, you can set how often you want to double the donation.Suppose 100 euros is donatedIf you set once, the organisation will add 100 euros.If you set twice, the organisation will add 200 euros.If you set 3x, the organisation will add 300 euros.If you set 4x, the organisation will add 400 euros.You can also set limits. A limit indicates what the maximum doubling can be. If you have set 4x as the number and a limit of 400 euros, and someone donates 200 euros then the amount the organisation contributes is 400 euros.Also here you can set a maximum amount. If that is reached then the pot is 'used up' and no more Match funding is done.An example of this type of match funding can be seen here.If you have this type of match funding active and you make a manual donation, you have to choose whether to matchfund the manual donation or not: OutputA donation made through Match funding is a manual automatic donation. It looks as follows:Match funding is linked to the original donation. If you delete it then the matchfunding donation will also be deleted. If you move the original donation then the match funding moves with it too.ExcelThe Excel file adds a new type of Payment Method: Match funding. Here see an example of an Excel file with match funding in which the columns not used by matchfunding have been omitted for convenience. Interested in this functionality on your platform? Then contact us.

Any transaction that is done has a description. If there is no PSP description filled in then it will say Donations <sitename> or Registration fee <sitename>, depending on whether it is a regular donation or one to which registration fee is linked.You can add extra text to the PSP description. This will then appear with the description and either for Donations <sitename> or for Registration fee <sitename>. Example:Here is the PSP description "PSP description with attribute" enteredIn the Buckaroo dashboard (this works the same with other payment providers), this looks like this:A donor will also see this on their bank statement or banking app. Depending on the number of characters filled in, the PSP description will be shown and therefore visible to a donor.You can set the PSP description per level, and in Buckaroo's (or another payment provider's) dashboard you can then search for all donations with that attribute. 

What is included in the Monthly reports?Directly after the end of a calendar month, a financialële Monthly report is available within the iRaiser Dashboard. The financialële Monthly reports contain a sum of all income and expenses in the month in question. It includes the following transactions:transactions that have been given the status 'paid' in the month in question only transactions settled via the online checkoutsuccessful PayPal and Tikkie transactions are also included in the statisticsThe Monthly reports can be viewed by month and downloaded by the site administrator in an excel file.What do the columns mean?All black amounts are income and all red amounts are expenses.DonatedThis includes donation income. Both regular donations and any start-up donations. It is a sum of the donation amounts. This does not include contributions to transaction fees, registration fees and webshop revenue.Registration feeThis includes receipts from paid registration fees.WebshopThis includes receipts from webshop items purchased at registration.Total refunded/refundedThe total amounts refunded by the site administrator and the total refunded by an end user, respectively.Transaction fees including VATThis is the cost of the payment service provider including VAT. PLEASE NOTE: this is an eo good indication of these costs. The costs may differ slightly from the actual payment service provider costs. For the actual payment service provider costs, please refer to the statement of these costs by the relevant payment service provider that can be seen in the payment service provider's dashboard. These transaction fees are automatically deducted from payouts by the payment service provider. iRaiser fees incl. VATThis refers to iRaiser's variable licence fees including VAT. These are calculated automatically per transaction based on the applicable agreements. In case of a volume tier this is automatically taken into account. The corresponding invoice of these costs can be downloaded via the download button. These variable iRaiser licence fees are automatically deducted from the payouts by the payment service provider. unless other agreements have been made. Split by Sub site and CampaignAt th top of the report are the totals for the entire website. A breakdown is then given on that:All transactions directly below the website homepage, broken down by Campaigns. Below that are the income from transactions on Fundraisers and Team pages created directly under the homepage and therefore not covered by a Campaign. Finally, general Donations made directly on the website's homepage. At the bottom there is a subtotal of all transactions directly under homepage, i.e. not under a Sub site or Campaigns.  In case of using the iRaiser Sub site module: all transactions per Sub site. For each Sub site, a breakdown of transactions per Campaigns is also given. Below that are the income from transactions on campaign and team pages that were created directly under the Sub site page and thus do not fall under a campaign. Finally, general Donations made directly on the website's Sub site page. At the bottom is a subtotal of all transactions directly under the relevant Sub site.

Ticketing via the webshop (“Ticketing”)Are you organising an event that requires tickets for attendees? If so, our webshop's ticketing feature could be the perfect solution. This feature allows you to create tickets automatically for your campaign, allowing you to stay organised and ready for your event.Features:This feature allows you to:Create varied ticket types based on cost.Register the data of the person who buy the tickets, also for future communications.Manage ticket availability and the maximum tickets that a supporter can purchase (this can be more than one if needed). During the event, easily track who is attending, and report the final attendance of the event in one click.Scan ticket during the event, and also add volunteers who can help with scanningTo activate this feature, let’s go through the steps to enable this:Enable e-tickets with the webshopFirst of all, check if the “E-tickets” and “Webshop” features are enabled in the left bar of your platform.Then, check if it's possible to turn off the creation of the fundraising page under Settings → Fundraising page.If this is not possible, please contact iRaiser support. We will check if the feature is included in your plan and then activate it for you.Create your ticket(s)To add a ticket item, go to Dashboard > Webshop > Catalog. From there, enable the webshop, add a new item, and select the 'ticket' option. You can then give the ticket a name and an amount. If it's a free ticket, simply enter "0."Additionally, you can indicate availability and set an order limit. This way, you maintain control over the number of available tickets. For example, you could create a ticket with 250 spots available, and allow a single buyer to order only four of them.You can, of course, create more than one type of ticket, with different availability and order limits for each.We also recommend adding an image; this makes the ticket visually recognizable in the registration flow. If a ticket is sold out, it will be grayed out. If it is the only type of ticket available, it will disappear completely from the registration flow.Remember to check where the tickets are available to supporters. If you create a ticket at the website level and make it available in a campaign, that ticket can be sold at both layers. Availability will be influenced by both: if there are 100 tickets available and one is bought at either the website or campaign layer, then there will be 99 tickets available for the next purchase, regardless of whether it happens on the website or in the campaign.Set up the “Sign up flow”The Sign up flow is the process a person goes through to register on the platform. In this case, it's for purchasing tickets. Let’s see how to create a simple registration flow for ticket purchase.Turn “Create a fundraising page off”On Community Fundraising Platform, by default, the person who registers is asked to create a fundraising page. For ticket purchases, we may not want them to create a page, so we need to go to Settings → Fundraising page, and then select “off”.Disable (or not) the “Start Donation”During the sign-up flow, you may ask people to make an additional, optional donation. If you don't want to add this step to make the ticket purchase even more straightforward, go to Settings → Start donation and uncheck that option.Customize the Sign up flowIt’s time to manage the steps of the registration process. Go to Settings → Sign up flow.If your website has different registration options (individual, team, etc.), you can turn them off for this layer where you want to sell tickets. We also suggest “show webshop” as the first step, so that the available tickets are the first thing presented, even before asking for registration data.You can then customize the text shown in every step of the flow on the left hand side: click on the second tab, “Sign up flow”, and then on “edit” corresponding to the step you want to modify.Remember that you can also customize the “Thank you page”, which is the page displayed after tickets are purchased. You can add text to reassure the buyer and build excitement for the event. For example: "Thank you for purchasing your tickets! You'll find them in your email in a few minutes. We're looking forward to seeing you at the event!"In the last tab, “Texts”, you can customize the registration button with a more event-related call to action, like “Reserve your place” or “Buy tickets”.EmailsOnce a client purchases tickets, they will receive related emails. The most important one will contain the PDF of the tickets attached, with one PDF per ticket.A single ticket will look like this:Note:The time it takes to generate them is proportional to the number of tickets. If only one ticket needs to be generated, it will take a few seconds. If 10 tickets need to be generated, the email will take a little longer to be sent.There are three emails to consider when enabling the ticketing system:“Set your password”: This is the standard email sent to any new user creating an account on the platform.In the email section of the layer where you created the tickets, you can then find the “participant” section.Here you may want to customize:Welcome email new participant: This is the email the purchaser will receive just after they have signed up for the event. Thank you mail for webshop ticket(s) order: This is the email with the various tickets attached. If the purchaser buys new tickets, they will receive another email like this one with the new tickets.Managing event attendanceOnce the event begins, you may want to manage the attendees. Each ticket has a QR code and a unique code on it.By clicking on E-tickets → E-tickets webshop → Overview, you will find the complete list of all the tickets generated. You can search for them by purchaser name or ID.You can even scan the QR code with your  camera (by clicking on the icon in the top right corner of the page), or create “scanner” users. Those are specific users that are only allowed to scan the tickets (they can not download data, they can not modify the contents…). Depending on the level you added them, they can scan tickets from that level. For example when you add a scanner to a specific campaign, they can only scan tickets from that campaign.Differences between tickets from participants and tickets from the webshopIn the Community Fundraising Platform, you might encounter another way to generate tickets: "participant tickets."Both types provide a PDF ticket with a scannable code, but there are some differences in how they can be used.Participant Tickets are primarily designed for events where individuals are asked (or encouraged) to set up a fundraising page and are mainly registering themselves. Marathons or other sporting events are good examples of this. If someone wishes to register more than one person, they will need to go through the registration process individually for each person. The ticket can be sent to the purchaser at a different time than when it was bought.Webshop Tickets, on the other hand, are intended for events where the main focus is simply allowing people to attend the event itself. The purchaser can buy multiple tickets in a single transaction, and the registration process can be significantly simplified by offering the ticket as the first step and removing steps like creating a fundraising page. Tickets are sent right after they're bought.If you are hosting a conference, a gala evening, or a concert, webshop tickets are the ideal choice for you.

Action starters can get badges in the iRaiser platform to reward them and give them extra motivation. There are two types of badges:Achievements badges. These are badges that one can earn by actively recruiting. These badges ("medals") are greyed out on the Fundraising page and are coloured in when the respective goal is achieved.Retention badges. This badge is linked to the number of participations. This badge ("ribbon") appears on the participant's action picture and shows how many times someone has already participated in the event.Badges for achieved goals (Achievements badges)These badges are aimed at motivating action starters to get started with their Fundraising page and reach various goals.For example, someone gets a badge for the first Donations and for posting a blog post. There are also badges for the amount of money raised (250, 500 and 1000 euros) and badges for the number of supporters (10, 25 and 50 donations).When this functionality is on, the following badges automatically appear on each Fundraising page:These badges are greyed out when not yet achieved and coloured in when achieved. The green colour you see above in the badge is the spot colour set on the site. This way, the badges are nicely integrated into your style.Badges are automatically coloured when the condition is achieved. When the functionality is turned on, all badges of existing action starters are also awarded retroactively. There are no emails associated with the badges. Although you could copyëren the email "More raised than set amount". You can then indicate in the mail when they reach 250, 500 and 1000 euros that they have earned a badge. Hooray!The badges have a fixed layout and also fixed conditions, and you can only choose to put all eight of them on them. You cannot make your own adjustments to this at the moment. We do want to make this adjustable in due course.Interested? Then send a message to iRaiser and we can turn it on for you!.Badges for number of participations (retention badges)You have the option of displaying a badge (image) on participants' fundraising page depending on the number of times they have participated.These Badges are part of the retention functionality, which consists of:The edition of your event -> This feature must be enabled to use the badges and retention functionality.A conditional welcome email based on number of participationsAble to set target amounts for action starters based on number of participationsThe aim is to make participants feel welcome and encourage them to participate more often. For a complete description, read the article on retention functionality.You can upload an image per participation. We have created four designs for you, see the downloads below. But you can also choose to design your own badges. This image has specific requirements: it must be a png image with transparency, the image must be 745x419 Pixels in size. So a landscape image. The badge is being placed over the existing image, so make sure the badge is not too large and is in one of the corners.You can only add retention badges if an edition is set. Please contact us for this.Download below your set of badges for returning participants. 

The iRaiser platform complies with the GDPR (General Data Protection Regulation) for storing personal data. Managers can use the dashboard to manage, for example, all consent texts displayed in forms that require Users to grant permission by checking a box. Below is general information on how to comply with the GDPR within iRaiser and some general explanation of what the GDPR is.Content of article:IntroductionController versus ProcessorWhat is personal data?What is a special personal data?When is there processing of personal data?General rules for processing personal dataOverview Personal dataExporting personal data: transferWhat are the rights of data subjects?Expressive consentRights of data subjectsRight of accessRight to rectification and completion and/or restriction of processingRight to erasureAt the request of the data subject (end user)On termination of contractRight to data portabilityIntroductionTo safeguard the data of our customers and their Users, we have established privacy and data protection policies within iRaiser.Privacy protection & personal data; General Data Protection RegulationPrivacy protection is regulated by various laws and treaties. The most important is the General Data Protection Regulation (GDPR), which comes into force from 25 May 2018. This is a European regulation (i.e. with direct effect) that standardises the rules for the processing of personal data by private companies and public authorities throughout the European Union. In addition, the Telecommunications Act provides rules on mailings, spam and cookies.Processor versus ProcessorThe GDPR makes a clear distinction between the duties and responsibilities of a so-called Controller and a Processor. iRaiser's customer owns the website and the data acquired with the website. They are the Controller. iRaiser carries out the technical operation of the website and does not do anything with the data without the consent of the customer. iRaiser is in GDPR terms a processor. The powers, duties and responsibilities of us as a Processor in terms of processing personal data are agreed in the so-called Processor Agreement that we conclude with our customers.  What is a personal data?Personal data is any data by which a person can beïdentified. A person can be identified if the person using the personal data can identify the person without making a special effort. This could include name and address data. E-mail addresses, passport photos, fingerprints and, for example, IP addresses are also considered personal data. And data that give a rating about a person, for example someone's IQ.     What is a special-personal data?In addition to ordinary personal data, the law also recognises special personal data. These are data that are so sensitive that processing them could seriously affect someone's privacy. Such data may therefore only be processed under very strict conditions. Special or sensitive personal data include, for example, data that says something about someone's race, religion, health, criminal past or sexual life. Trade union membership and the citizen service number (BSN) are also special personal data.Special personal data is data about someone's:race or ethnic originpolitical opinionsreligion or beliefmembership of a trade uniongenetic or biometric data for the purpose of unique identificationhealthsexual lifecriminal historyAn organisation may not use special personal data unless there is an exception for this in the law. There must be a need to request this data.When is personal data processing?"Processing means any operation involving personal data. The law lists as examples of processing: the collection, recording, organisation, storage, updating, modification, retrieval, consultation, use, provision by means of forwarding, dissemination or any other form of making available, bringing together, linking, blocking, erasing and destroying of data. From this enumeration, it is clear that the processing of personal data is readily apparent. One could argue that everything one does with personal data do falls under processing.General rules for processing personal dataMain rule is that personal data shall only be processed in accordance with the law and in a proper and careful manner. In addition, personal data may only be collected if a precise purpose is given for it. Moreover, the law states that personal data may only be processed insofar as they are adequate, relevant and not excessive.An example from practice is the making of a copy passport.An important obligation arising from the law is the notification that the processor must make to the Personal Data Authority AP. This notification is intended to promote transparency: all notifications made to the AP are included in a public register. Some processing operations do not need to be notified under the law, such as the trade register of the Chamber of Commerce. In addition, the GDPR includes a large number of processing operations that are exempt from notification. For such exempted processing operations, the other requirements of the GDPR simply remain in force. In addition to the general rules mentioned above, a justification ground must be present for any processing of personal data. This is explained below.Conditions for processing personal data: justificationsIn addition to the general rules mentioned above, the GDPR requires that at least ééone of the justifications listed in the law must apply to any processing of personal data. The GDPR has the following bases:ConsentThe data subject (this is the person whose data is being processed) has given his unambiguous consent to the processing. This explicit consent is also called informed consent or informed consent . The processing of personal data of a child under 13 requires the consent of a parent or legal representative. An organisation must make a reasonable effort to verify that consent.Execution of contractData processing is necessary for the performance of a contract to which the data subject is a party.Legal obligationData processing is necessary for compliance with a legal obligation.Vital interestData processing is necessary to counter a serious threat to the health of the data subject.Public law taskThe data processing is necessary for the proper performance of a public law task.Justified interestData processing is necessary for the fulfilment of a legitimate interest of the data controller (or of a third party to whom the data are disclosed). This means that the person processing the data must weigh his own interest against the interest and rights of the person concerned. The processor must also check beforehand whether the same result cannot be achieved with less data.Overview Personal dataIn the dashboard, via Administration > Overview Personal data, you can see a complete and current overview of all data processed by iRaiser for the website. This is governed by the concluded Collaboration Agreement or the General Terms and Conditions for the protection of personal data.A distinction is made between the personal data that iRaiser processes by default and the, for this website, specific personal data from set-up forms. You can have an Excel file generated from these via the Download button. This is sent by e-mail to the e-mail address of the site administrator requesting the download and can be retrieved there via a link. If desired, you can also filter the data by:All dataThe additional form data (additional questions)The default data (without the extra questions)Exporting personal data: transferExporting personal data, also known as transmission, is a form of processing personal data. The conditions described above apply to it in full. In addition, depending on the country to which the data is transferred, additional conditions apply.What are the rights of data subjects?The GDPR also grants rights to individuals whose data is processed:Right of inspectionThis right allows everyone to check whether, and in what way, their data are processed.Right of rectification and supplementation and/or restriction of processingWhen someone has used their right of inspection and comes to the conclusion that their data needs to be corrected, they can submit a request to that effect to the data controller.Right to oblivionThe data subject may object to certain forms of data processing, as a result of which the processing of his personal data may have to be stopped.Right to data portabilityThis is the ability to take data from one platform to another platform. The Controller (read: our client) must ensure that these rights are met. We as iRaiser only fill a role in this after consultation and approval from our customer. Thus, we have built functionalities within the iRaiser framework that largely automate the processes for the above rights. This is described in the agreement we enter into with a client.Express consentWhen and Users give permission (consent) for the storage of personal data anywhere within the iRaiser platform, a number of things are stored in the database to be able to resolve any dispute later. This explicit consent is also called informed consent or informed consent.This explicit consent is also called informed consent.The following data will be storedid of the user (to retrieve the information)consent text (which can be managed in the dashboard)date/timeversion number of the general terms and conditionsversion number of the cookie statementversion number of the privacy settingsdata subjects' rightsEvery person whose personal data is stored has a number of different rights under the GDPR legislation to view or delete his/her data. Below we explain how we handle the different rights within iRaiser and what you or the Users can/should do to make use of these rights.Users with an account can log in via the dashboard itself to exercise these rights. One does this by going to Accounts > Data protection when logged in: Following this, they enter the dashboard where everything is explained about their rights and they can request different downloads for each right:  Right of access This right allows everyone to control whether, and how, their data is processed.Procedure UsersUsers can use the dashboard (see image above) to download their own archive containing all their data. After clicking on the button Download my archive , the user receives a message "Archive is being created now. You will soon receive an e-mail containing a link to download your archive." The link in the e-mail is valid for 24 hours.Procedure ClientsWhen a customer addresses you and does not want to or cannot log into the dashboard himself, you (customer) can do so.To do so, go to Accounts > Users and click on the three dots behind the relevant user and go to Data Protection: If a contributor asks this question then a request must be sent by you (customer) in writing on behalf of the requestor(consumer) to iRaiser via iRaiser's support desk.After receiving the request, iRaiser will contact the customer to verify the request. In doing so, iRaiser asks for identification of the customer which is recorded in a logging.After verification of the request, iRaiser will, within 5 working days, collect all the data of the requester (consumer) and bundle it in a password-protected zip file.The password-protected zip file will be sent by iRaiser to the customer by secure WeTransfer.We will send the corresponding password to open the zip file by SMS.Right to rectification and completion and/or restriction of processing When someone has used their right of inspection and comes to the conclusion that their data needs to be corrected, they can submit a request to that effect to the person responsible for data processing; the Controller (read: you as iRaiser's customer of iRaiser). You can already adjust a lot of data yourself via the dashboard at fer the user's request.Should you not be able to change the data via the dashboard please contact support  via a written request on behalf of the applicant(consumer).  After receiving the request, iRaiser will contact you as customer to verify the request. In doing so, iRaiser will ask for identification of the customer which will be logged. After verifying the request, iRaiser will change the data within 5 working days and notify the customer accordingly.Right to erasureUsers with accounts can request the deletion of their personal data themselves. After clicking the "Delete personal data" button, they will receive an email about this and can still withdraw the request within a week. After that, all data will be irrevocably deleted. You as a customer can also trigger this customer request via the dashboard:To do so, go to Accounts > Users and click on the three dots behind the user in question and go to Data Protection.If a user cannot log in themselves or does not have an account, we can do so at the klnat's request. At the request of Data Subject (End User):There are three possibilities for this:The data subject/end user addresses the request to the customer. Customer orders deletion to iRaiser;The affected/end user uses the option for deletion of his/her personal data via the iRaiser Dashboard (option: Data Protection).The affected/end user addresses the request directly to us.iRaiser deletes Personal Data on dedicated servers and any hosted servers and from (internal) mailboxes, and other systems completely and irrevocably within 14 working days after being ordered to do so by customer. Within 30 days, Personal Data will be deleted from backup copyëns and from backup files. Upon termination of contract:If it is established after the end of the contract that the customer possesses all acquired Personal Data, iRaiser will completely and irrevocably delete all Personal Data on dedicated servers and any hosted servers and from (internal) mailboxes within 14 working days of being ordered to do so by the customer. Within 30 days, Personal Data will be removed from backup copyëns and from backup files.Netherly 3 months after termination of the agreement, iRaiser will completely and irrevocably anonymise all acquired Personal Data, whether or not it has received an order to do so from  the customer. iRaiser will inform Customer two weeks prior thereto.The account manager (sales consultant) of the relevant customer is responsible within iRaiser for initiating this procedure. Right to data portabilityWhen a user wants to take their data with them, they can do so by downloading a file containing their data. This works exactly the same as with the Right of Inspection. Procedure ClientsIf a customer contacts you and does not want to or cannot log into the dashboard themselves, you (customer) can do so.To do so, go to Accounts > Users and click on the three dots behind the relevant user and go to Data Protection.If a contributor asks this question then a request must be sent by you (customer) in writing on behalf of the requestor(consumer) to iRaiser.After receiving the request, iRaiser will contact the customer to verify the request. In doing so, iRaiser will ask for identification of the customer which will be recorded in a logging.After verification of the request, iRaiser will, within 5 working days, collect all data of the requester (consumer) and bundle it into a password-protected zip file.The password-protected zip file will be sent by iRaiser to the customer via secure WeTransferPlus.The corresponding password to open the zip file will be sent in a separate email.After verification of the request, iRaiser will contact the customer to collect and bundle all data of the requester (consumer) into a password-protected zip file.Questions?Do you still have questions about the GDPR within iRaiser after reading this information? Then send an email to iRaiser

It may happen that people want to register, for example for an event, but do not want to create a separate Fundraising page for this purpose. In such a case, you can set the sponsor page to be optional. You set this up by going to the level where you want to set this up and then going to Settings > Fundraising page optional and choosing to make Fundraising page optional there. In the Sign up flow, the step where you create the Fundraising page will have a slider:If you create the action page, the slider will appear at the step where you create the action page.If you then click this slider you can continue without creating a Fundraising page:After completing the registration, the participant will receive the 'Welcome email after signing up participant'. If he/she has joined a team then he/she will receive the 'Welcome email after joining team'. If E-tickets are used then the participant will also receive the e-tickets. A participant will appear as 'registration' in the action overview after completing the registration:A participant can still create a sponsorship page if desired, by going to 'My Registration' and clicking on 'Create a sponsorship page'.On the platform, you can see the participants by going to the Overview of Participants. That defaults to /participants.