Privacy Policy
Last updated: October 23, 2026
This English version is a translation provided for convenience. In case of any discrepancy, the German version prevails.
1. Controller
The controller for the data processing on makiro.de and in the makiro application is:
Tojiki — Inhaber Jakob Mayr
Kirchweg 30, 83043 Bad Aibling
Telephone: +49 171 264 95 80
Email: info@tojiki.de
There is no statutory obligation to appoint a data protection officer. For all data protection matters you can reach us at the email address given above.
2. Two roles: our own processing and processing on your behalf
As controller we process the data arising in connection with your user account — registration, use of the application, billing, support.
As processor we process the personal data that you as a user bring into makiro or have processed through the application — in particular the data of your own customers (emails, messages, appointments, documents, bookings via your booking page). For this you are the controller within the meaning of the GDPR; we act exclusively on your instructions. We make a data processing agreement pursuant to Art. 28 GDPR available on request at info@tojiki.de.
3. Hosting and server log files
The application, including the public booking pages, is hosted with Vercel Inc. (340 S Lemon Ave #4133, Walnut, CA 91789, USA). The execution of the server functions is pinned to the Frankfurt am Main region (“fra1”).
When a page is accessed, the hosting provider processes technically necessary connection data (IP address, time, resource requested, referrer, user agent) in order to deliver the page and to secure operations. The legal basis is our legitimate interest in secure and trouble-free operation (Art. 6 (1) lit. f GDPR).
4. User account and sign-in
For signing in we use Neon Auth, a service of Neon Inc. (USA). Processed are your email address, your name (insofar as provided) as well as sign-in times and session information. If you sign in via Google, we receive your email address, your name and your Google user ID from Google; we never receive your Google password. Signing in alone does not give us access to your mailbox, calendar or contacts — you grant that only if you separately connect an account (sections 8 to 10).
The legal basis is the performance of the usage contract (Art. 6 (1) lit. b GDPR). The session is maintained by means of a technically necessary cookie.
When your account is created we store, where present, the campaign identifier of the link you arrived through (utm parameters), the click ID of a Google ad (gclid) and the domain of the page that referred you to us. This tells us which channels bring customers to us. The legal basis is our legitimate interest in evaluating our advertising (Art. 6 (1) lit. f GDPR). Nothing is stored on your device for this; the data is deleted together with your account.
5. Database and storage
Application data is stored in a PostgreSQL database of Neon Inc. with the server located in Frankfurt am Main (AWS region eu-central-1). Particularly sensitive content — messages and subject lines, draft replies and notes, contact details, tasks, conversation transcripts as well as the access credentials for connected accounts — is additionally stored in encrypted form (AES-256-GCM). Which data belongs to which account is enforced by the database itself and not only by the application.
Uploaded and generated files are stored by us in Vercel Blob. Generated documents such as quotes and invoices are kept in non-public storage; access takes place exclusively via access-protected download routes of the application. Images and videos for your posts, by contrast, are kept at a publicly retrievable address with a long random identifier that cannot be guessed. This is necessary because platforms such as Instagram and YouTube fetch the file themselves from this address in order to publish it. We pass the address only to the platform on which you publish; however, anyone who knows it can open the file without signing in.
6. Voice-based onboarding conversations
The onboarding and parts of the application can be conducted as a voice conversation with an AI agent. For this we use ElevenLabs Inc. (USA). Processed are your voice input, the transcript produced from it and the conversation metadata.
Before the conversation begins you are informed that the conversation is being recorded and transcribed and that you are speaking with an AI agent and not with a human being; the processing takes place only after your express consent (Art. 6 (1) lit. a GDPR). You may withdraw your consent at any time with effect for the future.
Raw transcripts and audio references are automatically deleted 30 days after the conversation. Only the structured information derived from them is retained, on which your strategy and content documents are based.
7. Use of AI language models
In order to produce texts, summaries, suggested replies and strategy content, we transmit the content required for this to an AI provider. We determine which provider handles which task on a per-task basis; only the following two are used:
- Mistral AI SAS (15 rue des Halles, 75001 Paris, France) for all tasks relating to your mailbox and your appointments: sorting incoming messages, summarising newsletters, draft replies, recognising proposed appointments, deriving your work instructions and the daily overview, as well as assessing whether an Instagram comment needs a reply. For these tasks, mailbox content is therefore processed within the European Union.
- Anthropic PBC (USA) for the remaining functions, such as the help chat, onboarding and profile conversations, strategy and marketing content, including a monthly web search on current formats on Instagram and LinkedIn, for which we transmit your trade, your offer, your target customers and your town, and the creation of documents such as quotes and invoices — including when you create a document from a message. Suggested replies to Instagram comments are produced by whichever of the two models is used for your account.
Only the content necessary for the respective task is transmitted (e.g. the text of a message, your profile and strategy information). Both providers process the data on our behalf (Art. 28 GDPR). Under the providers' terms, data transmitted via the programming interface is not used to train the models. The legal basis is the performance of the contract (Art. 6 (1) lit. b GDPR).
8. Connecting your email mailbox (Google Gmail)
If you connect your Gmail mailbox, we access your emails via the Google API with the permissions granted by you, in order to display them in your inbox, to sort them, to summarise them, to create draft replies and to archive or send messages on your instruction. We read your Google Contacts to match senders to your contacts; we do not change your address book.
Makiro is meant for your business. The contacts of a connected account are visible to every member of your business, even if the mailbox is private. Members see a mailbox's emails as long as it is shared within the business; you can switch it to "Only me" in the settings. We also point this out when you connect.
The use of data received from Google APIs takes place in accordance with the Google API Services User Data Policy including the Limited Use requirements. This data is not used for advertising, not sold to third parties and not used to train general AI models.
The legal basis is the performance of the contract (Art. 6 (1) lit. b GDPR). You can disconnect at any time in the settings and additionally revoke access in your Google account.
9. Calendar connection (Google Calendar)
If you connect your Google calendar, we read out appointments and free times, display them in the application and, on your instruction, create, change or delete appointments. The legal basis is the performance of the contract (Art. 6 (1) lit. b GDPR). The connection can be disconnected at any time.
10. Connecting your Microsoft account (Outlook: email, calendar, contacts)
If you connect your Microsoft account — a personal account (such as Outlook.com, Hotmail) or a Microsoft 365 account of your business — we access your mailbox, your calendar and your contacts via the Microsoft Graph interface with the permissions granted by you. Processed are:
- emails including sender, recipients, subject, content and attachments, in order to display them in your inbox, to sort them, to summarise them, to create draft replies and to archive, forward or send messages on your instruction;
- appointments and free times of your calendars, in order to display them in the application and, on your instruction, to create, change or delete appointments;
- contacts from your default address book (name, email addresses, telephone numbers, company, job title, addresses), in order to match senders to your contacts. Contacts are only read; we do not change your address book. The permission requested when connecting also covers writing contacts; we do not currently use it and will update this policy before that changes;
- your email address and account ID with Microsoft as well as the access tokens, in order to link the connection to your account and to maintain it. We store the access tokens in encrypted form; we never receive your Microsoft password.
As with Google (section 8): the contacts of a connected account are visible to every member of your business, the emails only as long as the mailbox is shared within the business.
This data is not used for advertising, not sold to third parties and not used to train general AI models. For the functions described in section 7 we transmit the content required in each case to the AI providers named there.
Your mailbox, calendar and address book are kept at Microsoft on the basis of your own contract with Microsoft — for accounts in the European Economic Area, as a rule with Microsoft Ireland Operations Limited (One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland), whose parent company is Microsoft Corporation (One Microsoft Way, Redmond, WA 98052, USA). To that extent Microsoft is not our processor. Microsoft is a recipient of the data we transmit to it on your instruction: messages and forwards sent by you including attachments, appointments created, changed or deleted, and the archive status of messages.
The legal basis is the performance of the contract (Art. 6 (1) lit. b GDPR). Messages taken over from your Microsoft account are subject to the same retention periods as all other messages (section 17): we automatically delete archived threads 365 days after their last message.
You can disconnect at any time in the settings. In doing so we delete the stored access tokens as well as the message threads and contacts taken over via this account. Unlike Google, Microsoft offers no way to revoke the permission granted to an application from our side. After disconnecting we no longer use the connection; you revoke the permission itself at Microsoft — for a work or school account at myapps.microsoft.com, for a personal account at account.microsoft.com.
10a. Connecting via IMAP/SMTP, CalDAV and CardDAV
You can connect an email account from any provider (such as GMX, web.de, IONOS, Strato) via the standard protocols IMAP and SMTP. To do so you enter your email address and password and, if needed, a different username, the server addresses and a CalDAV address for your calendar. Some providers require a separate app password for this. We process:
- your login credentials (username and password). Because IMAP offers no other way to sign in, we have to store the password in order to fetch your mailbox regularly; we store it encrypted. Server addresses and ports are stored unencrypted;
- emails in your inbox, including sender, recipients, subject, content and attachment details (name, type, size), in order to display them, sort them, summarise them and create draft replies. We only fetch attachments themselves when you open them. On your instruction we send messages via SMTP, store a copy in the "Sent" folder and move archived conversations to the archive folder of your mailbox; if one of these folders is missing, we create it. We do not delete any emails;
- via CalDAV, the events in your calendars, in order to display them and to create, change or delete events on your instruction;
- via CardDAV, the contacts in your address books (name, email addresses, phone numbers, company, addresses, note), in order to match senders to your contacts. Contacts are only read; we do not change your address book.
To find your provider's servers, we first use a built-in list of common providers. If your provider is not on it, we query Mozilla Thunderbird's public configuration database (autoconfig.thunderbird.net); in doing so we transmit only the domain of your email address, not the address itself. For calendar and contacts we also look up your domain's DNS records. We then sign in with your credentials to the servers of your provider or your domain found this way until a sign-in succeeds. All connections are encrypted (TLS); we never establish an unencrypted connection.
As with Google (section 8): the contacts of a connected account are visible to every member of your business, the emails only as long as the mailbox is shared within the business. For the functions described in section 7 we transmit the content required in each case to the AI providers named there. This data is not used for advertising and not sold to third parties.
Your mailbox, calendar and address book are kept by your provider on the basis of your own contract with them; in this respect your provider is not our processor. Your provider receives the data we transmit there on your instruction: messages you send including attachments, events created, changed or deleted, and the moving of archived conversations.
The legal basis is the performance of a contract (Art. 6(1)(b) GDPR). Imported messages are subject to the same retention periods as all other messages (section 17). You can disconnect at any time in the settings. We then delete your stored credentials as well as the conversations and contacts imported through this account; your mailbox at the provider remains unchanged. If you used an app password, you can revoke it at your provider afterwards.
11. Social media publishing (Meta / Instagram, YouTube, LinkedIn)
Instagram. If you connect an Instagram account, we transmit the content released by you (text, images) to Meta Platforms Ireland Ltd. for publication. The processing takes place on your instruction in performance of the contract (Art. 6 (1) lit. b GDPR). Meta is independently responsible for the processing within the Meta platforms.
When you connect, we store the Instagram user id, the username, and the access token; the token is stored encrypted. If you disconnect, we delete the token and the connection; the Instagram user id and the username remain only with the direct messages in your inbox (see below). Meta can also trigger a deletion itself, for example if you revoke access in your Meta account; we then carry out such a deletion request on our end.
For posts you published on Instagram through makiro, we additionally retrieve metrics (likes, comments, shares, saves, reach, views) and the comments below them, including the Instagram usernames of the commenters. We store the comments and the suggested replies to them encrypted for 180 days from the comment. To assess whether a comment needs a reply, we have it classified by Mistral AI SAS; for suggested replies, the comment is sent together with the caption to the language model used for your account (both providers, see section 7). We only publish a reply if you send it yourself. If you disconnect or Meta triggers a deletion, we delete the metrics, comments and suggested replies as well.
Stories. Photos and videos you upload for an Instagram story are stored in our media store so that Instagram can fetch them, and we delete them 30 days after the story expires (24 hours after posting). The story's text and metrics (views, reach, replies) are kept. Unposted drafts, together with their uploaded files, are deleted after one day. For the text suggestion for a story, the photo is sent to the language model used for your account (both providers, see section 7). Replies to your story appear as direct messages in your inbox, with a link to the story. If you disconnect or Meta triggers a deletion, we delete your stories together with their text, metrics and files.
If customers send direct messages to your connected Instagram account, we process them together with the customer's Instagram username (or, if there is none, their display name) and the time in order to show them in your inbox and prepare replies. We store them encrypted like mailbox messages. For suggested replies, the message is sent to the language model used for your account (section 7). We only send a reply if you send it yourself. If you disconnect, we delete the token and the connection, but the conversations, together with your account's Instagram user id and username, stay readable in your inbox; they can no longer be answered. Unarchived conversations remain until you archive or delete them; archived conversations are deleted 365 days after the last message. If Meta triggers a deletion or you delete your makiro account, we delete the channel account and all Instagram conversations.
YouTube. If you connect a YouTube channel, we use the YouTube API Services of Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) to publish the videos released by you, including title and description, on your channel. The processing takes place on your instruction in performance of the contract (Art. 6 (1) lit. b GDPR). By connecting, you agree to the YouTube Terms of Service; processing by Google is governed by the Google Privacy Policy.
When you connect, we store the channel id, the channel name, the permissions you granted, and the access and refresh tokens; both tokens are stored encrypted. We use the data received from the YouTube API in accordance with the Google API Services User Data Policy (see section 8) solely for publishing. If you disconnect, we revoke access at Google and delete this data. You can additionally revoke access at any time at myaccount.google.com/permissions.
LinkedIn. If you connect your personal LinkedIn profile, we transmit the content released by you (text, images) to LinkedIn Ireland Unlimited Company (Wilton Plaza, Wilton Place, Dublin 2, Ireland) for publication in your name. The processing takes place on your instruction in performance of the contract (Art. 6 (1) lit. b GDPR). LinkedIn is independently responsible for the processing within LinkedIn; the LinkedIn Privacy Policy applies.
The connection belongs to the person who makes it: each member of a business connects their own profile, and posts are published only in the name of the person who publishes or schedules them. When you connect, we store the LinkedIn member id, your name, the access token and its expiry date; the token is stored encrypted and expires after about 60 days. If you disconnect or your account is deleted, we delete this data and cancel your scheduled LinkedIn posts that have not yet been published. You can additionally revoke Makiro's access at any time in your LinkedIn settings at linkedin.com/psettings/permitted-services.
12. Public booking page
Through a public booking page at www.makiro.de/termin/…, customers of a business can book appointments. When a booking is made, we process the data provided (name, email address, optionally telephone number, for on-site appointments the address, and optionally a message) in order to enter the appointment in the calendar of the business and deliver the booking to its inbox. The email address is added to the appointment as an attendee, so that the calendar provider of the business sends an invitation. The respective business is the controller for this; we act as a processor.
The legal basis is the performance of a contract (Art. 6 (1) lit. b GDPR). The booking is subject to the same retention periods as all other messages (section 17): we automatically delete archived threads 365 days after their last message.
13. Payment processing
For subscriptions we use Mollie B.V. (Keizersgracht 126, 1015 CW Amsterdam, Netherlands). When a paid subscription is concluded, the data required for the SEPA direct debit (name, bank details, mandate and payment data) is collected directly by Mollie and processed there. We ourselves store only the customer, mandate and subscription identifiers as well as the payment status.
The legal basis is the performance of the contract (Art. 6 (1) lit. b GDPR) as well as compliance with retention obligations under tax and commercial law (Art. 6 (1) lit. c GDPR).
14. Cookies and reach measurement
We use technically necessary cookies for signing in and for session management. These are strictly necessary for the service expressly requested by you (§ 25 Abs. 2 Nr. 2 TDDDG).
For product analytics we use PostHog (PostHog Inc., USA) on the provider's EU infrastructure (eu.posthog.com). Collection is disabled by default and starts only after you have consented in the application (§ 25 Abs. 1 TDDDG, Art. 6 (1) lit. a GDPR). The attribution takes place exclusively via a random account identifier; names or email addresses are not transmitted to PostHog. The requests run via our own domain (/ingest). You may withdraw your consent at any time; if you delete your account, the associated analytics profile is deleted as well.
15. Help chat and support
In the application you can open a help chat via the “Help” entry to ask questions about using makiro and to send feedback. We process your messages, the page of the application you are on, your role and the modules activated for your account. The replies are generated by an AI language model; for this purpose, this content is transmitted to the AI provider named in section 7 for the remaining functions.
If the AI cannot help or you wish to speak to the team, the Makiro team can view the conversation and reply in person. While a team member has taken over the conversation, the AI does not reply. An internal Slack channel (Slack Technologies Ltd., Ireland) informs us of new conversations and of hand-overs to the team; only your name, the page you were on, a link to the conversation and — for a hand-over — a short reason worded by the AI are transmitted, but not the content of your messages in the help chat.
Every time a team member opens, takes over, answers or hands back your conversation, we log it — with the team member, the time and the reference to your account, but without the content of your messages. The same applies to changes the team makes to your account in its internal area. This keeps it traceable who accessed your data and when. The legal basis is our legitimate interest in the security of processing (Art. 6(1)(f), Art. 32 GDPR).
If you send feedback elsewhere in the application (for example on a reply draft or during onboarding), your message is transferred to an internal Slack channel (Slack Technologies Ltd., Ireland) so that we can deal with it. The legal basis is our legitimate interest in improving the service and in handling your request (Art. 6 (1) lit. f GDPR).
The help chat messages are stored in encrypted form in our database and are deleted automatically 180 days after the last message of the conversation; when you delete your account, they are removed immediately. The legal basis is the performance of the contract (Art. 6 (1) lit. b GDPR).
16. Transfers to third countries
Some of the service providers named have their seat in the USA (Vercel, Neon, PostHog, ElevenLabs, Anthropic, Google, Microsoft). Insofar as personal data is thereby transferred to the USA, we base the transfer on the European Commission's standard contractual clauses (Art. 46 (2) lit. c GDPR) or — insofar as the respective provider is certified — on an adequacy decision under the EU-US Data Privacy Framework (Art. 45 GDPR). Copies of the safeguards are available on request.
17. Retention periods
- Account and application data: for the duration of the usage relationship.
- Raw transcripts of voice conversations: 30 days.
- Message threads archived by you: 365 days from the last message of the thread; after that, the thread, messages, drafts and feedback are deleted automatically. What is in the inbox or has been deferred is retained regardless of its age.
- Conversations in the help chat: 180 days from the last message of the conversation.
- Log of access and changes by the Makiro team: 730 days; deleting your account removes the reference to you.
- Comments below your Instagram posts published through makiro: 180 days from the comment; the suggested replies to them are deleted along with them.
- Photos and videos of your Instagram stories: 30 days after the story expires (24 hours after posting); text and metrics are kept until you disconnect; drafts with their files: one day.
- Instagram direct messages: like mailbox messages, archived conversations after 365 days counted from the last message of the conversation.
- Billing and accounting data: until the statutory retention periods have elapsed (as a rule 8 to 10 years pursuant to § 147 AO, § 257 HGB).
- Remaining data: deletion as soon as the purpose ceases to apply or you delete your account. Deleting the account removes your data from our database as well as the associated files, conversation recordings held by the voice provider, your analytics profile and your sign-in with the authentication service, including the email address stored there and the link to your Google account.
18. Your rights
You have the right of access (Art. 15 GDPR), to rectification (Art. 16), to erasure (Art. 17), to restriction of processing (Art. 18), to data portability (Art. 20) as well as the right to object to processing based on legitimate interests (Art. 21 GDPR). You may withdraw consent given at any time with effect for the future.
To do so, please contact info@tojiki.de. You can additionally delete your account together with the associated data yourself at any time in the settings of the application; a running subscription is terminated in the process.
Irrespective of this, you have a right to lodge a complaint with a data protection supervisory authority; the authority responsible for us is the Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Promenade 27, 91522 Ansbach.
19. Changes to this policy
We adapt this privacy policy when the functions of the application or the service providers used change. The version published on this page in each case applies.