Send to Buffer App Privacy Policy
This privacy notice covers the Kittl Send to Buffer Extension and supplements Kittl's main Privacy Policy at kittl.com/privacy. Both apply in full; this notice describes only what is specific to the Buffer integration.
The Send to Buffer Extension uses the Buffer API to let you schedule a finished design from Kittl to the social channels you have connected in Buffer: one image or a carousel of up to ten, with the text you enter, added to a channel's queue or set for a time you pick. It requests the "account:read", "posts:read" and "posts:write" permissions, and "offline_access" so that it stays connected. Kittl is not affiliated with, sponsored by, or endorsed by Buffer, Inc. Buffer is a trademark of Buffer, Inc.
When you connect Buffer, Buffer issues an access token and a refresh token. Kittl's servers store them encrypted, in storage dedicated to your connection and tied to your Kittl account, because Buffer lets each refresh token be used only once and one place must renew it. The Kittl editor holds only a separate token that works with Kittl's servers alone, and Kittl's servers keep only a one-way fingerprint of it. Kittl never logs your tokens or the text of your posts.
To keep the extension fast and within the limits Buffer sets for all Kittl users together, Kittl's servers keep a copy of your Buffer account's name and picture and of your organizations for up to 24 hours, and of your channels' names, pictures, networks and settings for up to 10 minutes. After a send, they keep the result for each channel (the post's identifier, status and scheduled time, without its text or images) for 24 hours, so that pressing Send again does not post twice. They also count your sends and status checks under a fingerprint of your Kittl account, and delete those counts once the period they cover has passed.
When you schedule a post, each image is exported from your design and saved to your Kittl uploads, which gives it a public web address. Kittl's servers then send Buffer, for each channel you chose, the text you entered, the address and alternative text of each image, whether to add the post to the queue or the time you picked, and the type of post where a network needs one. Buffer fetches the images from that address. Kittl receives operational data back from Buffer in connection with scheduling, for example each post's identifier, status, scheduled and published time, its link once published and any error messages, which we use to operate the integration. Once scheduled, the post is governed by Buffer's terms and those of the network it is published to; you can edit, reschedule or delete it in your Buffer account.
Kittl does not access or process the personal data of people who follow or interact with your channels, including their names, comments or messages. That data stays between you, Buffer and each network under their privacy practices.
The extension keeps a list of your recent sends in your browser, never on Kittl's servers: when each was sent and, for each channel, its name and the post's identifier. It belongs to the Kittl account that is signed in and is removed, with the cached channel list, whenever you sign out. When Check status finds that a post no longer exists in Buffer, that post is removed from the list.
Kittl records anonymous usage events for the extension, for example whether connecting or scheduling succeeded, how many channels and images a post had, whether it had text or alternative text, whether it went to the queue or a picked time and how long it took, to operate and improve the feature, as described in the main Privacy Policy. These events do not include your post text, alternative text, channel, organization or network names, Buffer or Kittl identifiers, or error messages. Kittl does not sell or redistribute Buffer content or Buffer-derived data to any third party; the service providers described in the main Privacy Policy process it only to operate the extension.
When you disconnect in the extension, Kittl deletes your Buffer tokens and everything it keeps for that connection, including the cached account and channel details and the send records, from its production systems (subject to the limited log and backup retention noted in the main Privacy Policy). Disconnecting does not withdraw Kittl's access in Buffer itself; you can also remove Kittl in your Buffer settings. If you remove it there first, Kittl deletes the stored tokens the next time it tries to use them, and the rest of the connection after 30 days without use, as it does for any connection left unused for 30 days. Buffer content remains subject to Buffer's Terms of Use.