Aiploya Logo
    Legal
    Last updated: 13 November 2026Deutsch (Datenschutz)

    Privacy Policy

    This Privacy Policy explains how Aiploya, a product of DIIF-KI – Deutsches Institut für Künstliche Intelligenz GmbH, processes personal data on its website, in its platform and in connected third-party integrations.

    1

    Controller

    The controller for the processing of personal data in connection with the Aiploya website, platform and services is:

    DIIF-KI – Deutsches Institut für Künstliche Intelligenz GmbH

    Franz-Lehner-Straße 3, 85716 Unterschleißheim, Germany

    Email: kontakt@diifki.com

    Phone: +49 89-41611233-0

    Commercial register: HRB308641 (Local Court of Munich)

    VAT ID: DE460300686

    2

    Privacy contact

    For all data protection matters, including requests regarding your rights, please contact us at kontakt@diifki.com or by post at the address above.

    Data protection contact

    David Nann

    DIIF-KI – Deutsches Institut für Künstliche Intelligenz GmbH

    Franz-Lehner-Straße 3, 85716 Unterschleißheim, Germany

    Email: kontakt@diifki.com

    Phone: +49 89-41611233-0

    David Nann is also the contact person for users outside the European Union for all questions regarding this Privacy Policy and the exercise of data subject rights.

    3

    Scope

    This Privacy Policy applies to:

    • the Aiploya website
    • the Aiploya web application
    • user and organization accounts
    • recruiting, applicant management and talent functions
    • social media integrations (for example TikTok, Meta, Facebook, Instagram)
    • other connected services and integrations

    This English version is provided for information and for international app and API reviews. The German version is authoritative: Datenschutzerklärung (German).

    4

    Roles: Aiploya, companies and applicants

    For our own website, accounts and platform operation we act as controller. Where a customer company uses Aiploya to process applicant or employee data in its own recruiting and HR processes, that company is the controller and we act as processor on its behalf under a data processing agreement (Art. 28 GDPR).

    5

    Categories of personal data

    Account data: name, email address, organization, role and permissions, login and account information, preferences.

    Recruiting data (where applicable): applicant and candidate information, CV and profile data, application data, qualifications, skills, communication history, interview and process information, notes and evaluations created by the customer organization.

    Technical data: IP address, browser and device information, server and application logs, timestamps, error reports and security events.

    Demo with your company: if you request a demo with your own company, we process your business email address, your name (optional) and the website you provide. For this we only read publicly accessible pages of your website and public job portal (e.g. imprint, careers page, job ads; robots.txt is respected) and use company name, industry, locations, size and open positions solely for this private demo. All applicants, employees and talents in the demo are fictitious. The request and demo data are deleted no later than 30 days after the demo expires; unconfirmed requests after 30 days.

    Social media integration data: when a user voluntarily connects an external platform such as TikTok, Meta/Facebook or Instagram, we may process data returned by that provider, depending on the permissions granted:

    • platform user or account identifier
    • display name and basic profile information
    • connected business account information
    • Facebook Page identifiers
    • Instagram professional account identifiers
    • TikTok account identifiers
    • advertising account identifiers (where advertising features are used)
    • granted permissions/scopes
    • access tokens
    • refresh tokens
    • token expiry information
    • identifiers of published content and posts
    • campaign identifiers and campaign performance data
    • lead information, where explicitly authorized
    6

    OAuth authorization

    • You authenticate directly with the third-party provider (for example TikTok or Meta) on that provider's own login and consent screens.
    • Aiploya does not receive and does not store your TikTok, Facebook, Instagram or Meta password.
    • After you approve the requested permissions, the provider returns OAuth credentials (access token, where applicable a refresh token and expiry information) to our backend.
    • These tokens are used solely to perform the actions you authorized, for the features you enabled.
    7

    Purposes of integration data processing

    • establishing the connection to a social media account
    • displaying which accounts are connected
    • publishing content requested by users
    • scheduling posts
    • retrieving post and publishing status
    • managing authorized advertising campaigns
    • retrieving campaign and content analytics
    • importing authorized leads
    • maintaining the connection and refreshing authorization tokens
    • detecting, logging and troubleshooting integration errors
    8

    Legal bases

    • Art. 6(1)(b) GDPR – performance of a contract: account management, provision of the platform and the features you use, including connected integrations.
    • Art. 6(1)(a) GDPR – consent: optional analytics/marketing cookies, newsletters and voluntary connection of third-party accounts where consent is the appropriate basis. Consent can be withdrawn at any time.
    • Art. 6(1)(f) GDPR – legitimate interests: security, abuse prevention, logging, error analysis and product improvement.
    • Art. 6(1)(c) GDPR – legal obligations: statutory retention and documentation duties.
    • Art. 28 GDPR – processing on behalf of customer companies for their recruiting and HR data.

    For users in Switzerland, the Swiss Federal Act on Data Protection (revFADP) applies in addition where relevant.

    9

    TikTok Integration

    • Users of a customer organization may voluntarily connect their own TikTok account to Aiploya.
    • Authentication takes place through TikTok's own authorization process; we never see your TikTok password.
    • Aiploya requests only the scopes required for the features enabled in the organization (for example basic account information and content publishing).
    • We may receive a TikTok account identifier and basic account information such as the display name.
    • Where publishing is enabled, Aiploya may transmit content selected by the user (video or media URL, caption, hashtags) to TikTok.
    • Content is only published when an authorized user initiates or confirms the publication in Aiploya.
    • Users can disconnect TikTok from Aiploya at any time in the social recruiting area of the platform.
    • TikTok remains an independent third party; TikTok's own privacy policy and terms apply in addition.
    10

    Meta, Facebook and Instagram Integration

    • Users can connect their own business accounts, Facebook Pages and Instagram professional accounts.
    • Authorization takes place through Meta OAuth / Facebook Login for Business.
    • Aiploya may receive Page IDs, Instagram professional account IDs, advertising account IDs, the granted scopes and the authorized tokens.
    • Depending on the permissions granted, Aiploya may publish content, retrieve insights and post statistics, manage advertising campaigns and retrieve leads.
    • Users control which accounts and pages they connect and can disconnect them at any time.
    • Meta remains an independent third party; the Meta privacy policy and platform terms apply in addition.
    11

    Tokens and credentials

    • Access and refresh tokens are treated as confidential credentials.
    • They are stored server-side in our backend database and are not sent to the browser or exposed in the front end.
    • Access is restricted to privileged backend service processes; regular application users and other customer organizations cannot read them.
    • Organization-level access controls (row-level security and permission checks) are applied to connection records.
    • Tokens are refreshed automatically where the provider supports refresh tokens.
    • Transport is protected by TLS. Data at rest is protected by the encryption provided by our database and hosting infrastructure; tokens are not additionally encrypted at application level.
    12

    Multi-tenant separation

    Connected social accounts, tokens, posts and campaign data belong to the specific Aiploya organization that created the connection. Data of different customers is separated technically and organizationally through tenant identifiers, row-level security policies and role-based permissions. One organization has no access to another organization's social connections or connected account data.

    13

    Data sharing and processors

    We use service providers in the following categories, based on data processing agreements pursuant to Art. 28 GDPR:

    • Hosting / infrastructure: Hetzner Online GmbH (Germany, Falkenstein data centre) – website, database, file storage and sign-in, operated by us on our own servers.
    • Authentication and application backend: our own platform backend components.
    • AI providers: Mistral AI SAS (France, processing in the EU; no training on submitted data). Optional, only if voice features are enabled: OpenAI Ireland Ltd. (Ireland/USA, EU Standard Contractual Clauses).
    • AI without personal data: Google Cloud (Vertex AI, Google Ireland Ltd., Frankfurt region) – only for content without personal data (e.g. blog images, public texts). All AI processing involving personal data runs exclusively via Mistral AI, enforced by our own AI gateway.
    • HR system connection: Kombo (interface provider kombo.dev, EU instance) – only if a company connects its applicant tracking or HR system; job and application data from that system are transferred.
    • DNS: Cloudflare (name resolution only; page requests and content do not pass through Cloudflare).
    • Social media platforms: TikTok, Meta (Facebook, Instagram) for the integrations you connect.
    • Email, CRM, support, forms, calendar, e-signature: Zoho One applications (CRM, Desk, Forms, Bookings, Campaigns, Sign), Google Calendar/Meet, Microsoft 365/Teams, Zoom, Calendly, Cal.com.
    • Payments: Stripe Payments Europe Ltd. (Ireland); PayPal (Europe) S.à r.l. et Cie, S.C.A. (Luxembourg) if you choose to pay with PayPal.
    • System and sign-in emails: Scaleway SAS (France; sending from data centres in Paris, EU); as a fallback and for recipients of certain mailbox providers (e.g. GMX, WEB.DE): Sendinblue SAS/Brevo (France; processing in data centres in the EU).
    • Analytics: Google Analytics/GTM, Matomo, Microsoft Clarity, Hotjar, PostHog, Plausible, Zoho Analytics – only to the extent covered by your cookie consent.
    • Cookieless audience measurement: Umami (open source), self-hosted on our own server at Hetzner Online GmbH, Germany – no cookies, no disclosure to third parties.

    The list above reflects the subprocessors currently in use, including their countries of processing.

    14

    International transfers

    We aim to process personal data within the EU/EEA. Where processing takes place in third countries, we ensure appropriate safeguards:

    • adequacy decisions of the EU Commission
    • EU standard contractual clauses
    • technical and organizational protective measures
    • encryption in transit
    • access restrictions
    • contractual audit rights
    • risk assessments and transfer impact assessments

    Social media platforms such as TikTok and Meta are independent controllers for their own processing and may transfer data internationally under their own policies.

    15

    Mobile apps, push notifications and purchases via Google Play

    Aiploya is also available as Android apps: “Aiploya” for applicants and “Aiploya Business” for users of a company account. The apps show the same content as aiploya.com and this Privacy Policy applies. In addition:

    Installation: you obtain the apps from Google Play (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). Google's terms and privacy policy apply to downloads, updates and purchases; Google processes your account data as an independent controller.

    Sign-in on the device: the apps store your session (access and refresh token) encrypted in the Android Keystore. It is excluded from backups (Google backup, device transfer). If secure storage is unavailable, the session is kept in memory only until the app is closed.

    Permissions: the apps only use internet and network state, notifications (only with your consent) and – if you switch it on – fingerprint or face unlock as a convenience feature. Biometric checks are performed solely by your device; we receive no biometric data. By default the app hides its preview in the app switcher (Android; screenshots inside the app are then blocked as well) – this can be switched off in the app settings. Photos (e.g. of your CV) are taken by your device's camera app; the apps have no camera permission of their own. No location data is collected.

    Push notifications: if you allow notifications, your device receives a device identifier (push token) from Google Firebase Cloud Messaging (Google Ireland Limited). We store this token with your account, the app and the time of last use in order to send you notifications, e.g. about new messages, the status of your applications, interview invitations and new matching jobs or (Aiploya Business) new applications, messages and pending approvals. Notifications contain no message content and no company names, only a neutral hint (e.g. “New message about your application”). Google receives the token and the notification text; a transfer to the USA cannot be ruled out (Google LLC is certified under the EU-US Data Privacy Framework; EU Standard Contractual Clauses also apply). Legal basis: Art. 6(1)(b) GDPR or your consent via the system prompt (Sec. 25(1) TDDDG for access to the device). You can switch notifications off at any time in the app per topic or in the Android settings. We delete the token when you sign out, when you delete your account and when Google reports it as invalid; tokens unused for 12 months are deleted automatically by a daily clean-up job.

    AI processing: personal data is processed for AI features only by providers in the EU and via our own AI gateway, as described in this Privacy Policy.

    In-app purchases in “Aiploya” (Google Play Billing): in the Android app, applicant plans (Starter, Smart, Flat) can only be purchased via Google Play. Google handles payment, invoicing and cancellation; we receive no payment data. If a plan booked on aiploya.com is already active, we do not complete a second purchase (Google refunds it). To unlock your plan we receive and store from Google: purchase token, product and term, status (active, cancelled, expired, refunded), start and expiry, order number and a pseudonymised identifier of your Aiploya account (hash, not plain text). We query the status via the Google Play Developer API and receive status notifications via Google Cloud Pub/Sub. Legal basis: Art. 6(1)(b) GDPR (contract). Google handles billing towards you; we retain the sales and payout reports we receive from Google in accordance with commercial and tax law (Art. 6(1)(c) GDPR). On the web, payments continue to be processed by Stripe.

    Aiploya Business: there are no purchases in the company app. Applicant data shown in the app is processed by your company as controller; Aiploya acts as processor.

    Deletion: you can delete your applicant account in the app under Settings → My data → Delete account or at aiploya.com/konto-loeschen. This also deletes push tokens, notification settings and purchase records. We end a running Google Play subscription via Google (revocation with a pro-rata refund, otherwise cancellation); if that fails in exceptional cases, we ask you to cancel it in Google Play.

    16

    Reporting and blocking messages

    You can report individual messages to the Aiploya team and block senders. For a report we store a reference to the reported message, the selected reason, your optional comment, your account, the company concerned, the time, and the processing status with an internal note. The sender is not told who reported the message. Reported messages are only visible to authorized Aiploya staff (administration and moderation) and only to review the report; every access is logged, and we provide this log to the companies concerned on request. For a block we store who blocked whom and since when. Blocked companies can no longer send you personal messages; if a company blocks a person, that person's new messages are no longer shown in the company's inbox and message history. Notifications about an ongoing application process (e.g. appointments, status, rejection) may still be delivered. Legal basis: Art. 6(1)(b) GDPR and Art. 6(1)(f) GDPR (legitimate interest in protection against harassment, fraud and abuse). Retention: reports until processed and for 12 months afterwards, but no longer than 24 months after receipt, then automatic deletion; blocks until you lift them or your account is deleted. If you delete your account, your reports and blocks are deleted as well.

    17

    Minimum age

    The applicant area (website and app “Aiploya”) may only be used from the age of 16; you confirm your age when registering or once before first use. Anyone who states that they are younger than 16 cannot use the applicant area and can delete their account at any time. Access to a company account (website and app “Aiploya Business”), e.g. for apprentices, is granted by the respective company, which is the controller for that processing.

    18

    Retention

    • Accounts: for as long as the account exists, plus statutory retention where required.
    • Server and security logs: only as long as needed for security and error analysis.
    • Recruiting data: for the duration of the process and afterwards only where documentation or legal obligations require it, or as instructed by the customer organization.
    • Reported messages: reports until processed and for 12 months afterwards, at most 24 months after receipt; blocks until lifted or the account is deleted.
    • App push tokens: until sign-out or account deletion, at the latest after 12 months without use.
    • OAuth tokens: for the duration of the connection. On disconnection they are deleted from our database and, where the provider supports it, revoked.
    • Social connection and post data: post records, tracking codes and statistics remain with the organization's campaign documentation until deleted by the organization or on account deletion.
    19

    Your rights

    • access (Art. 15 GDPR)
    • rectification (Art. 16 GDPR)
    • erasure (Art. 17 GDPR)
    • restriction of processing (Art. 18 GDPR)
    • objection (Art. 21 GDPR)
    • data portability (Art. 20 GDPR)
    • withdrawal of consent at any time (Art. 7(3) GDPR)
    • complaint to a supervisory authority (Art. 77 GDPR)

    Where a customer company is the controller (for example for its applicant data), please address your request to that company; we will support it as processor.

    20

    Disconnecting Connected Accounts

    You can disconnect a connected TikTok, Meta, Facebook or Instagram account from Aiploya at any time in the social recruiting area of your organization's dashboard. Upon disconnection:

    • Aiploya stops using that authorization and no further actions are performed on the account.
    • The stored access and refresh tokens are deleted from our database and revoked where the provider technically supports revocation.
    • Content that was already published on the third-party platform remains there until you delete it on that platform.
    • You can additionally remove Aiploya's access in the app or business settings of the respective platform.
    21

    Account and data deletion

    Registered users can delete their account in the account settings of the platform. Alternatively, you can request deletion of your account and personal data by email to kontakt@diifki.com. We will confirm and carry out the deletion unless statutory retention obligations require continued storage; in that case the data is restricted from further processing.

    22

    Cookies and analytics

    We use technically necessary cookies for operation, security and session handling. Optional analytics and marketing technologies are only used with your consent, which you can give, refuse or withdraw at any time via our cookie settings. Details, including the tools used, are described in the German Privacy Policy and in the cookie settings dialog.

    Cookieless audience measurement (Umami, no consent required): to count visits to our public pages (e.g. home page, blog, job board, career pages) we use the open-source software Umami, which we operate ourselves on our own server at Hetzner Online GmbH in Germany. No data is passed to third parties. Umami sets no cookies and stores nothing on your device. It records the page visited (address only, without parameters), the referring website (domain only), page title, browser, operating system, device type, screen size, language and approximate location (country, region, city). Your IP address is used only briefly to derive this approximate location and a daily rotating anonymous visitor hash and is not stored. Logged-in areas and personalised links are never recorded. We only see aggregated statistics, kept for at most 24 months. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in privacy-friendly audience measurement). You may object at any time (Art. 21 GDPR), e.g. by email to datenschutz@diifki.com, by enabling "Do Not Track" or by blocking scripts from aiploya.com/u/.

    23

    Security

    We apply appropriate technical and organizational measures, including:

    • encryption in transit (TLS) and encryption at rest provided by our infrastructure
    • role and permission management, least privilege
    • multi-factor authentication for privileged access
    • access logging and audit trails
    • tenant separation and row-level security
    • backup and recovery processes
    • security updates and dependency scanning
    • code reviews and secrets management
    • monitoring and incident response processes
    • human oversight of HR-related decisions

    No system can be made completely secure; we make no claim of absolute security or of certifications we do not hold.

    24

    Changes to this Privacy Policy

    We may adapt this Privacy Policy when legal, technical, organizational or product requirements change (for example new features, providers or integrations). Material changes will be communicated appropriately; the current version is always available on this page.

    25

    Contact

    DIIF-KI – Deutsches Institut für Künstliche Intelligenz GmbH

    Franz-Lehner-Straße 3, 85716 Unterschleißheim, Germany

    Email: kontakt@diifki.com

    Phone: +49 89-41611233-0

    Commercial register: HRB308641 (Local Court of Munich)

    VAT ID: DE460300686

    See also our Terms of Service and Legal Notice (Impressum).

    Last updated: 13 November 2026