Privacy Policy & Data Processing Notice
How Asimovx Technologies AB processes, protects, and retains personal data on the Deeyam platform.
Notice Concerning Legal Review & Statutory Compliance
This document is a structured, production-oriented privacy and data processing disclosure drafted for formal review by qualified Swedish legal counsel (advokat or jurist). Neither this document nor platform documentation constitutes legal advice or guarantees statutory compliance, as GDPR determinations depend upon actual technical configurations, physical data flows, and ongoing operational practices.
1. Data Controller Identity
Under Article 4(7) of the General Data Protection Regulation (Regulation (EU) 2016/679 - "GDPR"), the primary Data Controller for personal data processed through Deeyam is:
2. Processing Activities & Retention Schedule
In accordance with GDPR Article 13 and Article 30, the table below delineates the specific categories of personal data processed, the specific operational purpose, the applicable legal basis under GDPR Article 6(1), and the strictly defined data retention period.
| Processing Purpose | Categories of Data | Legal Basis (GDPR Art. 6) | Retention Period |
|---|---|---|---|
| Account Creation & AuthenticationPlatform user profiles, credentials & identity | Full name, email address, password hash (argon2/bcrypt), profile picture, professional title/bio, timezone, preferred language. | Art. 6(1)(b)Contract Performance (Platform Terms) | Maintained for the duration of the active account plus a 30-day grace period post-account deletion request to facilitate dispute resolution and operational purging. |
| Consultation Bookings & Session Metadata1:1 schedule facilitation & technical routing | Scheduled time slot, service title, calendar event IDs, WebRTC peer connection telemetry (IP address, packet loss, bandwidth). Ephemeral Media Streams: Audio and video streams are transmitted point-to-point via WebRTC mesh / relay servers and are NOT recorded or persisted by default. | Art. 6(1)(b)Contract Performance & Art. 6(1)(f) Legitimate Interest (service quality) | 90 days for technical session diagnostics, network connection logs, and scheduling disputes. Purged automatically upon expiry. |
| Financial & Statutory BookkeepingPayment receipts, commission invoices & payouts | Invoice ID, transaction amounts, VAT breakdown, Stripe charge/transfer IDs, payer/payee legal name and billing address, business establishment country, VAT registration status and VAT number where applicable, declaration and validation timestamps. Seller onboarding also collects a tax identification number and tax residence for seller tax reporting (DAC7), where applicable. Expert billing details are reused from onboarding for platform fee invoices. The billing address, country and applicable VAT ID are sent to Stripe Tax to calculate VAT on Deeyam's commission and processing fees. We retain the billing snapshot used for each transaction with its accounting records. These details are not displayed on public expert profiles and are not an application for admin approval to sell. | Art. 6(1)(c)Legal Statutory Obligation (Bokföringslagen (1999:1078)) | Retained strictly for the statutory period mandated by Swedish bookkeeping legislation (currently the remaining calendar year plus 7 years under Bokföringslagen 1999:1078).*Non-financial metadata, user messaging, and user profiles are expressly excluded from this statutory retention period and are erased earlier. |
| Security Monitoring & Error DiagnosticsAbuse prevention, rate limiting & server health | IP address, User-Agent header, request URL paths, HTTP status codes, timestamp, crash stack traces. | Art. 6(1)(f)Legitimate Interest (Network and information security, Art. 32 GDPR) | Rolling retention window of 14 to 30 days, after which server logs are automatically overwritten or anonymized. |
| Consent-Based Analytics & PreferencesPlatform performance & interface enhancements | Aggregated click patterns, navigation flows, cookie identifiers, UI theme preferences. | Art. 6(1)(a)Explicit Consent (Swedish LEK & GDPR) | Valid for up to 12 months or until consent is withdrawn by the user via our Cookie Settings modal. |
Google Calendar Integration
Access and use. Connecting Google Calendar is optional. When you connect it, Deeyam requests Google authorization to read and manage calendar events. The current integration uses your primary calendar to check busy periods, support availability management, and create, update, or delete events associated with Deeyam bookings. Where applicable, Deeyam also creates Google Meet joining links.
Calendar permissions. Deeyam requests two Google Calendar scopes: https://www.googleapis.com/auth/calendar.events to read and manage calendar events for availability and bookings, and https://www.googleapis.com/auth/calendar.events.freebusy to check when your calendar is busy. These permissions can apply to calendars you can access, although this integration uses your primary calendar. Google sign-in is a separate feature and requests identity information.
Deeyam processes event identifiers, titles, descriptions, start and end dates and times, event status, availability information, and event links. Calendar event responses may contain additional event details. Deeyam uses this information for its calendar and booking features.
Storage. Deeyam stores an encrypted Google refresh token to maintain the connection without requiring authorization for each operation. It also stores booking-to-event identifiers, synchronized event identifiers, start and end times, event status, and synchronization metadata. Event titles and descriptions are processed for availability management; the synchronized availability cache stores event identifiers, times, and status.
Data protection. Google refresh tokens newly stored by Deeyam are encrypted using AES-256-GCM, with the encryption key configured separately from the stored data. Deeyam communicates with Google's OAuth and Calendar APIs over HTTPS. Access to calendar integration features is restricted to authenticated accounts, and calendar connections are associated with the signed-in expert. Disconnecting removes the connection data described below from the active database.
Sharing. Deeyam sends booking details to Google to create or update calendar events and, where applicable, generate Google Meet links and invitations. Booking event details can include the service title, participant names, booking code, session times, and meeting link. Where invitations are used, attendee names and email addresses are also sent to Google. Calendar information is processed through the hosting and database providers listed in this policy to operate the integration.
Disconnecting and deletion. Disconnecting Google Calendar in Deeyam deletes the stored Google refresh token, connection records, synchronized availability events, and synchronization state from Deeyam's active database. Disconnecting does not itself revoke Deeyam's authorization in your Google Account or delete events already created in Google Calendar. You can separately remove Deeyam's access through your Google Account's third-party connections settings. Booking records, including calendar event identifiers and meeting links, are handled separately under the booking retention provisions of this policy. To request deletion of other retained personal data, contact privacy@deeyam.com.
Google API data use. Deeyam's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Google Calendar data is used only to provide or improve the calendar and booking features described here. We do not sell it, use it for advertising or creditworthiness decisions, or transfer it except as permitted by Google's Limited Use requirements. Human access is limited to the exceptions allowed by those requirements, including your affirmative agreement to access specific data, necessary security investigations, legal obligations, or permitted aggregated internal operations.
3. Stripe Connect Roles & Payment Data Flows
We integrate Stripe Connect (using Destination Charges architecture) to process payments from clients and facilitate split payouts to independent experts. Under GDPR, Stripe’s legal role varies depending on the specific activity:
When a client inputs card details, they are tokenized directly via Stripe Elements. Asimovx Technologies AB never receives or stores raw PANs, CVVs, or full cardholder data. For the execution of the payment transaction, Stripe acts as a Data Processor on our behalf.
Stripe analyzes transaction signals across its global merchant network to detect fraudulent patterns. For this fraud detection and risk scoring processing, Stripe acts as an Independent Data Controller under its own global privacy commitments.
When independent experts onboard to receive payouts, Stripe collects identity documentation, national tax IDs, and bank details to satisfy statutory Anti-Money Laundering (AML) and Know-Your-Customer (KYC) directives. For these regulatory verification activities, Stripe acts as an Independent Data Controller.
Transactions will appear on client statements under the descriptor format DEEYAM* [EXPERT], providing clear identification of the marketplace intermediary and specific expert consultation.
4. Data Processors & Subprocessor Directory
We engage third-party subprocessors to deliver specialized cloud infrastructure, authentication, email delivery, and media transport. In accordance with GDPR Article 28, all subprocessors are bound by executed Data Processing Agreements (DPAs) with strict security covenants.
Stripe Payments Europe, Ltd. / Stripe Inc.
Payment processing, card tokenisation, payouts to experts (Stripe Connect), fraud prevention and expert identity (KYC/AML) checks
Supabase Inc.
Managed PostgreSQL database and file storage (profile images)
Vercel Inc.
Website hosting and serverless application execution
Google LLC (Firebase Authentication; Google Calendar / Meet)
Sign-in and session security; reading calendar events and availability, synchronizing booking events, and creating Google Meet links when an expert connects Google Calendar
Resend, Inc.
Sending transactional email (booking confirmations, cancellations, receipts)
6. Automated Decision-Making & Profiling (GDPR Art. 22)
We do not employ automated decision-making or profiling systems that produce legal effects concerning you or similarly significantly affect you under Article 22 of the GDPR.
Marketplace search rankings and expert recommendations are generated based on transparent, objective parameters including explicit search filters, schedule availability, expert category tags, and verified client review averages.
7. Your Rights Under GDPR (Articles 15–22)
As a data subject located within the European Economic Area, you hold statutory rights enforceable against Asimovx Technologies AB:
Right of Access (Art. 15)
Obtain confirmation of processing and a machine-readable copy of your personal data.
Right to Rectification (Art. 16)
Request immediate correction of inaccurate or incomplete personal records.
Right to Erasure / "To Be Forgotten" (Art. 17)
Request erasure where data is no longer necessary, excluding records legally required by Bokföringslagen.
Right to Restriction of Processing (Art. 18)
Request that data processing be temporarily restricted while disputes or claims are verified.
Right to Data Portability (Art. 20)
Receive your profile and booking records in a structured, commonly used JSON/CSV format.
Right to Object & Withdraw Consent (Art. 21 & 7(3))
Object to legitimate interest processing or withdraw cookie/marketing consent without penalty.
9. Profile Accuracy & Anti-Impersonation
To ensure trust and safety across the Deeyam platform, all users must provide strictly truthful and accurate information regarding their identity, credentials, certifications, titles, and professional experience.
While we process identity and credential data to verify experts and facilitate a safe marketplace, any deliberate misrepresentation constitutes a material breach of our terms and compromises the integrity of our platform.