Effective July 17, 2026 · Last updated July 17, 2026
This Cookie Policy explains how Redwane Studio LLC, doing business as Pegasy (“Pegasy,” “we,” “us,” or “our”), uses cookies and similar technologies when you visit or use:
This Cookie Policy should be read together with the Pegasy Privacy Policy.
Cookies are small text files that a website stores on your browser or device.
Cookies can help websites:
Cookies may be:
Cookies may also be:
Pegasy may also use technologies that perform functions similar to cookies, including:
References to “cookies” in this Policy may include these similar technologies where appropriate.
Pegasy may use cookies and similar technologies to:
Pegasy does not use cookies to sell personal information.
Pegasy does not use advertising cookies or cross-site behavioral advertising cookies.
Strictly necessary cookies are required for the website or application to function securely.
These cookies may be used for:
Because these cookies are necessary to provide the Service or protect users, they generally cannot be disabled through Pegasy’s consent controls.
You may still block them through your browser, but parts of Pegasy may stop functioning.
Preference cookies or browser-storage records may remember:
These technologies improve usability but are not used for advertising.
Pegasy may use limited analytics technologies to understand:
Where required by law, non-essential analytics technologies will be activated only after consent.
Pegasy will not use analytics data obtained through cookies for:
If Pegasy introduces or changes a non-essential analytics provider, the cookie banner and this Policy will be updated where required.
When you access a Stripe-hosted checkout or customer portal, Stripe may use cookies and similar technologies for:
These cookies are controlled by Stripe and are subject to Stripe’s own privacy and cookie practices.
Infrastructure providers such as Webflow, Render, Cloudflare, or other technical providers may use cookies or similar records for:
These cookies may be strictly necessary depending on the service configuration.
The exact names and durations may vary as the Service evolves, but Pegasy may use the following types of records.
Example name: pg_oauth_csrf
Provider: Pegasy
Purpose: Helps protect Google Sign-In against cross-site request forgery by binding the OAuth request to the user’s browser.
Category: Strictly necessary
Typical duration: Temporary and limited to the authentication flow.
Name: May vary depending on the active authentication implementation.
Provider: Pegasy
Purpose: Maintains an authenticated session, identifies the active account, and protects access to workspace information.
Category: Strictly necessary
Typical duration: Session-based or until the configured session expiration or logout.
Name: May vary.
Provider: Pegasy
Purpose: Remembers information such as the active workspace, language, theme, onboarding state, or display settings.
Category: Preference
Typical duration: Until expiration, account reset, or deletion through browser settings.
Name: May vary depending on the consent-management implementation.
Provider: Pegasy
Purpose: Remembers whether the user accepted, rejected, or customized non-essential cookies.
Category: Strictly necessary
Typical duration: Up to 12 months unless renewed or deleted earlier.
Name: Determined by Stripe.
Provider: Stripe
Purpose: Checkout, customer portal, payment security, authentication, and fraud prevention.
Category: Strictly necessary or payment-related
Typical duration: Determined by Stripe.
Name: Determined by the relevant infrastructure provider.
Provider: Webflow, Render, Cloudflare, or another technical provider
Purpose: Security, bot protection, network integrity, routing, and performance.
Category: Strictly necessary where active
Typical duration: Determined by the provider and configuration.
When you use Google Sign-In or connect Gmail, you are redirected to Google’s services.
Google may use its own cookies and similar technologies on Google-controlled pages to:
These cookies are controlled by Google.
Pegasy’s use of information received from Google APIs is described in the Pegasy Privacy Policy.
Pegasy does not use Gmail data for advertising or cookie-based profiling.
At the effective date of this Policy, Pegasy does not intentionally use:
If Pegasy introduces advertising or materially different tracking technologies in the future, we will:
Where consent is legally required, Pegasy will request consent before placing or accessing non-essential cookies.
The consent interface should allow users to:
Rejecting non-essential cookies should not prevent access to the essential functions of the website or application.
Strictly necessary cookies may operate without consent where permitted because they are required to provide or secure the requested service.
Where a cookie-preference tool is available, you may change your choices through the Cookie Settings link displayed in the website footer or cookie banner.
Withdrawing consent does not affect processing that occurred before withdrawal.
After preferences are changed, certain cookies may remain until:
Most browsers allow you to:
The available controls depend on your browser and device.
Blocking strictly necessary cookies may cause:
If Pegasy later provides a mobile application or uses mobile SDKs, device settings may provide additional controls over:
This Policy will be updated if materially different mobile technologies are introduced.
Cookies are retained only for as long as reasonably necessary for their purpose.
Typical durations may include:
Security and fraud-prevention records may be retained for longer where necessary to protect the Service or comply with law.
Third-party providers may set or access their own cookies when you interact with their services.
These providers may include:
Pegasy does not control third-party cookies placed on third-party domains.
You should review the relevant provider’s privacy and cookie information for more details.
Cookie and browser data may be processed in the United States and other countries where Pegasy or its providers operate.
International data transfers are addressed in the Pegasy Privacy Policy.
Pegasy may update this Cookie Policy when:
The “Last updated” date will be revised when changes are made.
Material changes may also be communicated through the cookie banner, website, application, or account communications.
For questions about cookies or similar technologies, contact:
Redwane Studio LLC
30 N Gould St, Ste R
Sheridan, WY 82801
United States
Email: support@pegasy.io
Start with one campaign, choose your creative direction, and let Pegasy prepare personalized Creative Hooks for the companies you want to reach.