The cookies and similar technologies we use on aewita.com and app.aewita.com, in plain language.
This Cookie Policy describes the cookies and similar technologies (local storage, session storage, pixel tags) used by Scrivly, Inc. d/b/a Aewita on:
It supplements the Privacy Policy. If a conflict arises between the two documents about cookies specifically, this Cookie Policy controls.
We take a minimalist approach. The marketing site runs with no advertising cookies and no cross-site trackers. Inside the app we use session cookies so you can stay logged in and CSRF tokens so we can verify that requests actually came from you. We do not participate in ad networks and we do not embed social-media "share" buttons that phone home when the page loads.
A cookie is a small text file that a website stores in your browser. When you return to that website, the browser sends the cookie back, which is how the site recognizes you. Cookies serve different purposes and come in several flavors:
Related technologies include browser local storage, session storage, and pixel tags. We treat all of these the same way: we use them only where there is a clear functional need, and we list them below alongside cookies.
The list below is exhaustive. If we add a cookie, we update this page.
Required for the Service to function. You cannot opt out of these without losing the ability to log in.
aw_session (app only) — authenticated session identifier. Lifetime: up to 30 days or until logout, whichever comes first. HttpOnly, Secure, SameSite=Lax.aw_csrf (app only) — CSRF protection token. Lifetime: session. Secure, SameSite=Strict.aw_auth_state (app only, transient) — OAuth round-trip state during DMS connection flows. Lifetime: 10 minutes.Remember settings so you don't have to repeat yourself.
aw_theme — light or dark mode. Lifetime: 1 year.aw_last_workspace — which workspace you opened last, so we can return you there on next login. Lifetime: 1 year.We use privacy-respecting, aggregate-only analytics to understand which pages are useful. No cross-site tracking.
We currently use no analytics inside app.aewita.com beyond the server-side operational telemetry described in the Privacy Policy.
Inside app.aewita.com we use a few non-cookie storage mechanisms that are functionally similar:
We do not use web beacons, tracking pixels, or browser fingerprinting. The Service does not try to re-identify you across devices using canvas fingerprinting, audio fingerprinting, font enumeration, or other probabilistic signals.
For clarity, Aewita does not set or permit any of the following on aewita.com or app.aewita.com:
We commit to this list actively: adding any of these categories would require a material update to this Cookie Policy and, where required, consent from visitors before the cookie is set.
You have several ways to control cookies:
Because we do not set optional tracking cookies by default, we do not interrupt your visit with a consent banner on aewita.com. If you are in a jurisdiction that requires explicit consent for a specific cookie we later add, we will ask for consent before setting it.
A small number of third-party services may set their own cookies when you interact with their specific feature:
We do not control the cookies third parties set on their own domains. When we link to those services, we link to their policies as well.
You may notice that aewita.com does not show a consent banner. That is intentional. Consent banners exist to gate optional cookies behind your agreement. We do not set optional cookies on the marketing site by default, so there is nothing to ask permission for. If we ever add a cookie that requires consent under applicable law, we will show a banner at that point, and we will design it so the least-intrusive option (reject all optional cookies) is as easy as the most-intrusive option. If you are in a jurisdiction that grants you specific cookie-consent rights and you believe we have missed one, tell us at legal@aewita.com and we will fix it.
If you block the strictly necessary cookies on app.aewita.com, login will not work; the server cannot recognize that a request belongs to your session. That is a property of cookie-based authentication on the web generally, not a limitation we have imposed. If you block the preference cookies, the Service still works; you will simply see the default theme and default workspace on each visit. If you block our analytics on aewita.com (either by sending DNT/GPC or by blocking first-party analytics scripts at the browser level), the marketing site still works; we just lose aggregate visibility into which pages are useful to readers.
We may update this Cookie Policy. Material changes will be announced at the top of this page, and the "Last updated" date will be revised. For customers logged into the app, material changes that affect your experience are also announced by email. We keep prior versions of this page on request so you can see what was in force at the time of your visit.
Questions about cookies or anything on this page:
Scrivly, Inc. d/b/a Aewita
Attn: Privacy
Wilmington, DE
legal@aewita.com