Acapela Data Privacy FAQ
Acapela Data Privacy FAQ
Hi there 👋🏼 You have most likely been onboarded to Acapela recently and you wondered how is your data handled within the app. This is a doc with the most important questions about how we import and store data in the app. If you have any unanswered burning questions, please hit us up at hello@acapela.com
What data is stored on Acapela?
Acapela reads none of the content of the integrations you add to your account. We listen to notifications in the background and in case of a new notification we save the id of the author, source URL (app and channel or filename), and text preview for one notification per file. All other information stays only locally on your personal machine.
Where is my data stored?
Acapela stores minimal information about imported notifications. We keep information about id of the author, notification URL, and text preview of the last notification per file. This information is stored on an encrypted SQL database hosted in Frankfurt by Google Cloud.
Who has access to the stored information?
The information can only be accessed through a secured proxy by the CTO of Acapela. The data is never exported nor shared with anyone. On very rare occasions, where technical issues cannot be otherwise resolved, other engineers from the Acapela team can be given temporary access to the database.
What usage data is saved by Acapela?
We collect information about primary actions on the app and technical issues that come up. The primary actions include events such as resolving notifications and snoozing notifications. The usage information only includes the ids of users and notifications, thus no personally identifiable information is saved.
We also collect information about errors that occur during usage. For errors, we save the user id who was affected and which version of the app they were using. Again, no personal information is saved.
Do you have access to the content of my integrated apps?
The embedded application is loaded in a stand-alone browser inside Acapela. Acapela does not read nor manipulate the content of the integrated applications. We also do not track which URLs or applications the user has interacted with.
Hi there 👋🏼 You have most likely been onboarded to Acapela recently and you wondered how is your data handled within the app. This is a doc with the most important questions about how we import and store data in the app. If you have any unanswered burning questions, please hit us up at hello@acapela.com
What data is stored on Acapela?
Acapela reads none of the content of the integrations you add to your account. We listen to notifications in the background and in case of a new notification we save the id of the author, source URL (app and channel or filename), and text preview for one notification per file. All other information stays only locally on your personal machine.
Where is my data stored?
Acapela stores minimal information about imported notifications. We keep information about id of the author, notification URL, and text preview of the last notification per file. This information is stored on an encrypted SQL database hosted in Frankfurt by Google Cloud.
Who has access to the stored information?
The information can only be accessed through a secured proxy by the CTO of Acapela. The data is never exported nor shared with anyone. On very rare occasions, where technical issues cannot be otherwise resolved, other engineers from the Acapela team can be given temporary access to the database.
What usage data is saved by Acapela?
We collect information about primary actions on the app and technical issues that come up. The primary actions include events such as resolving notifications and snoozing notifications. The usage information only includes the ids of users and notifications, thus no personally identifiable information is saved.
We also collect information about errors that occur during usage. For errors, we save the user id who was affected and which version of the app they were using. Again, no personal information is saved.
Do you have access to the content of my integrated apps?
The embedded application is loaded in a stand-alone browser inside Acapela. Acapela does not read nor manipulate the content of the integrated applications. We also do not track which URLs or applications the user has interacted with.
Hi there 👋🏼 You have most likely been onboarded to Acapela recently and you wondered how is your data handled within the app. This is a doc with the most important questions about how we import and store data in the app. If you have any unanswered burning questions, please hit us up at hello@acapela.com
What data is stored on Acapela?
Acapela reads none of the content of the integrations you add to your account. We listen to notifications in the background and in case of a new notification we save the id of the author, source URL (app and channel or filename), and text preview for one notification per file. All other information stays only locally on your personal machine.
Where is my data stored?
Acapela stores minimal information about imported notifications. We keep information about id of the author, notification URL, and text preview of the last notification per file. This information is stored on an encrypted SQL database hosted in Frankfurt by Google Cloud.
Who has access to the stored information?
The information can only be accessed through a secured proxy by the CTO of Acapela. The data is never exported nor shared with anyone. On very rare occasions, where technical issues cannot be otherwise resolved, other engineers from the Acapela team can be given temporary access to the database.
What usage data is saved by Acapela?
We collect information about primary actions on the app and technical issues that come up. The primary actions include events such as resolving notifications and snoozing notifications. The usage information only includes the ids of users and notifications, thus no personally identifiable information is saved.
We also collect information about errors that occur during usage. For errors, we save the user id who was affected and which version of the app they were using. Again, no personal information is saved.
Do you have access to the content of my integrated apps?
The embedded application is loaded in a stand-alone browser inside Acapela. Acapela does not read nor manipulate the content of the integrated applications. We also do not track which URLs or applications the user has interacted with.