PRIVACY POLICY

Effective Date: January 3, 2026

Last Updated: January 3, 2026

App Name: Alias Bot ("Alias Bot", the "App")

Provider: Yippa ("Yippa", "we", "us", "our")

Support / Privacy Contact: team@yippa.io

This Privacy Policy explains how we collect, use, disclose, and protect information when you install or use Alias Bot in Slack. By installing or using the App, you agree to this Privacy Policy.

Alias Bot is a third-party application that integrates with Slack. Slack's processing of your data is governed by Slack's own terms and privacy policy.

1. What Alias Bot Does

Alias Bot allows users to create channel-scoped aliases (e.g., !devs) that expand into mentions of specific Slack members when used in messages. To provide this functionality, Alias Bot processes certain Slack events and stores only the configuration required to manage aliases.

2. Information We Collect

2.1 Slack Installation & Workspace Data

When you install Alias Bot, Slack provides data necessary to authenticate and operate the App, which may include:

Workspace / organization identifiers (e.g., team_id, and where applicable enterprise_id)
Installation metadata (e.g., installation time, installer user ID)
OAuth credentials required for the App to operate (e.g., bot token and related authorization metadata)

We store this information to maintain your installation and enable the App to call Slack APIs as required.

2.2 Alias Configuration Data (Stored)

Alias Bot stores the data you explicitly configure, including:

Alias name (e.g., !devs)
Slack user IDs mapped to the alias
Channel ID where the alias is defined (aliases are channel-scoped)
Workspace / org identifiers needed to scope and isolate data correctly
Optional metadata you may add (e.g., description, if enabled in your version)

2.3 Message and Event Data (Processed; Not Stored as Content)

To detect when an alias is used and to respond appropriately, Alias Bot may receive Slack event payloads that include message text and related metadata.

Important:

We process message text to detect alias usage and to post a reply.
We do not store Slack message bodies, message history, or conversation transcripts as part of normal App operation.
We do not store files shared in Slack.

2.4 Operational Data and Logs

To run a reliable and secure service, we collect limited operational data such as:

Request timestamps, event IDs, error traces
Performance and uptime diagnostics
High-level usage metrics (e.g., number of alias triggers)

We aim to avoid logging message content. If message content is included in logs due to an unexpected error, we treat it as sensitive and restrict access.

2.5 Support Communications

If you contact us at team@yippa.io, we receive the information you choose to provide (e.g., your email address, workspace/channel context, screenshots, and your description of the issue). We use this information solely to provide support.

2.6 Billing and Payments (DodoPayments)

If you purchase a subscription (monthly or yearly), payment processing is handled by DodoPayments. We do not collect or store full payment card details.

Depending on DodoPayments' integration and checkout configuration, we may receive and store limited billing-related metadata such as:

Subscription status (active/canceled)
Plan type (monthly/yearly)
Billing identifiers (e.g., customer/subscription IDs)
Timestamps for subscription start/end/renewal events

3. How We Use Information

We use the information described above to:

Provide and operate Alias Bot functionality (create/edit/delete aliases; expand aliases into mentions)
Authenticate your installation and maintain secure access to Slack APIs
Provide customer support and troubleshoot issues
Monitor performance, improve reliability, and maintain service quality
Prevent abuse, fraud, and security incidents
Comply with legal obligations

We do not:

Sell personal data
Use Slack message content for advertising or marketing profiling
Store message history or analyze conversations for unrelated purposes

4. Legal Bases for Processing (Where Applicable)

Depending on your jurisdiction, we rely on one or more of the following legal bases:

Performance of a contract (to provide the App you installed)
Legitimate interests (operating, securing, and improving the service)
Consent (where required, such as optional communications)
Compliance with law (when legally compelled)

5. Data Sharing and Disclosure

We share information only as necessary to operate the service, including with:

5.1 Service Providers (Processors)

DigitalOcean (hosting/infrastructure): we host the App and related databases/services on DigitalOcean.
DodoPayments (payments): subscription checkout and payment processing.
Email provider(s) used to receive and respond to support emails (as applicable).

These providers are permitted to process data only to provide services to us.

5.2 Legal and Safety Disclosures

We may disclose information if we believe disclosure is reasonably necessary to:

Comply with applicable law, regulation, legal process, or governmental request
Enforce our terms, protect our rights, users, or the public
Detect, prevent, or address fraud, security, or technical issues

We do not share Slack message content because we do not store it as a matter of normal operation.

6. Data Retention

We retain information only for as long as needed to operate the service and meet legal and security requirements.

Alias configuration data: retained until you delete it via the App, or until the App is uninstalled (subject to backups).
Installation/OAuth data: retained while the App remains installed; tokens are deleted or invalidated within a reasonable time after uninstall, subject to security and backup constraints.
Operational logs: typically retained for a limited period for troubleshooting and security (commonly 30-90 days).
Backups: deleted data may persist in backups until backup rotation completes.

If you want deletion confirmation or have specific retention requests, contact team@yippa.io.

7. Security

We implement reasonable administrative, technical, and organizational safeguards designed to protect information, including:

Encryption in transit (HTTPS/TLS)
Access controls and least-privilege internal access
Secure handling of Slack OAuth tokens and configuration data
Monitoring and logging for reliability and abuse prevention

No method of transmission or storage is fully secure, and we cannot guarantee absolute security.

8. International Data Transfers

Depending on where your Slack workspace is located and where our service providers operate, your data may be processed in countries other than your own. By using the App, you understand that such transfers may occur.

9. Your Rights and Choices

Depending on your jurisdiction, you may have rights to access, correct, delete, or export certain data.

You may request:

A copy of alias configuration data associated with your workspace (where feasible)
Deletion of alias configuration data
Assistance confirming uninstall-related deletion steps (subject to backups/log retention)

To make a request, email team@yippa.io. We may need your workspace identifiers (e.g., team_id) to verify and locate the correct data.

10. Children's Privacy

Alias Bot is intended for use by organizations and is not directed to children under 13. We do not knowingly collect personal information from children under 13.

11. Changes to This Policy

We may update this Privacy Policy from time to time. We will update the "Last Updated" date when changes are made. Continued use of the App after updates means you accept the revised policy.

12. Contact

For privacy questions, requests, or concerns, contact:

Email: team@yippa.io