Last updated 23 August 2026. This is the whole policy; there is no longer version elsewhere.

ASAS is a library of layout blocks for WordPress and Elementor, and a browser tool for putting them in order. This page says exactly what the site records about you, why, and how to get it changed or removed. It describes what the software actually does today. If that changes, this page changes with it.

Using the site without an account

Browsing the library, filtering it, stacking a page, changing the design kit and previewing the result need no account and record nothing about you. No account is created, no cookie is set by ASAS, and nothing you do is stored against you.

Your browser keeps a few small preferences on your own device so the site behaves sensibly when you come back. They stay in your browser and are never sent anywhere: the design kit you last picked on the home page, whether you have dismissed the Studio’s “How it works” panel, whether you have dismissed the step-by-step tips, and — for the current tab only — the stack you are building, so that signing in does not lose it. Elementor, the page builder this site runs on, also keeps a page-view and session counter in your browser; it too is only read in the browser.

What an account records

An account is needed for one thing: downloading a build as an Elementor template file. This is what is stored, and nothing else.

• Your email address — it identifies the account and is how you sign in and reset a password. Your sign-in name is derived from the part of the address before the @, because the form never asks you to invent one.
• The name you gave us — shown back to you in the Studio so you can see whose account you are in.
• Your password — stored only as a one-way hash by WordPress itself. Nobody at ASAS can read it.
• When the account was created, and when it last signed in — so an account that is not being used can be recognised as such.
• How many builds you have downloaded, and when the last one was — shown back to you on your own account panel.
• Your last 20 builds — for each one, the list of template names it contained, the colour and type kit you chose, how many blocks it had, and the date. This is what lets you reopen a page you have already taken instead of rebuilding it. It is a list, not an archive: the twenty-first pushes the oldest out. The downloaded file itself is not kept.
• The moment you accepted the Terms and this policy — a timestamp, because “they agreed” is only worth something if we can say when.
• Whether you asked for occasional email — recorded as its own separate fact, and it starts unticked.
• Company, website and role — optional. These three are only stored if you type them. Leaving them blank stores nothing at all.

No payment information is collected anywhere on this site. There is no checkout, no card field and no billing record, because nothing here is sold today. The registration form has no field for a phone number or a postal address either.

Signing in, cookies and sessions

Signing in uses WordPress’s own login. It sets WordPress’s own session cookies — named wordpress_logged_in_… and wordpress_sec_… — which are what keep you signed in as you move between pages. They are set to last fourteen days, they cannot be read by scripts on the page, and they are only sent back to this site. They exist to keep you signed in, and for nothing else. Signing out clears them.

WordPress also records, alongside each active session, the IP address and browser user-agent it was started from. This is part of how WordPress lets a session be recognised and ended; it is core behaviour rather than something ASAS adds, and it goes away when the session expires or you sign out. ASAS’s own code records no IP address and no browser fingerprint of any kind.

Passwords

Passwords are handled by WordPress. There is no separate ASAS password store, which is also why a reset works the way you would expect: the “Forgot your password?” link goes to WordPress’s own lost-password form, which sends a one-time reset link to the address on the account.

Outgoing email from this site is not yet configured, so a reset message may not arrive. If that happens, write to the address at the foot of this page and we will sort it out with you directly. This paragraph will be removed once mail is working.

Email you have asked for

The marketing box on the registration form is separate from accepting the Terms, and it starts unticked. Ticking it records that you are willing to hear occasionally when new blocks are added — nothing more. There is no mailing list yet and no marketing email has been sent. Ask at the address below to change your answer at any time.

Who else sees any of this

Nobody. Your account details are not sold, rented, shared or passed to anyone, and there is no advertising network, analytics service, tag manager or tracking pixel anywhere on this site. The fonts are served from this server rather than from a font service, the placeholder images and icons are drawn for the library, and a page here does not fetch anything from a third-party host.

Two things do leave this server, and neither carries anything about you: WordPress checks wordpress.org for software updates, and the Elementor plugin checks its own licence with its maker. Both are the software maintaining itself.

How long it is kept

Your account and the details above are kept while the account exists. Saved builds are capped at the most recent twenty and older ones drop off on their own. Ask us to delete the account and all of it goes with it.

Seeing it, correcting it, deleting it

Write to mousa@asas.build from the address on your account and ask for any of the following. We will use WordPress’s own personal-data export and erase tools so that what you get is the complete record rather than a summary of it.

• A copy of everything held about you.
• A correction — your name, your email address, or any of the three optional fields.
• Deletion of the account and everything listed on this page.
• A change of mind about the marketing question.

Depending on where you live you may also have rights under your own data-protection law. Nothing here is meant to narrow them; if you want to exercise one, the same address is the place to start.

Contact

ASAS — Mousa Batarseh, Warren, Michigan.
Email: mousa@asas.build
Phone: +1 (248) 810-1816

If this page and the software ever disagree, the software is the bug. Tell us and we will fix whichever one is wrong.