Last updated: 2026-08-18
1. Scope
This notice covers rebeccabot 2.0, F5's internal tool for submitting, reviewing, and publishing DevCentral social posts and videos. It's an internal tool for F5 employees and select external contributors - it is not a public F5 product or service, so it is separate from F5's general Privacy Notice, which governs F5's customer- and public-facing business. This page explains what rebeccabot itself collects, how it's used, where it's stored, and who to contact with questions.
2. Who can use rebeccabot
Signed-in access is restricted to Microsoft Entra ID (@f5.com) accounts via SSO. One request type - "Suggest a Post for Us to Share" (the influencer/community submission flow) - is intentionally open to anonymous external submitters who don't have an F5 account, so that community members can suggest content without signing in.
3. What we collect
- Account/identity data - your name, email address, and role (user/admin), sourced from Entra ID at sign-in and cached in a `core-users` DynamoDB record.
- Request content - whatever you submit through the intake form: request type, title/description/copy, brand, tags, scheduling preferences, and an optional source article URL.
- Uploaded files - video and thumbnail files you upload are stored in S3 via a presigned direct upload; transcripts generated from your video are stored alongside them.
- Anonymous submissions - the community/influencer form collects only a LinkedIn post URL and a display name (plus an optional email if you opt in to a copy of your submission) - no account or sign-in is required or created.
- Operational data - basic request/job status, timestamps, and (for admins) actions taken while reviewing, scheduling, or publishing content, kept for troubleshooting and audit purposes.
We do not use analytics, advertising, or third-party tracking cookies. Your session token and cached role are kept in your browser's session storage only, cleared when you sign out.
4. How we use it
Submitted content is used solely to fulfill your request: generating draft social copy (via Amazon Bedrock), transcribing uploaded video (via Amazon Transcribe), creating draft posts in Sprinklr for review, and publishing approved content to the relevant channel (e.g., an unlisted YouTube upload pending review, or a scheduled social post). Admin actions (approvals, edits, publishing) are tied to the admin's account for accountability. We do not sell data, run marketing campaigns with it, or use it to profile individuals beyond what's needed to operate the request/review workflow itself.
5. Where it's stored
All data is stored in F5's own AWS account (DynamoDB for structured records, S3 for uploaded files and generated artifacts), in the region rebeccabot is deployed to. Data is not knowingly transferred outside of F5's AWS infrastructure except to the third-party services listed below, as needed to fulfill a request.
6. Third-party services we send data to
- Microsoft Entra ID - authentication only (SSO sign-in).
- Amazon Bedrock (Anthropic Claude) - request/article text sent to generate suggested social copy and titles/descriptions.
- Amazon Transcribe (AWS) - uploaded video audio, to produce a text transcript.
- Sprinklr - draft and scheduled post content, to publish to F5's social channels.
- YouTube (Google) - uploaded video, title, and description, to publish approved videos.
- LinkedIn - public post URLs only, for the influencer-repost tracking flow (no LinkedIn account access).
Each of these providers has its own privacy practices governing how they handle data once it's sent to them; we only send what's necessary for the specific feature (drafting, transcribing, or publishing) you're using.
7. Retention
We keep request records, uploaded media, and transcripts for as long as needed to support the review/publishing workflow and for reasonable operational troubleshooting afterward. Rebeccabot does not currently have an automated expiry/deletion schedule - if you'd like a specific submission or file removed sooner, contact us using the details in Section 10 and we'll handle it manually.
8. Your choices
F5 employees can ask an admin (via Section 10) to review, correct, or delete their submitted requests or account record. Anonymous community submitters are not tracked beyond the single submission they make; there's no account to manage or opt out of because none is created.
9. Security
Access to admin/operator features requires an authenticated, role-checked session; file uploads use short-lived presigned S3 URLs rather than exposing storage credentials to the browser. As with any software, no system can guarantee perfect security - we apply reasonable technical safeguards and address issues as they're identified.
10. Contact & changes to this notice
Questions, corrections, or deletion requests about data handled by rebeccabot should go to the DevCentral / rebeccabot team through your usual internal F5 contact channel for this tool.
We may update this notice as rebeccabot's features change; the "Last updated" date at the top of this page reflects the most recent revision.