Impact-Site-Verification: 4d2cfbdf-2457-4b3e-9d2b-371c9c0743c9

Privacy and data protection

Updated: 4 November 2026 · Version: 2026-11-04-privacy-cookies

At Kalenda, we process your personal data in order to provide the service. Here we explain what data we use, why we use it, how long we keep it and what rights you have.

1. Data controller

Controller: Paula Aharonian. Tax ID: 46436615Y. Address: Esteve Terradas 31, 08023 Barcelona, España. Contact email: info@ka-len-da.com.

2. Data we process

Account data: your name, email address, profile photo if you sign in through an external provider, and information about your plan and monthly AI-processing usage.

Content you provide: the text, images, links or screenshots you submit to capture an event, and the resulting event data (title, date, time, location, description, category and source link).

When you choose to use the clipboard, Kalenda reads the text you copied to prepare the capture. The content is sent for analysis only when you request processing. Avoid copying or uploading passwords, health data or other private information that is not needed for the event.

Sharing data: if you explicitly create a sharing link, Kalenda stores a separate copy of the event associated with an opaque link token so that anyone who has that link can view the included information.

Affiliate ticket-link usage: normal ticket links do not create a Kalenda click record. If Kalenda has applied an affiliate link, it records only the destination provider and domain, that the link was affiliate and the interface source. This record does not include the full URL, its parameters, the event identifier or a Kalenda account identifier. The destination and attribution providers may still generate their own technical records.

Technical and usage data: Base44 and other infrastructure providers may generate necessary service, security and request logs when Kalenda is used. Separately, only if you accept optional analytics in the cookie controls, Base44 can measure visits and use of Kalenda using page paths, visit timing and duration, referral and campaign information, an analytics session identifier and your user ID when signed in. Optional analytics starts disabled. You can withdraw your choice in Cookie settings. Some reports are aggregated; the underlying records are not necessarily anonymous.

Payment data: if you subscribe to Plus, Wix processes payment. Kalenda does not receive your full card details. It retains the purchase email, transaction and subscription references, amount, currency, status and relevant dates for subscription management and legal records.

3. How we use the data

To create and maintain your account, save your events and let you access them from any device.

To process the content you submit and extract event information from it using artificial intelligence.

To apply the monthly processing limit associated with your plan and, if you subscribe to Plus, manage the subscription.

To send you service-related communications and, only where you have authorised it, informational or commercial communications.

Optional email preferences are separate: Kalenda news, tips and promotions; and event suggestions based on interests and an optional city you explicitly select. Both start disabled. You can enable either, both or neither, and change or withdraw each choice in My account or through the unsubscribe link in the relevant email. These preferences do not control essential account or payment messages, and are separate from saved-event summaries.

For event suggestions, Kalenda uses only the interests and city you choose for that purpose. It does not analyse your saved events or Google Calendar content for these communications, and does not share your contact details with event organisers so they can market to you. An administrator can prepare a recipient list filtered by the choices you have authorised.

When affiliate links are activated, to keep a minimal record of affiliate-link use and support attribution and commission reporting. Normal ticket links are not logged by Kalenda for this purpose.

To detect abuse, protect the security of the service and comply with legal obligations.

4. Legal basis

Performance of a contract: processing is necessary to provide the service you request, including your account, event capture, saved events, requested calendar actions, sharing features and support requests.

Your consent: for optional saved-event summary emails and, independently, for the news/promotions and selected-interest event suggestions you expressly authorise. Optional browser analytics requires a separate choice in the cookie controls. You may withdraw each consent at any time without affecting the lawfulness of earlier processing.

Legitimate interests: for proportionate service security, fraud and abuse prevention, necessary technical diagnostics and strictly limited service measurement where applicable. You may object to processing based on legitimate interests. Optional analytics or profiling that requires consent will not be activated under this clause.

Legal obligations: we also process billing data and other information required to comply with accounting, tax and other legal obligations.

5. How long we keep the data

We keep your account data and your events while your account remains active.

For optional communications we keep a history of your choices, including the statements shown, their versions, language, date, source and any expressly selected interests/city, while your account exists to manage and evidence those choices. Only the latest choice determines eligibility for future communications. Withdrawing permission removes you from the relevant recipient list; deleting your account also deletes this application-level history. Provider logs and backups follow the separate limitations described below.

If you delete your account in My account, Kalenda removes the account, saved events, sharing links, support records, optional-communication history and plan state that it can delete directly, except for information that must be retained by law. It first attempts to cancel subscription renewals and remove any Google Calendar connection; it does not complete account deletion if those steps cannot be confirmed. You can also request erasure by email.

Base44 distinguishes removing a record from permanently deleting it from Recently deleted. Where records remain there, completing an erasure request requires that additional step, which Kalenda will handle with the provider's available tools. Private files, provider logs, analytics and backups follow the separate procedures below; deleting an account does not by itself erase every copy.

If you have subscribed to the Plus plan, billing data (the transaction and subscription references, the email used for the purchase, amount, currency, status and dates) may also be retained after your account is deleted for the period required by applicable Spanish accounting and tax law. This does not include your full card details or the content you saved, and is used only to meet accounting and tax obligations and to provide evidence of payments made.

Images submitted to capture an event are stored privately. Temporary signed links used for processing normally expire after five minutes; their expiry does not delete the stored file. The uploaded image is not attached to the saved event. Kalenda retains a private file reference associated with your account so it can manage access and deletion requests. Base44 has confirmed that files uploaded through the live application cannot currently be permanently deleted using a self-service control or API: deletion must be requested from its support team using the permanent file reference and the app name. Deleting an event or account alone does not delete that file. When you delete your account, Kalenda marks the references for deletion handling; it retains only the information needed to identify the pending files until deletion is confirmed, then minimizes those records. To request deletion of an uploaded image, contact info@ka-len-da.com. Kalenda will coordinate the request with Base44 and inform you of its outcome. Any backup copies follow the provider's retention rules.

Provider logs may include activity identified by email address. Base44 has confirmed that app owners cannot delete those log entries. Its analytics use a user ID and are automatically deleted after 60 days. Base44 has not specified to Kalenda a fixed retention period for all Builder infrastructure logs or internal backups. The periods published for the separate Backup & Restore feature on other plans should not be read as Builder's retention period. Under the DPA, data retained in backups or because of legal requirements remains protected and is not used for other purposes while awaiting deletion. For a rights request affecting these records, Kalenda will seek the provider's assistance and explain any applicable retention or deletion limits.

A shared event copy is created only when you explicitly generate a sharing link. Anyone with that link can view and forward the included information. The link does not currently expire automatically. You can revoke it from the Share window, and deleting the original event revokes its active link. Editing the original event does not update an existing shared copy unless you choose Update link.

6. Google Calendar integration and Google data

If you choose to connect your Google Calendar account, Kalenda requests permission to create and manage in your calendar the events you choose to save from the application. The integration is activated only when you explicitly connect it.

In the current implementation, Kalenda uses Google Calendar access to create in your calendar the events you request. Kalenda does not read or use the general content of your existing Google Calendar events for profiling, advertising, analytics or purposes unrelated to this functionality.

The calendar.events permission technically allows viewing and modifying events in your calendars. Kalenda currently uses it to create the events you choose in your primary calendar. There is no two-way synchronisation: editing or deleting an event in Kalenda does not update or remove its copy in Google Calendar, and saving it again may create another copy.

Data received through Google APIs, including authentication and authorisation data required to maintain the connection, is used exclusively to provide the requested functionality. We do not sell Google user data or use it for advertising, profiling, credit decisions or other purposes unrelated to the integration.

Kalenda shares data needed for the Google Calendar integration with Google to carry out your requested calendar actions and with Base44 to manage the OAuth connection and application infrastructure. Kalenda does not send that data to advertisers or event organisers. Base44's workspace-wide processing conditions are explained in section 8.

Kalenda does not provide artificial intelligence services with user data obtained through Google Workspace APIs. Kalenda's artificial intelligence processes only content the user voluntarily provides to prepare an event, such as text, images or URLs, before the user decides to save it to Google Calendar.

Kalenda's application code does not use Google Workspace API data, including derived data, to train general-purpose or foundation AI models. Base44 has stated that Google Calendar data stored in the workspace follows its general training policy, subject to the DPA conditions described in section 8. This is a statement of the provider's policy, not confirmation that particular Google data has been used for training or that every training use is preceded by anonymization.

Use and transfer of information received from Google Workspace APIs are subject to the Google API Services User Data Policy and its Limited Use requirements. This privacy notice does not grant permission for uses prohibited by those requirements, including training beyond the specific user's permitted personalized use case.

Kalenda does not receive or store your Google password. Authorisation is carried out through OAuth and the connection is managed through Base44 infrastructure.

You can disconnect Google Calendar in My account. Base44 has confirmed that disconnecting from Kalenda removes that user's token stored by Base44. To also withdraw authorization on Google's side, remove Kalenda's access in your Google Account under Security / third-party connections. These are separate actions. Deleting a Base44 app user alone does not disconnect their connector, so Kalenda attempts the disconnect before deleting your account and aborts if it cannot confirm that the connection was removed. Events already created in Google Calendar remain there.

When you choose Outlook / Microsoft 365, Kalenda builds a web link containing the event details you selected (such as title, date, time, description and location); those details are sent to Microsoft when you open that link. The Apple Calendar option downloads an .ics file to your device for you to import into a compatible calendar.

7. Chrome extension

If you install the official Kalenda extension for Chrome, the extension uses only the URL of the active tab when you explicitly click the “Save to Kalenda” icon. That URL is sent to Kalenda to prepare the event you want to review and save.

The extension does not read your browsing history, does not automatically inspect the content of other pages, does not capture URLs in the background and does not track your browsing. Access to the active tab occurs only as a result of your action when you click the extension icon.

8. Who can access your data

We do not sell your data. Kalenda runs on Base44 infrastructure for hosting, database, backend functions, authentication, integrations and platform service/security logs. The event-capture flow calls Base44 Core.InvokeLLM; Kalenda's code does not select a specific underlying model provider. Transactional emails are sent through Base44 Core.SendEmail. The current application code does not call Google Analytics, Meta Pixel or Hotjar.

Kalenda Plus checkout and subscription operations use Wix services. Kalenda stores transaction and subscription references, status, amount, currency and purchase-related email where needed for the subscription and legal records; it does not receive your full card details.

Kalenda runs on Base44 Builder. Base44 has confirmed that workspace data can be used to develop and train its internal AI/ML models. This covers database records, forms, uploaded files and connector data, not only content sent to Core.InvokeLLM. Builder and Business have no training opt-out; Enterprise excludes the entire workspace automatically. Calling an external AI API instead does not change that workspace-wide policy. Base44 has separately stated that it does not use customer data to train third-party AI models.

This policy is subject to Base44's Data Processing Agreement (DPA): it limits personal-data use to providing the services, use after complete anonymization removing personal attributes, or use in aggregate. These are the contractual conditions communicated by Base44; Kalenda does not claim that all training uses are necessarily preceded by anonymization. Please do not submit passwords, health information or other private or sensitive material unnecessary for the event.

Optional marketing permissions cover only the communications described in section 3. They are not consent to train AI models; accepting this privacy notice is not separate consent to that purpose.

Base44 publishes the AI service providers it may use for Core.InvokeLLM, but has not yet confirmed which provider handles a given call or the retention period for prompts and outputs. Base44 has also confirmed that Builder data is stored in the United States by default; an EU/UK storage region is available only on Business and Enterprise plans and does not necessarily determine where processing occurs.

The AI extraction flow written by Kalenda processes content you submit before the requested save to Google Calendar. Kalenda does not feed the contents of your existing calendar into that extraction flow. This separation in application code does not amount to a provider-wide training exclusion; Base44's stated workspace policy also covers stored connector data.

If an affiliate link is activated, opening it may take you through an attribution network before reaching the seller. That network and the destination platform may process technical visit and purchase data for attribution under their own privacy notices and any applicable consent requirements. Kalenda does not send Google Workspace data through this affiliate flow.

Base44 has confirmed that vendors receiving personal data are subject to data-processing terms and that international transfers may rely, as applicable, on adequacy decisions, Standard Contractual Clauses or the Data Privacy Framework. The current DPA and subprocessor list are available through Base44 and its Trust Center. Some processing may therefore take place outside the European Economic Area.

9. Your rights

You can exercise your rights of access, rectification, erasure, objection, restriction of processing and data portability by writing to info@ka-len-da.com. You may withdraw consent at any time without affecting the lawfulness of earlier processing, and you may object to processing based on legitimate interests. You do not need to keep an account open in order to submit a rights request.

We may ask for information reasonably necessary to verify your identity. We will normally respond to a rights request within one month of receipt. If the legal conditions for an extension apply, we will notify you within that first month and explain the reasons; the extension may be up to two further months. Erasure is subject to applicable legal exceptions; if any data cannot be deleted immediately, we will explain what is retained and why.

You may lodge a complaint with Spain's Agencia Española de Protección de Datos (AEPD) or with the competent data protection authority in your country of habitual residence, work or the place of the alleged infringement.

10. Security

We apply reasonable technical and organisational measures to protect your information. Saved events are restricted to your account by default; copies you explicitly share through a sharing link are accessible to anyone who has that link until it is revoked.

11. Children

Kalenda is not designed as a child-directed service. We do not currently operate an age-verification or parental-authorisation flow. The minimum age and contractual capacity requirements can vary by country; those requirements must be defined before Kalenda is deliberately offered to minors.

12. Provider documentation

You can consult Base44's DPA, Terms of Service, privacy and training documentation, user-data deletion guide and Trust Center. These references explain the provider's conditions and do not limit your rights against Kalenda.

Your cookie preferences

We use necessary storage to keep your session, language and cookie choices. With your permission, Base44 can also measure visits and how Kalenda is used. Optional analytics stays off until you accept. Cookie policy.

You can change your choice at any time using “Cookie settings” in the footer or app menu. Your choice lasts up to 180 days.