What happens if my webhook fails?

We automatically retry failed webhooks with exponential backoff. You can configure the number of retries and delay between attempts. All failures are logged with detailed error information.

Can I schedule webhooks in my local timezone?

Yes! You can set any timezone for your webhooks. We handle daylight saving time transitions automatically, so your schedules stay consistent.

What's the difference between one-time and recurring webhooks?

One-time webhooks fire at a specific date and time, then are done. Recurring webhooks use cron expressions to repeat at intervals - hourly, daily, weekly, or any custom schedule.

How do I integrate with Slack/Discord/Zapier?

We provide pre-built templates for popular services. Just paste your webhook URL and customize the message. Our templates include the correct headers and payload format.

Is there a free trial?

Yes! All plans include a 14-day free trial. No credit card required to start. You can upgrade or downgrade at any time.

What's the minimum delay for scheduled webhooks?

You can schedule webhooks as little as 1 minute in the future. For recurring webhooks, the minimum interval is 1 minute.

Privacy Policy

Last updated: December 17, 2024

Overview

RunLater ("we", "our", or "us") operates a service that schedules HTTP requests to run at specified times. This Privacy Policy explains what data we collect, how we use it, and your rights regarding your information.

Key Point: Your Request Data

We store the minimum data necessary to execute your scheduled requests: the URL, method, headers, body, and schedule. Request/response logs are retained temporarily for debugging and are automatically deleted after 30 days.

How RunLater Works

Understanding our service helps explain what data we handle:

You create a scheduled request with a target URL, method, headers, and body
You specify when the request should run (one-time or recurring)
At the scheduled time, our servers send the HTTP request to your target URL
We log the response for you to review, then delete logs after 30 days

Information We Collect

Account Information

When you sign up, we collect:

Your email address (for authentication and notifications)
Account creation date

Scheduled Request Data

For each scheduled request, we store:

Target URL
HTTP method (GET, POST, etc.)
Headers (may include API keys you provide)
Request body
Schedule (timing, timezone, recurrence pattern)

Execution Logs

When requests are executed, we temporarily log:

Timestamp of execution
HTTP response status code
Response headers and body (for debugging)
Execution duration

Execution logs are automatically deleted after 30 days.

Billing Information

Payments are processed by Stripe. We store:

Stripe customer ID
Subscription ID and plan type
Usage counts (for billing limits)

We do NOT store credit card numbers or bank details. All payment processing happens through Stripe.

How We Use Your Information

Provide the service: Execute your scheduled HTTP requests at the specified times
Manage your account: Authenticate you, manage your subscription, enforce usage limits
Communicate with you: Send important service updates and billing notifications
Improve the service: Analyze usage patterns to fix bugs and improve features

Third-Party Services

We use the following third-party services:

Resend (resend.com) - Sends authentication emails and notifications. Privacy Policy
Stripe (stripe.com) - Processes payments. Privacy Policy
DigitalOcean (digitalocean.com) - Hosts our servers. Privacy Policy

Data Retention

Account data: Retained while your account is active, deleted within 30 days of account deletion
Scheduled requests: Retained until you delete them or delete your account
Execution logs: Automatically deleted after 30 days
Usage metrics: Retained for 12 months for billing purposes

Data Security

We implement appropriate measures to protect your data:

All data in transit is encrypted using TLS/HTTPS
Database access is restricted and authenticated
API keys in your request headers are stored securely
Regular security reviews of our infrastructure

Your Rights

Depending on your location, you may have the following rights:

Access: Request a copy of the data we hold about you
Correction: Request correction of inaccurate data
Deletion: Request deletion of your account and associated data
Portability: Request your data in a portable format

To exercise any of these rights, contact us at privacy@runlater.app.

For European Users (GDPR)

If you are in the European Economic Area (EEA), we process your data under the following legal bases:

Contract: Processing necessary to provide our service to you
Legitimate interests: Improving our service, preventing fraud, ensuring security
Consent: Where required, such as for marketing communications

Our servers are located in the United States. By using RunLater, you consent to the transfer of your data to the US.

For California Users (CCPA)

California residents have additional rights under the CCPA:

Right to know what personal information we collect
Right to delete personal information
Right to opt-out of the sale of personal information
Right to non-discrimination for exercising your rights

We do not sell personal information. To exercise your CCPA rights, contact privacy@runlater.app.

Children's Privacy

RunLater is not intended for use by children under 16. We do not knowingly collect personal information from children under 16. If you believe we have collected information from a child, please contact us.

Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the new policy on this page and updating the "Last updated" date.

Contact Us

If you have questions about this Privacy Policy, contact us at:

Email: privacy@runlater.app

General Support: support@runlater.app